Summary: | sys-apps/sandbox-2.12 fail to emerge, due to error during install phase: multilib-strict check failed! | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sven E. <dark> |
Component: | Current packages | Assignee: | Sandbox Maintainers <sandbox> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | axs, floppym, whissi |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
build.log |
Description
Sven E.
2017-10-13 19:59:41 UTC
Can you please attach all the usual suspects -- build.log, emerge --info ? Created attachment 500428 [details]
emerge --info
Created attachment 500430 [details]
build.log
You have "-m64" in your CFLAGS. That is causing /usr/lib32/libsanbox.so to be built as a 64-bit object instead of a 32-bit object. In general, you should not add -m64 or -m32 to CFLAGS unless you are doing so for some specific, known purpose (like development/testing). (In reply to Mike Gilbert from comment #4) > You have "-m64" in your CFLAGS. That is causing /usr/lib32/libsanbox.so to > be built as a 64-bit object instead of a 32-bit object. > > In general, you should not add -m64 or -m32 to CFLAGS unless you are doing > so for some specific, known purpose (like development/testing). Ah I see. I added this a while back on one guest (and it propagated) since an older version of gcc did have some problems regarding -march and did not build 64 bit code at all. Stupid me. |