pastebin - collaborative debugging tool
kpaste.net RSS


Untitled
Posted by z0TK on Sun 3rd Jun 2012 23:51
raw | new post

  1. >>> Verifying ebuild manifests
  2. >>> Starting parallel fetch
  3. >>> Emerging (1 of 12) dev-libs/iniparser-3.0b-r1
  4. >>> Failed to emerge dev-libs/iniparser-3.0b-r1, Log file:
  5. >>>  '/var/tmp/portage/dev-libs/iniparser-3.0b-r1/temp/build.log'
  6. >>> Jobs: 0 of 12 complete, 1 failed                Load avg: 0.00, 0.01, 0.05
  7.  * Package:    dev-libs/iniparser-3.0b-r1
  8.  * Repository: gentoo
  9.  * Maintainer: samba@gentoo.org
  10.  * USE:        amd64 elibc_glibc kernel_linux multilib userland_GNU
  11.  * FEATURES:   distcc sandbox
  12.  * Applying iniparser-3.0b-fix-set-functions.patch ...
  13.  [ ok ]
  14. CFLAGS: -march=athlon64 -O2 -pipe
  15. compiling src/iniparser.c ...
  16. compiling src/dictionary.c ...
  17. distcc[19972] ERROR: nonblocking connect to 10.0.0.10:3632 failed: Connection refused
  18. distcc[19972] Warning: failed to distribute src/dictionary.c to 10.0.0.10, running locally instead
  19. distcc[19970] ERROR: nonblocking connect to 10.0.0.10:3632 failed: Connection refused
  20. distcc[19970] Warning: failed to distribute src/iniparser.c to 10.0.0.10, running locally instead
  21. distcc[19977] (dcc_execvp) ERROR: failed to exec i686-pc-linux-gnu-gcc: No such file or directory
  22. distcc[19970] ERROR: compile src/iniparser.c on localhost failed with exit code 110
  23. distcc[19973] (dcc_execvp) ERROR: failed to exec i686-pc-linux-gnu-gcc: No such file or directory
  24. make: *** [src/iniparser.o] Error 110
  25. make: *** Waiting for unfinished jobs....
  26. distcc[19974] (dcc_execvp) ERROR: failed to exec i686-pc-linux-gnu-gcc: No such file or directory
  27. distcc[19975] (dcc_execvp) ERROR: failed to exec i686-pc-linux-gnu-gcc: No such file or directory
  28. distcc[19972] ERROR: compile src/dictionary.c on localhost failed with exit code 110
  29. make: *** [src/dictionary.o] Error 110
  30. emake failed
  31.  * ERROR: dev-libs/iniparser-3.0b-r1 failed (compile phase):
  32.  *   emake failed
  33.  *
  34.  * Call stack:
  35.  *     ebuild.sh, line  85:  Called src_compile
  36.  *   environment, line 1836:  Called die
  37.  * The specific snippet of code:
  38.  *       emake CC=$(tc-getCC) AR="$(tc-getAR)" || die "emake failed"
  39.  *
  40.  * If you need support, post the output of 'emerge --info =dev-libs/iniparser-3.0b-r1',
  41.  * the complete build log and the output of 'emerge -pqv =dev-libs/iniparser-3.0b-r1'.
  42.  * The complete build log is located at '/var/tmp/portage/dev-libs/iniparser-3.0b-r1/temp/build.log'.
  43.  * The ebuild environment file is located at '/var/tmp/portage/dev-libs/iniparser-3.0b-r1/temp/environment'.
  44.  * S: '/var/tmp/portage/dev-libs/iniparser-3.0b-r1/work/iniparser3.0b'
  45.  
  46.  * Messages for package dev-libs/iniparser-3.0b-r1:
  47.  
  48.  * ERROR: dev-libs/iniparser-3.0b-r1 failed (compile phase):
  49.  *   emake failed
  50.  *
  51.  * Call stack:
  52.  *     ebuild.sh, line  85:  Called src_compile
  53.  *   environment, line 1836:  Called die
  54.  * The specific snippet of code:
  55.  *       emake CC=$(tc-getCC) AR="$(tc-getAR)" || die "emake failed"
  56.  *
  57.  * If you need support, post the output of 'emerge --info =dev-libs/iniparser-3.0b-r1',
  58.  * the complete build log and the output of 'emerge -pqv =dev-libs/iniparser-3.0b-r1'.
  59.  * The complete build log is located at '/var/tmp/portage/dev-libs/iniparser-3.0b-r1/temp/build.log'.
  60.  * The ebuild environment file is located at '/var/tmp/portage/dev-libs/iniparser-3.0b-r1/temp/environment'.
  61.  * S: '/var/tmp/portage/dev-libs/iniparser-3.0b-r1/work/iniparser3.0b'

Submit a correction or amendment below (click here to make a fresh posting)
After submitting an amendment, you'll be able to view the differences between the old and new posts easily.

Syntax highlighting:

To highlight particular lines, prefix each line with {%HIGHLIGHT}




All content is user-submitted.
The administrators of this site (kpaste.net) are not responsible for their content.
Abuse reports should be emailed to us at