API tools faq
paste
Advertisement
Guest User

error

a guest
Oct 16th, 2013
122
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 18.59 KB | None | 0 0
raw download clone embed print report
  1. * (445/445) Generating zu_ZA.ISO-8859-1 ... [ ok ]
  2. * Generation complete
  3. /var/tmp/portage/._portage_reinstall_.XHEXl9/bin/phase-functions.sh: line 84: 22361 Segmentation fault "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}"
  4. * ERROR: sys-libs/glibc-2.17 failed (postinst phase):
  5. * filter-bash-environment.py failed
  6. *
  7. * Call stack:
  8. * ebuild.sh, line 712: Called __ebuild_main 'postinst'
  9. * phase-functions.sh, line 872: Called __filter_readonly_variables '--filter-path' '--filter-sandbox' '--allow-extra-vars'
  10. * phase-functions.sh, line 134: Called die
  11. * The specific snippet of code:
  12. * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
  13. *
  14. * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.17'`,
  15. * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.17'`.
  16. * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.17/temp/build.log'.
  17. * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.17/temp/environment'.
  18. * Working directory: '/var/tmp/portage/sys-libs/glibc-2.17'
  19. * S: '/var/tmp/portage/sys-libs/glibc-2.17/work/glibc-2.17'
  20. /var/tmp/portage/._portage_reinstall_.XHEXl9/bin/isolated-functions.sh: line 109: 22440 Segmentation fault "$PORTAGE_BIN_PATH"/ebuild-ipc exit 1
  21. * The ebuild phase 'postinst' has exited unexpectedly. This type of
  22. * behavior is known to be triggered by things such as failed variable
  23. * assignments (bug #190128) or bad substitution errors (bug #200313).
  24. * Normally, before exiting, bash should have displayed an error message
  25. * above. If bash did not produce an error message above, it's possible
  26. * that the ebuild has called `exit` when it should have called `die`
  27. * instead. This behavior may also be triggered by a corrupt bash binary or
  28. * a hardware problem such as memory or cpu malfunction. If the problem is
  29. * not reproducible or it appears to occur randomly, then it is likely to
  30. * be triggered by a hardware problem. If you suspect a hardware problem
  31. * then you should try some basic hardware diagnostics such as memtest.
  32. * Please do not report this as a bug unless it is consistently
  33. * reproducible and you are sure that your bash binary and hardware are
  34. * functioning properly.
  35. /var/tmp/portage/._portage_reinstall_.XHEXl9/bin/misc-functions.sh: line 1262: 22464 Segmentation fault "$PORTAGE_BIN_PATH"/ebuild-ipc exit $?
  36. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  37. * behavior is known to be triggered by things such as failed variable
  38. * assignments (bug #190128) or bad substitution errors (bug #200313).
  39. * Normally, before exiting, bash should have displayed an error message
  40. * above. If bash did not produce an error message above, it's possible
  41. * that the ebuild has called `exit` when it should have called `die`
  42. * instead. This behavior may also be triggered by a corrupt bash binary or
  43. * a hardware problem such as memory or cpu malfunction. If the problem is
  44. * not reproducible or it appears to occur randomly, then it is likely to
  45. * be triggered by a hardware problem. If you suspect a hardware problem
  46. * then you should try some basic hardware diagnostics such as memtest.
  47. * Please do not report this as a bug unless it is consistently
  48. * reproducible and you are sure that your bash binary and hardware are
  49. * functioning properly.
  50. !!! FAILED postinst: 1
  51. /var/tmp/portage/._portage_reinstall_.XHEXl9/bin/misc-functions.sh: line 1262: 22489 Segmentation fault "$PORTAGE_BIN_PATH"/ebuild-ipc exit $?
  52. * The ebuild phase 'other' has exited unexpectedly. This type of behavior
  53. * is known to be triggered by things such as failed variable assignments
  54. * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  55. * exiting, bash should have displayed an error message above. If bash did
  56. * not produce an error message above, it's possible that the ebuild has
  57. * called `exit` when it should have called `die` instead. This behavior
  58. * may also be triggered by a corrupt bash binary or a hardware problem
  59. * such as memory or cpu malfunction. If the problem is not reproducible or
  60. * it appears to occur randomly, then it is likely to be triggered by a
  61. * hardware problem. If you suspect a hardware problem then you should try
  62. * some basic hardware diagnostics such as memtest. Please do not report
  63. * this as a bug unless it is consistently reproducible and you are sure
  64. * that your bash binary and hardware are functioning properly.
  65.  
  66. >>> Emerging (3 of 38) sys-devel/gcc-config-1.8
  67. * gcc-config-1.8.tar.xz SHA256 SHA512 size ;-) ... [ ok ]
  68. /var/tmp/portage/._portage_reinstall_.XHEXl9/bin/phase-functions.sh: line 84: 22557 Segmentation fault "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}"
  69. * ERROR: sys-devel/gcc-config-1.8 failed (setup phase):
  70. * filter-bash-environment.py failed
  71. *
  72. * Call stack:
  73. * ebuild.sh, line 712: Called __ebuild_main 'setup'
  74. * phase-functions.sh, line 972: Called __filter_readonly_variables '--filter-features'
  75. * phase-functions.sh, line 134: Called die
  76. * The specific snippet of code:
  77. * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
  78. *
  79. * If you need support, post the output of `emerge --info '=sys-devel/gcc-config-1.8'`,
  80. * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-config-1.8'`.
  81. * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-config-1.8/temp/build.log'.
  82. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-config-1.8/temp/environment'.
  83. * Working directory: '/var/tmp/portage/sys-devel/gcc-config-1.8'
  84. * S: '/var/tmp/portage/sys-devel/gcc-config-1.8/work/gcc-config-1.8'
  85. /var/tmp/portage/._portage_reinstall_.XHEXl9/bin/isolated-functions.sh: line 109: 22636 Segmentation fault "$PORTAGE_BIN_PATH"/ebuild-ipc exit 1
  86. * The ebuild phase 'setup' has exited unexpectedly. This type of behavior
  87. * is known to be triggered by things such as failed variable assignments
  88. * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  89. * exiting, bash should have displayed an error message above. If bash did
  90. * not produce an error message above, it's possible that the ebuild has
  91. * called `exit` when it should have called `die` instead. This behavior
  92. * may also be triggered by a corrupt bash binary or a hardware problem
  93. * such as memory or cpu malfunction. If the problem is not reproducible or
  94. * it appears to occur randomly, then it is likely to be triggered by a
  95. * hardware problem. If you suspect a hardware problem then you should try
  96. * some basic hardware diagnostics such as memtest. Please do not report
  97. * this as a bug unless it is consistently reproducible and you are sure
  98. * that your bash binary and hardware are functioning properly.
  99. /var/tmp/portage/._portage_reinstall_.XHEXl9/bin/misc-functions.sh: line 1262: 22649 Segmentation fault "$PORTAGE_BIN_PATH"/ebuild-ipc exit $?
  100. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  101. * behavior is known to be triggered by things such as failed variable
  102. * assignments (bug #190128) or bad substitution errors (bug #200313).
  103. * Normally, before exiting, bash should have displayed an error message
  104. * above. If bash did not produce an error message above, it's possible
  105. * that the ebuild has called `exit` when it should have called `die`
  106. * instead. This behavior may also be triggered by a corrupt bash binary or
  107. * a hardware problem such as memory or cpu malfunction. If the problem is
  108. * not reproducible or it appears to occur randomly, then it is likely to
  109. * be triggered by a hardware problem. If you suspect a hardware problem
  110. * then you should try some basic hardware diagnostics such as memtest.
  111. * Please do not report this as a bug unless it is consistently
  112. * reproducible and you are sure that your bash binary and hardware are
  113. * functioning properly.
  114.  
  115. >>> Failed to emerge sys-devel/gcc-config-1.8, Log file:
  116.  
  117. >>> '/var/tmp/portage/sys-devel/gcc-config-1.8/temp/build.log'
  118.  
  119. * Messages for package sys-libs/timezone-data-2013g:
  120.  
  121. * You do not have TIMEZONE set in /etc/conf.d/clock.
  122. * Skipping auto-update of /etc/localtime.
  123.  
  124. * Messages for package sys-libs/glibc-2.10.1-r1:
  125.  
  126. * The ebuild phase 'prerm' has exited unexpectedly. This type of behavior
  127. * is known to be triggered by things such as failed variable assignments
  128. * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  129. * exiting, bash should have displayed an error message above. If bash did
  130. * not produce an error message above, it's possible that the ebuild has
  131. * called `exit` when it should have called `die` instead. This behavior
  132. * may also be triggered by a corrupt bash binary or a hardware problem
  133. * such as memory or cpu malfunction. If the problem is not reproducible or
  134. * it appears to occur randomly, then it is likely to be triggered by a
  135. * hardware problem. If you suspect a hardware problem then you should try
  136. * some basic hardware diagnostics such as memtest. Please do not report
  137. * this as a bug unless it is consistently reproducible and you are sure
  138. * that your bash binary and hardware are functioning properly.
  139. * ERROR: sys-libs/glibc-2.10.1-r1 failed (prerm phase):
  140. * filter-bash-environment.py failed
  141. *
  142. * Call stack:
  143. * ebuild.sh, line 486: Called __preprocess_ebuild_env
  144. * phase-functions.sh, line 153: Called __filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
  145. * phase-functions.sh, line 134: Called die
  146. * The specific snippet of code:
  147. * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
  148. *
  149. * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.10.1-r1'`,
  150. * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.10.1-r1'`.
  151. * The complete build log is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.10.1-r1/temp/build.log'.
  152. * The ebuild environment file is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.10.1-r1/temp/environment'.
  153. * Working directory: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.10.1-r1'
  154. * S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.10.1-r1/work/glibc-2.10.1'
  155. * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  156. * is known to be triggered by things such as failed variable assignments
  157. * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  158. * exiting, bash should have displayed an error message above. If bash did
  159. * not produce an error message above, it's possible that the ebuild has
  160. * called `exit` when it should have called `die` instead. This behavior
  161. * may also be triggered by a corrupt bash binary or a hardware problem
  162. * such as memory or cpu malfunction. If the problem is not reproducible or
  163. * it appears to occur randomly, then it is likely to be triggered by a
  164. * hardware problem. If you suspect a hardware problem then you should try
  165. * some basic hardware diagnostics such as memtest. Please do not report
  166. * this as a bug unless it is consistently reproducible and you are sure
  167. * that your bash binary and hardware are functioning properly.
  168. * The 'postrm' phase of the 'sys-libs/glibc-2.10.1-r1' package has failed
  169. * with exit value 1.
  170. *
  171. * The problem occurred while executing the ebuild file named
  172. * 'glibc-2.10.1-r1.ebuild' located in the '/var/db/pkg/sys-
  173. * libs/glibc-2.10.1-r1' directory. If necessary, manually remove the
  174. * environment.bz2 file and/or the ebuild file located in that directory.
  175. *
  176. * Removal of the environment.bz2 file is preferred since it may allow the
  177. * removal phases to execute successfully. The ebuild will be sourced and
  178. * the eclasses from the current portage tree will be used when necessary.
  179. * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  180. * removal phases to be skipped entirely.
  181. * ERROR: sys-libs/glibc-2.10.1-r1 failed (postrm phase):
  182. * filter-bash-environment.py failed
  183. *
  184. * Call stack:
  185. * ebuild.sh, line 486: Called __preprocess_ebuild_env
  186. * phase-functions.sh, line 153: Called __filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
  187. * phase-functions.sh, line 134: Called die
  188. * The specific snippet of code:
  189. * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
  190. *
  191. * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.10.1-r1'`,
  192. * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.10.1-r1'`.
  193. * The complete build log is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.10.1-r1/temp/build.log'.
  194. * The ebuild environment file is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.10.1-r1/temp/environment'.
  195. * Working directory: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.10.1-r1'
  196. * S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.10.1-r1/work/glibc-2.10.1'
  197.  
  198. * Messages for package sys-libs/glibc-2.17:
  199.  
  200. * Defaulting /etc/host.conf:multi to on
  201. * The ebuild phase 'postinst' has exited unexpectedly. This type of
  202. * behavior is known to be triggered by things such as failed variable
  203. * assignments (bug #190128) or bad substitution errors (bug #200313).
  204. * Normally, before exiting, bash should have displayed an error message
  205. * above. If bash did not produce an error message above, it's possible
  206. * that the ebuild has called `exit` when it should have called `die`
  207. * instead. This behavior may also be triggered by a corrupt bash binary or
  208. * a hardware problem such as memory or cpu malfunction. If the problem is
  209. * not reproducible or it appears to occur randomly, then it is likely to
  210. * be triggered by a hardware problem. If you suspect a hardware problem
  211. * then you should try some basic hardware diagnostics such as memtest.
  212. * Please do not report this as a bug unless it is consistently
  213. * reproducible and you are sure that your bash binary and hardware are
  214. * functioning properly.
  215. * Generating all locales; edit /etc/locale.gen to save time/space
  216. * ERROR: sys-libs/glibc-2.17 failed (postinst phase):
  217. * filter-bash-environment.py failed
  218. *
  219. * Call stack:
  220. * ebuild.sh, line 712: Called __ebuild_main 'postinst'
  221. * phase-functions.sh, line 872: Called __filter_readonly_variables '--filter-path' '--filter-sandbox' '--allow-extra-vars'
  222. * phase-functions.sh, line 134: Called die
  223. * The specific snippet of code:
  224. * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
  225. *
  226. * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.17'`,
  227. * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.17'`.
  228. * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.17/temp/build.log'.
  229. * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.17/temp/environment'.
  230. * Working directory: '/var/tmp/portage/sys-libs/glibc-2.17'
  231. * S: '/var/tmp/portage/sys-libs/glibc-2.17/work/glibc-2.17'
  232. * The ebuild phase 'other' has exited unexpectedly. This type of behavior
  233. * is known to be triggered by things such as failed variable assignments
  234. * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  235. * exiting, bash should have displayed an error message above. If bash did
  236. * not produce an error message above, it's possible that the ebuild has
  237. * called `exit` when it should have called `die` instead. This behavior
  238. * may also be triggered by a corrupt bash binary or a hardware problem
  239. * such as memory or cpu malfunction. If the problem is not reproducible or
  240. * it appears to occur randomly, then it is likely to be triggered by a
  241. * hardware problem. If you suspect a hardware problem then you should try
  242. * some basic hardware diagnostics such as memtest. Please do not report
  243. * this as a bug unless it is consistently reproducible and you are sure
  244. * that your bash binary and hardware are functioning properly.
  245.  
  246. * Messages for package sys-devel/gcc-config-1.8:
  247.  
  248. * The ebuild phase 'setup' has exited unexpectedly. This type of behavior
  249. * is known to be triggered by things such as failed variable assignments
  250. * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  251. * exiting, bash should have displayed an error message above. If bash did
  252. * not produce an error message above, it's possible that the ebuild has
  253. * called `exit` when it should have called `die` instead. This behavior
  254. * may also be triggered by a corrupt bash binary or a hardware problem
  255. * such as memory or cpu malfunction. If the problem is not reproducible or
  256. * it appears to occur randomly, then it is likely to be triggered by a
  257. * hardware problem. If you suspect a hardware problem then you should try
  258. * some basic hardware diagnostics such as memtest. Please do not report
  259. * this as a bug unless it is consistently reproducible and you are sure
  260. * that your bash binary and hardware are functioning properly.
  261. * ERROR: sys-devel/gcc-config-1.8 failed (setup phase):
  262. * filter-bash-environment.py failed
  263. *
  264. * Call stack:
  265. * ebuild.sh, line 712: Called __ebuild_main 'setup'
  266. * phase-functions.sh, line 972: Called __filter_readonly_variables '--filter-features'
  267. * phase-functions.sh, line 134: Called die
  268. * The specific snippet of code:
  269. * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
  270. *
  271. * If you need support, post the output of `emerge --info '=sys-devel/gcc-config-1.8'`,
  272. * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-config-1.8'`.
  273. * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-config-1.8/temp/build.log'.
  274. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-config-1.8/temp/environment'.
  275. * Working directory: '/var/tmp/portage/sys-devel/gcc-config-1.8'
  276. * S: '/var/tmp/portage/sys-devel/gcc-config-1.8/work/gcc-config-1.8'
  277.  
  278. * Regenerating GNU info directory index...
  279. * Processed 84 info files.
  280.  
  281. * IMPORTANT: 17 news items need reading for repository 'gentoo'.
  282. * Use eselect news to read news items.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!