summary says it all. some errors below, i think from the first one ---------- /bin/sh ../libtool --tag=CXX --mode=link x86_64-pc-linux-gnu-g++ -O2 -march=core2 -pipe -fomit-frame-pointer -mfpmath=sse -I/usr -I/usr/include/gpgme -I/usr/include/gpgme -L../connwrap -L../kkconsui -L../kkstrtext -L../kksystr -L../libicq2000 -L../libjabber -Wl,-O1 -o centerim centerim-centerim.o centerim-icqcontact.o centerim-icqgroups.o centerim-eventmanager.o centerim-icqdialogs.o centerim-icqhist.o centerim-imexternal.o centerim-imcontact.o centerim-imlogger.o centerim-accountmanager.o centerim-icqcontacts.o centerim-icqmlist.o centerim-imcontroller.o centerim-icqconf.o centerim-imevents.o centerim-impgp.o centerim-icqface.o centerim-centermain.o centerim-icqgroup.o centerim-captcha.o centerim-git-version.o ../src/hooks/libhooks.a -lkkconsui -lkkstrtext -lkksystr -llibicq2000 -llibjabber -lconnwrap -lncursesw -lnsl -lssl -L/usr/lib64 -lgpgme -L/usr/lib64 -lgpg-error -lcurl -ljpeg -lssl -L/usr/lib64 -lgpgme -L/usr/lib64 -lgpg-error -lcurl ../libtool: line 852: X--tag=CXX: command not found ../libtool: line 885: libtool: ignoring unknown tag : command not found ../libtool: line 852: X--mode=link: command not found ../libtool: line 1019: *** Warning: inferring the mode of operation is deprecated.: command not found ../libtool: line 1020: *** Future versions of Libtool will require --mode=MODE be specified.: command not found x86_64-pc-linux-gnu-gcc: no input files x86_64-pc-linux-gnu-gcc: no input files x86_64-pc-linux-gnu-gcc: no input files x86_64-pc-linux-gnu-gcc: no input files g++: no input files g++: no input files ../libtool: line 693: x86_64-pc-linux-gnu-x86_64-pc-linux-gnu-g++: command not found ../libtool: line 693: x86_64-pc-linux-gnu-x86_64-pc-linux-gnu-g++: command not found ../libtool: line 2264: X-O2: command not found ../libtool: line 2099: X-march=core2: command not found ../libtool: line 2264: X-pipe: command not found ../libtool: line 2264: X-fomit-frame-pointer: command not found ../libtool: line 2099: X-mfpmath=sse: command not found ../libtool: line 2264: X-I/usr: No such file or directory ../libtool: line 2264: X-I/usr/include/gpgme: No such file or directory ../libtool: line 2264: X-I/usr/include/gpgme: No such file or directory ../libtool: line 1978: X-L../connwrap: No such file or directory ../libtool: line 1978: X-L../kkconsui: No such file or directory ../libtool: line 1978: X-L../kkstrtext: No such file or directory ../libtool: line 1978: X-L../kksystr: No such file or directory ../libtool: line 1978: X-L../libicq2000: No such file or directory ../libtool: line 1978: X-L../libjabber: No such file or directory ../libtool: line 2227: X-Wl,-O1: command not found Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. ../libtool: line 1978: X-L/usr/lib64: No such file or directory ../libtool: line 1978: X-L/usr/lib64: No such file or directory ../libtool: line 1978: X-L/usr/lib64: No such file or directory ../libtool: line 1978: X-L/usr/lib64: No such file or directory ../libtool: line 2433: Xcenterim: command not found Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. ../libtool: line 2445: Xcenterim: command not found ../libtool: line 2453: mkdir /.libs: No such file or directory [31;01mACCESS DENIED[0m mkdir: /.libs mkdir: cannot create directory `/.libs': Permission denied make[3]: *** [centerim] Error 1 make[3]: Leaving directory `/var/tmp/portage/net-im/centerim-4.22.5/work/centerim-4.22.5/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/net-im/centerim-4.22.5/work/centerim-4.22.5/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/net-im/centerim-4.22.5/work/centerim-4.22.5' make: *** [all] Error 2 [31;01m*[0m [31;01m*[0m ERROR: net-im/centerim-4.22.5 failed. [31;01m*[0m Call stack: [31;01m*[0m ebuild.sh, line 49: Called src_compile [31;01m*[0m environment, line 2613: Called die [31;01m*[0m The specific snippet of code: [31;01m*[0m emake || die "emake failed" [31;01m*[0m The die message: [31;01m*[0m emake failed [31;01m*[0m [31;01m*[0m If you need support, post the topmost build error, and the call stack if relevant. [31;01m*[0m A complete build log is located at '/var/tmp/portage/net-im/centerim-4.22.5/temp/build.log'. [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/net-im/centerim-4.22.5/temp/environment'. [31;01m*[0m [31;01m--------------------------- ACCESS VIOLATION SUMMARY ---------------------------[0m [31;01mLOG FILE = "/var/log/sandbox/sandbox-24071.log"[0m mkdir: /.libs [31;01m--------------------------------------------------------------------------------[0m Reproducible: Always
Actually, summary says nothing. Full build log, please. Most important will probably be src_unpack phase, unless 'missing --run' was triggered.
Yes, as Rafal said. Additionally, please attach 'build.log', 'config.log', 'enviranment' file, and 'emerge --info' information and reopen.
Created attachment 163021 [details] emerge --info
Created attachment 163023 [details] build.log
Created attachment 163025 [details] environment
Created attachment 163026 [details] config.log
everything you wanted. no sandbox violation anymore (after a nights rest) and it seems to install, but e.g. the executable is missing
Well, 'missing --run' was triggered, so, looking at the build.log and the ebuild, I think changing 'eautoconf' to 'eautoreconf' should fix it.
(In reply to comment #8) > Well, 'missing --run' was triggered, so, looking at the build.log and the > ebuild, > I think changing 'eautoconf' to 'eautoreconf' should fix it. > Is this a change that will need to be changed by us end users in an overlay, or is it something that will be changed in the official ebuild in portage? I ask because I just attemtped to emerge centerim and received an almost identical error as the original submitter. I grep'd the build log file and saw 'missing --run' show up a few times.
I moved the ebuild into my overlay and modified it to change eautoconf to eautoreconf and the new ebuild compiled and installed with no problems at all.
Why ebuild not fixed yet?
Uhm, seems like I silently fixed it on 07 Nov 2008.