This one seems /really/ borked up! 1) The confcache patch fails on what is now the separate sandbox package. Patch skipped. 2) >>> Install portage-2.0.51.20-r1 into /tmp/portage/portage-2.0.51.20-r1/image/ category sys-apps * * Portage does not have an arch-specific configuration for this arch. * Please notify the arch maintainer about this issue. Using generic. * 3) Still in the install step: file: symbol lookup error: /usr/lib64/libsandbox.so: undefined symbol: egetcwd usr/lib/portage/bin/fixpackages x86_64-pc-linux-gnu-strip: /tmp/portage/portage-2.0.51.20-r1/image/usr/lib/portage/bin/fixpackages: File format not recognized usr/lib/portage/bin/fixpackages x86_64-pc-linux-gnu-strip: /tmp/portage/portage-2.0.51.20-r1/image/usr/lib/portage/bin/fixpackages: File format not recognized usr/lib/portage/bin/fixpackages x86_64-pc-linux-gnu-strip: /tmp/portage/portage-2.0.51.20-r1/image/usr/lib/portage/bin/fixpackages: File format not recognized readelf: Error: Unable to read in 0x4620 bytes of section headers readelf: Error: Not an ELF file - it has the wrong magic bytes at the start file: symbol lookup error: /usr/lib64/libsandbox.so: undefined symbol: egetcwd usr/lib/portage/bin/dispatch-conf-dialog x86_64-pc-linux-gnu-strip: /tmp/portage/portage-2.0.51.20-r1/image/usr/lib/portage/bin/dispatch-conf-dialog: File format not recognized usr/lib/portage/bin/dispatch-conf-dialog x86_64-pc-linux-gnu-strip: /tmp/portage/portage-2.0.51.20-r1/image/usr/lib/portage/bin/dispatch-conf-dialog: File format not recognized usr/lib/portage/bin/dispatch-conf-dialog x86_64-pc-linux-gnu-strip: /tmp/portage/portage-2.0.51.20-r1/image/usr/lib/portage/bin/dispatch-conf-dialog: File format not recognized readelf: Error: Unable to read in 0x6f74 bytes of section headers readelf: Error: Not an ELF file - it has the wrong magic bytes at the start ... and on and on and on, many similar errors, ending with a long string of unbroken libsandbox.so undefined symbol egetcwd errors (as above). Reproducible: Always Steps to Reproduce: The first couple times I tried merging, I had worse problems and it left me with an unworking portage. It would start an emerge, calculate deps, then go into a high CPU usage mode until killed. Luckily I use the buildpkg FEATURE, and was able to untarbz2 a copy of my last portage, portage-2.0.51.19, over top of my live system. Of course, sandbox was then dead, but I could FEATURES=-sandbox to try remerging sandbox and portage once again. Eventually, I got it working good enough I could emerge the new portage over itself, without disabling sandbox. Many of the emerge errors for the previous runs persisted, however, and those are reported above. emerge info to be attached (if /it/ works now <g>).
Created attachment 57016 [details] emerge info output
1) The confcache patch is not supported with 2.0.51. 2) Yep. Small error which would have given you an x86-like make.conf.example. Has been fixed. 3) Something weird going on with the sandbox, it seems. Have dropped keywording for other archs until they can test.
Can you try emerging sandbox with CFLAGS="-O1 -pipe" and see if that fixes it?
I had package-masked 20-r1 and gone back to .19. So, I umasked it again and tried again, with CFLAGS="-march=k8 -O1 -pipe" emerge sandbox. Even from .19, sandbox had similar errors: make[1]: Leaving directory `/tmp/portage/sandbox-1.2/work/sandbox-1.2-amd64' man: prepallstrip: strip: x86_64-pc-linux-gnu-strip --strip-unneeded strip: x86_64-pc-linux-gnu-strip --strip-unneeded file: symbol lookup error: /usr/lib64/libsandbox.so: undefined symbol: egetcwd usr/bin/sandbox usr/bin/sandbox usr/bin/sandbox file: symbol lookup error: /usr/lib64/libsandbox.so: undefined symbol: egetcwd usr/lib64/libsandbox.la x86_64-pc-linux-gnu-strip: /tmp/portage/sandbox-1.2/image/usr/lib64/libsandbox.la: File format not recognized usr/lib64/libsandbox.la x86_64-pc-linux-gnu-strip: /tmp/portage/sandbox-1.2/image/usr/lib64/libsandbox.la: File format not recognized usr/lib64/libsandbox.la x86_64-pc-linux-gnu-strip: /tmp/portage/sandbox-1.2/image/usr/lib64/libsandbox.la: File format not recognized readelf: Error: Unable to read in 0x7265 bytes of section headers readelf: Error: Not an ELF file - it has the wrong magic bytes at the start file: symbol lookup error: /usr/lib64/libsandbox.so: undefined symbol: egetcwd usr/lib64/libsandbox.so.0.0.0 usr/lib64/libsandbox.so.0.0.0 usr/lib64/libsandbox.so.0.0.0 making executable: /usr/lib64/libsandbox.so.0.0.0 >>> Completed installing sandbox-1.2 into /tmp/portage/sandbox-1.2/image/ However, looking at the binpkg created (since I use FEATURES=buildpkg), I think I see the issue. amd64 is a dual-bitness arch by default with 2005.0, and /should/ be installing a 32-bit libsandbox.so to /usr/lib, as well as the 64-bit version to /usr/lib64. The 32-bit version is missing from the sandbox package. Therefore, I think portage is trying to use unmatched versions for the 32-bit and 64-bit stuff, and that's creating issues! Give me an ebuild that creates the 32-bit lib as well, and we'll see if THAT fixes the errors! (Going to bed and then to work. I'll check back in ~14 hours, if I'm not too tired by then to make sense of things.)
upgrade to sandbox-1.2.1 *** This bug has been marked as a duplicate of 90153 ***
Utilizing this bug to track the progress of this specific bug as this is the first report.
multilib code doesnt seem to be working quite right ... care to check it out eradicator ? otherwise all the other issues should be resolved ...
should be exporting HAVE_64BIT_ARCH="${MULTILIB}" instead of fooling with cflags, 1.2.1-r2 is in cvs now.
Confirmed fixed, portage-2.0.51.20-r3 and sandbox-1.2.1-r2, here. Thanks for all the hard work! It works, now!
