Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 634200 - sys-apps/sandbox-2.12 fail to emerge, due to error during install phase: multilib-strict check failed!
Summary: sys-apps/sandbox-2.12 fail to emerge, due to error during install phase: mult...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Sandbox Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-13 19:59 UTC by Sven E.
Modified: 2017-10-28 03:54 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge.info,5.30 KB, text/plain)
2017-10-27 16:47 UTC, Sven E.
Details
build.log (build.log,165.70 KB, text/plain)
2017-10-27 16:51 UTC, Sven E.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sven E. 2017-10-13 19:59:41 UTC
sys-apps/sandbox-2.12 bails out during install phase with:

 * ERROR: sys-apps/sandbox-2.12::gentoo failed:
 *   multilib-strict check failed!

Reproducible: Always

Steps to Reproduce:
1. emerge sandbox
2. error during install phase

Actual Results:  
install phase fails

Expected Results:  
clean install

I've multiple systems where the problem occurs and others, where it does not.

What seems to be common among all systems having problems so far is, that they are VM guests.

One system that fails is a VirtualBox guest.
Two failing systems are VMware guests.

However install phase succeeds on a KVM guest.

All Systems have the same CHOST and are KEYWORDED with ~amd64.
Comment 1 Ian Stakenvicius (RETIRED) gentoo-dev 2017-10-27 15:02:40 UTC
Can you please attach all the usual suspects -- build.log, emerge --info ?
Comment 2 Sven E. 2017-10-27 16:47:02 UTC
Created attachment 500428 [details]
emerge --info
Comment 3 Sven E. 2017-10-27 16:51:14 UTC
Created attachment 500430 [details]
build.log
Comment 4 Mike Gilbert gentoo-dev 2017-10-28 01:56:38 UTC
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).
Comment 5 Sven E. 2017-10-28 03:54:07 UTC
(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.