Advertisement
Guest User

Untitled

a guest
Oct 29th, 2010
167
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.80 KB | None | 0 0
  1. * sandbox-2.3.tar.xz RMD160 SHA1 SHA256 size ;-) ... [ ok ]
  2. * Package: sys-apps/sandbox-2.3-r1
  3. * Repository: gentoo
  4. * Maintainer: sandbox@gentoo.org
  5. * USE: amd64 elibc_glibc kernel_linux multilib userland_GNU
  6. >>> Unpacking source...
  7. >>> Unpacking sandbox-2.3.tar.xz to /var/tmp/portage/sys-apps/sandbox-2.3-r1/work
  8. unpack sandbox-2.3.tar.xz: file format not recognized. Ignoring.
  9. >>> Source unpacked in /var/tmp/portage/sys-apps/sandbox-2.3-r1/work
  10. >>> Compiling source in /var/tmp/portage/sys-apps/sandbox-2.3-r1/work/sandbox-2.3 ...
  11. * Configuring sandbox for ABI=x86...
  12. * econf: updating sandbox-2.3/config.guess with /usr/share/gnuconfig/config.guess
  13. * econf: updating sandbox-2.3/config.sub with /usr/share/gnuconfig/config.sub
  14. ../sandbox-2.3//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 --libdir=/usr/lib32
  15. checking for a BSD-compatible install... /usr/bin/install -c
  16. checking whether build environment is sane... yes
  17. checking for a thread-safe mkdir -p... /bin/mkdir -p
  18. checking for gawk... gawk
  19. checking whether make sets $(MAKE)... yes
  20. checking environment state... ok
  21. checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32
  22. checking whether the C compiler works... no
  23. configure: error: in `/var/tmp/portage/sys-apps/sandbox-2.3-r1/work/build-x86':
  24. configure: error: C compiler cannot create executables
  25. See `config.log' for more details
  26.  
  27. !!! Please attach the following file when seeking support:
  28. !!! /var/tmp/portage/sys-apps/sandbox-2.3-r1/work/build-x86/config.log
  29. * ERROR: sys-apps/sandbox-2.3-r1 failed:
  30. * econf failed
  31. *
  32. * Call stack:
  33. * ebuild.sh, line 56: Called src_compile
  34. * environment, line 2688: Called econf
  35. * ebuild.sh, line 558: Called die
  36. * The specific snippet of code:
  37. * die "econf failed"
  38. *
  39. * If you need support, post the output of 'emerge --info =sys-apps/sandbox-2.3-r1',
  40. * the complete build log and the output of 'emerge -pqv =sys-apps/sandbox-2.3-r1'.
  41. * If configure failed with a 'cannot run C compiled programs' error, try this:
  42. * FEATURES=-sandbox emerge sandbox
  43. * The complete build log is located at '/var/tmp/portage/sys-apps/sandbox-2.3-r1/temp/build.log'.
  44. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/sandbox-2.3-r1/temp/environment'.
  45. * S: '/var/tmp/portage/sys-apps/sandbox-2.3-r1/work/sandbox-2.3'
  46.  
  47. >>> Failed to emerge sys-apps/sandbox-2.3-r1, Log file:
  48.  
  49. >>> '/var/tmp/portage/sys-apps/sandbox-2.3-r1/temp/build.log'
  50.  
  51. * Messages for package sys-apps/sandbox-2.3-r1:
  52.  
  53. * ERROR: sys-apps/sandbox-2.3-r1 failed:
  54. * econf failed
  55. *
  56. * Call stack:
  57. * ebuild.sh, line 56: Called src_compile
  58. * environment, line 2688: Called econf
  59. * ebuild.sh, line 558: Called die
  60. * The specific snippet of code:
  61. * die "econf failed"
  62. *
  63. * If you need support, post the output of 'emerge --info =sys-apps/sandbox-2.3-r1',
  64. * the complete build log and the output of 'emerge -pqv =sys-apps/sandbox-2.3-r1'.
  65. * If configure failed with a 'cannot run C compiled programs' error, try this:
  66. * FEATURES=-sandbox emerge sandbox
  67. * The complete build log is located at '/var/tmp/portage/sys-apps/sandbox-2.3-r1/temp/build.log'.
  68. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/sandbox-2.3-r1/temp/environment'.
  69. * S: '/var/tmp/portage/sys-apps/sandbox-2.3-r1/work/sandbox-2.3'
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement