Guest User

Untitled

a guest
Nov 17th, 2018
139
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.91 KB | None | 0 0
  1. Calculating dependencies
  2. * IMPORTANT: 1 news items need reading for repository 'gentoo'.
  3. * Use eselect news to read news items.
  4.  
  5. ... done!
  6.  
  7. >>> Verifying ebuild manifests
  8.  
  9. >>> Emerging (1 of 1) sys-devel/libtool-2.4-r1
  10. * libtool-2.4.tar.xz RMD160 SHA1 SHA256 size ;-) ... [ ok ]
  11. >>> Unpacking source...
  12. >>> Unpacking ./libtool-2.4.tar to /var/tmp/portage/sys-devel/libtool-2.4-r1/work
  13. >>> Source unpacked in /var/tmp/portage/sys-devel/libtool-2.4-r1/work
  14. >>> Preparing source in /var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4 ...
  15. * Applying libtool-1.5.20-use-linux-version-in-fbsd.patch ...
  16. [ ok ]
  17. * Running eautoreconf in '/var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4/libltdl' ...
  18. * Running true --install --copy --force --automake ...
  19. [ ok ]
  20. * Running aclocal -I m4 ...
  21. [ ok ]
  22. * Running autoconf ...
  23. [ ok ]
  24. * Running autoheader ...
  25. [ ok ]
  26. * Running automake --add-missing --copy --foreign ...
  27. [ ok ]
  28. * Running eautoreconf in '/var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4' ...
  29. * Running true --install --copy --force --automake ...
  30. [ ok ]
  31. * Running aclocal -I libltdl/m4 ...
  32. [ ok ]
  33. * Running autoconf ...
  34. [ ok ]
  35. * Running autoheader ...
  36. [ ok ]
  37. * Running automake --add-missing --copy ...
  38. [ ok ]
  39. >>> Source prepared.
  40. >>> Configuring source in /var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4 ...
  41. * econf: updating libtool-2.4/libltdl/config/config.guess with /usr/share/gnuconfig/config.guess
  42. * econf: updating libtool-2.4/libltdl/config/config.sub with /usr/share/gnuconfig/config.sub
  43. ./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib
  44. ## ----------------------- ##
  45. ## Configuring libtool 2.4 ##
  46. ## ----------------------- ##
  47.  
  48. checking for a BSD-compatible install... /usr/bin/install -c
  49. checking whether build environment is sane... yes
  50. checking for a thread-safe mkdir -p... /bin/mkdir -p
  51. checking for gawk... gawk
  52. checking whether make sets $(MAKE)... yes
  53. checking build system type... i686-pc-linux-gnu
  54. checking host system type... i686-pc-linux-gnu
  55. configure: autobuild project... GNU Libtool
  56. configure: autobuild revision... 2.4 ()
  57. configure: autobuild hostname... li459-123
  58. configure: autobuild mode... default
  59. configure: autobuild timestamp... 20120624T123436Z
  60. checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
  61. checking whether the C compiler works... no
  62. configure: error: in `/var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4':
  63. configure: error: C compiler cannot create executables
  64. See `config.log' for more details
  65.  
  66. !!! Please attach the following file when seeking support:
  67. !!! /var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4/config.log
  68. * ERROR: sys-devel/libtool-2.4-r1 failed (configure phase):
  69. * econf failed
  70. *
  71. * Call stack:
  72. * ebuild.sh, line 85: Called src_configure
  73. * environment, line 2795: Called default
  74. * phase-functions.sh, line 798: Called _eapi2_src_configure
  75. * phase-helpers.sh, line 567: Called econf
  76. * phase-helpers.sh, line 467: Called die
  77. * The specific snippet of code:
  78. * die "econf failed"
  79. *
  80. * If you need support, post the output of `emerge --info '=sys-devel/libtool-2.4-r1'`,
  81. * the complete build log and the output of `emerge -pqv '=sys-devel/libtool-2.4-r1'`.
  82. /usr/lib/portage/bin/isolated-functions.sh: line 214: wait: `econf failed': not a pid or valid job spec
  83. * The complete build log is located at '/var/tmp/portage/sys-devel/libtool-2.4-r1/temp/build.log'.
  84. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/libtool-2.4-r1/temp/environment'.
  85. * Working directory: '/var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4'
  86. * S: '/var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4'
  87.  
  88. >>> Failed to emerge sys-devel/libtool-2.4-r1, Log file:
  89.  
  90. >>> '/var/tmp/portage/sys-devel/libtool-2.4-r1/temp/build.log'
  91. * Messages for package sys-devel/libtool-2.4-r1:
  92. * ERROR: sys-devel/libtool-2.4-r1 failed (configure phase):
  93. * econf failed
  94. *
  95. * Call stack:
  96. * ebuild.sh, line 85: Called src_configure
  97. * environment, line 2795: Called default
  98. * phase-functions.sh, line 798: Called _eapi2_src_configure
  99. * phase-helpers.sh, line 567: Called econf
  100. * phase-helpers.sh, line 467: Called die
  101. * The specific snippet of code:
  102. * die "econf failed"
  103. *
  104. * If you need support, post the output of `emerge --info '=sys-devel/libtool-2.4-r1'`,
  105. * the complete build log and the output of `emerge -pqv '=sys-devel/libtool-2.4-r1'`.
  106. * The complete build log is located at '/var/tmp/portage/sys-devel/libtool-2.4-r1/temp/build.log'.
  107. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/libtool-2.4-r1/temp/environment'.
  108. * Working directory: '/var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4'
  109. * S: '/var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4'
Add Comment
Please, Sign In to add comment