Advertisement
znavko

emerge -uN gcc

Dec 17th, 2017
230
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.45 KB | None | 0 0
  1. # emerge -uN gcc
  2. Calculating dependencies... done!
  3.  
  4. >>> Verifying ebuild manifests
  5.  
  6. >>> Emerging (1 of 2) sys-devel/binutils-2.28-r4::core-kit
  7. * binutils-2.28.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
  8. * binutils-2.28-patches-1.2.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
  9. >>> Unpacking source...
  10. >>> Unpacking binutils-2.28.tar.bz2 to /var/tmp/portage/sys-devel/binutils-2.28-r4/work
  11. >>> Unpacking binutils-2.28-patches-1.2.tar.xz to /var/tmp/portage/sys-devel/binutils-2.28-r4/work
  12. >>> Source unpacked in /var/tmp/portage/sys-devel/binutils-2.28-r4/work
  13. >>> Preparing source in /var/tmp/portage/sys-devel/binutils-2.28-r4/work/binutils-2.28 ...
  14. * Applying various patches (bugfixes/updates) ...
  15. * 00_all_0001-ld-always-warn-about-textrels-in-files.patch ... [ ok ]
  16. * 00_all_0002-gold-ld-add-support-for-poisoned-system-directories.patch ... [ ok ]
  17. * 00_all_0003-ld-enable-new-dtags-by-default-for-linux-gnu-targets.patch ... [ ok ]
  18. * 00_all_0004-gold-ld-enable-gnu-hash-by-default.patch ... [ ok ]
  19. * 00_all_0005-libiberty-install-PIC-version-of-libiberty.a.patch ... [ ok ]
  20. * 00_all_0006-opcodes-link-against-libbfd.la-for-rpath-deps.patch ... [ ok ]
  21. * 00_all_0007-CVE-2017-8398.patch ... [ ok ]
  22. * 00_all_0008-CVE-2017-8393.patch ... [ ok ]
  23. * 00_all_0009-CVE-2017-8394.patch ... [ ok ]
  24. * 00_all_0010-CVE-2017-8395.patch ... [ ok ]
  25. * 00_all_0011-CVE-2017-8396-CVE-2017-8397.patch ... [ ok ]
  26. * 00_all_0012-CVE-2017-8421.patch ... [ ok ]
  27. * 00_all_0013-CVE-2017-9038.patch ... [ ok ]
  28. * 00_all_0014-CVE-2017-9039.patch ... [ ok ]
  29. * 00_all_0015-CVE-2017-9040-CVE-2017-9042.patch ... [ ok ]
  30. * 00_all_0016-CVE-2017-9041.patch ... [ ok ]
  31. * 00_all_0017-CVE-2017-7614.patch ... [ ok ]
  32. * 00_all_0018-CVE-2017-6965.patch ... [ ok ]
  33. * 00_all_0019-CVE-2017-6966.patch ... [ ok ]
  34. * 00_all_0020-CVE-2017-6969.patch ... [ ok ]
  35. * Done with patching
  36. * Using GNU config files from /usr/share/gnuconfig
  37. * Updating config.sub [ ok ]
  38. * Updating config.guess [ ok ]
  39. * Running elibtoolize in: binutils-2.28/
  40. * Applying portage/2.2 patch ...
  41. * Applying sed/1.5.6 patch ...
  42. * Applying as-needed/2.2.6 patch ...
  43. * Running elibtoolize in: binutils-2.28/bfd/
  44. * Applying target-nm/2.4.2 patch ...
  45. * Applying ppc64le/2.4.4 patch ...
  46. * Running elibtoolize in: binutils-2.28/binutils/
  47. * Applying target-nm/2.4.2 patch ...
  48. * Applying ppc64le/2.4.4 patch ...
  49. * Running elibtoolize in: binutils-2.28/etc/
  50. * Running elibtoolize in: binutils-2.28/gas/
  51. * Applying target-nm/2.4.2 patch ...
  52. * Applying ppc64le/2.4.4 patch ...
  53. * Running elibtoolize in: binutils-2.28/gold/
  54. * Running elibtoolize in: binutils-2.28/gprof/
  55. * Applying target-nm/2.4.2 patch ...
  56. * Applying ppc64le/2.4.4 patch ...
  57. * Running elibtoolize in: binutils-2.28/intl/
  58. * Running elibtoolize in: binutils-2.28/ld/
  59. * Applying target-nm/2.4.2 patch ...
  60. * Applying ppc64le/2.4.4 patch ...
  61. * Running elibtoolize in: binutils-2.28/libiberty/
  62. * Running elibtoolize in: binutils-2.28/opcodes/
  63. * Applying target-nm/2.4.2 patch ...
  64. * Applying ppc64le/2.4.4 patch ...
  65. * Running elibtoolize in: binutils-2.28/zlib/
  66. * Applying target-nm/2.4.2 patch ...
  67. * Applying ppc64le/2.4.4 patch ...
  68. * Applying 00_all_0024-CVE-2017-9742.patch ... [ ok ]
  69. * Applying 00_all_0025-CVE-2017-9954.patch ... [ ok ]
  70. >>> Source prepared.
  71. >>> Configuring source in /var/tmp/portage/sys-devel/binutils-2.28-r4/work/binutils-2.28 ...
  72. * Sorry, but binutils does not support the LINGUAS: en_US ru_RU
  73.  
  74. * CATEGORY: sys-devel
  75. * CBUILD: x86_64-pc-linux-gnu
  76. * CHOST: x86_64-pc-linux-gnu
  77. * CTARGET: x86_64-pc-linux-gnu
  78. * CFLAGS: -march=native -O2 -pipe
  79. * LDFLAGS: -Wl,-O1 -Wl,--sort-common -Wl,--as-needed
  80.  
  81. ./configure --enable-gold --enable-plugins --without-included-gettext --with-system-zlib --build=x86_64-pc-linux-gnu --enable-secureplt --prefix=/usr --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --datadir=/usr/share/binutils-data/x86_64-pc-linux-gnu/2.28 --infodir=/usr/share/binutils-data/x86_64-pc-linux-gnu/2.28/info --mandir=/usr/share/binutils-data/x86_64-pc-linux-gnu/2.28/man --bindir=/usr/x86_64-pc-linux-gnu/binutils-bin/2.28 --libdir=/usr/lib64/binutils/x86_64-pc-linux-gnu/2.28 --libexecdir=/usr/lib64/binutils/x86_64-pc-linux-gnu/2.28 --includedir=/usr/lib64/binutils/x86_64-pc-linux-gnu/2.28/include --enable-obsolete --enable-shared --enable-threads --enable-relro --enable-install-libiberty --disable-werror --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion=Gentoo 2.28 p1.2 --disable-static --disable-gdb --disable-libdecnumber --disable-readline --disable-sim --without-stage1-ldflags
  82. checking build system type... x86_64-pc-linux-gnu
  83. checking host system type... x86_64-pc-linux-gnu
  84. checking target system type... x86_64-pc-linux-gnu
  85. checking for a BSD-compatible install... /usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c
  86. checking whether ln works... yes
  87. checking whether ln -s works... yes
  88. checking for a sed that does not truncate output... /bin/sed
  89. checking for gawk... gawk
  90. checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
  91. checking for C compiler default output file name...
  92. configure: error: in `/var/tmp/portage/sys-devel/binutils-2.28-r4/work/build':
  93. configure: error: C compiler cannot create executables
  94. See `config.log' for more details.
  95. * ERROR: sys-devel/binutils-2.28-r4::core-kit failed (configure phase):
  96. * (no error message)
  97. *
  98. * Call stack:
  99. * ebuild.sh, line 115: Called src_configure
  100. * environment, line 2975: Called toolchain-binutils_src_configure
  101. * environment, line 3856: Called die
  102. * The specific snippet of code:
  103. * "${S}"/configure "${myconf[@]}" || die;
  104. *
  105. * If you need support, post the output of `emerge --info '=sys-devel/binutils-2.28-r4::core-kit'`,
  106. * the complete build log and the output of `emerge -pqv '=sys-devel/binutils-2.28-r4::core-kit'`.
  107. * The complete build log is located at '/var/tmp/portage/sys-devel/binutils-2.28-r4/temp/build.log'.
  108. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/binutils-2.28-r4/temp/environment'.
  109. * Working directory: '/var/tmp/portage/sys-devel/binutils-2.28-r4/work/build'
  110. * S: '/var/tmp/portage/sys-devel/binutils-2.28-r4/work/binutils-2.28'
  111.  
  112. >>> Failed to emerge sys-devel/binutils-2.28-r4, Log file:
  113.  
  114. >>> '/var/tmp/portage/sys-devel/binutils-2.28-r4/temp/build.log'
  115.  
  116. * Messages for package sys-devel/binutils-2.28-r4:
  117.  
  118. * ERROR: sys-devel/binutils-2.28-r4::core-kit failed (configure phase):
  119. * (no error message)
  120. *
  121. * Call stack:
  122. * ebuild.sh, line 115: Called src_configure
  123. * environment, line 2975: Called toolchain-binutils_src_configure
  124. * environment, line 3856: Called die
  125. * The specific snippet of code:
  126. * "${S}"/configure "${myconf[@]}" || die;
  127. *
  128. * If you need support, post the output of `emerge --info '=sys-devel/binutils-2.28-r4::core-kit'`,
  129. * the complete build log and the output of `emerge -pqv '=sys-devel/binutils-2.28-r4::core-kit'`.
  130. * The complete build log is located at '/var/tmp/portage/sys-devel/binutils-2.28-r4/temp/build.log'.
  131. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/binutils-2.28-r4/temp/environment'.
  132. * Working directory: '/var/tmp/portage/sys-devel/binutils-2.28-r4/work/build'
  133. * S: '/var/tmp/portage/sys-devel/binutils-2.28-r4/work/binutils-2.28'
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement