Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 31507 - failures preloading libsandbox.so on dual 32/64bit environments
Summary: failures preloading libsandbox.so on dual 32/64bit environments
Status: RESOLVED DUPLICATE of bug 32963
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-19 07:54 UTC by Brad House
Modified: 2011-10-30 22:19 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brad House 2003-10-19 07:54:50 UTC
ok, well, just going to cut and paste out of a IRC post:
<brad_mssw> wondering if this change is feasible:
<brad_mssw> on amd64 you can have a dual 64bit/32bit environment...  some applications are 32bit only
<brad_mssw> for the sake of this explanation, I'll strictly be referring to java
<brad_mssw> which is binary-only, so it must be 32bit (and sun-j2sdk won't yet compile, so the binary packages are our only choice)
<brad_mssw> anyhow, the way libsandbox.so works, it gets preloaded before any executable gets called for each executable
<brad_mssw> the problem with this is libsandbox.so is a 64bit shared object
<brad_mssw> when a 32bit executable such as 'javac' gets called while compiling say db-4.0.12, it fails because the 32bit 'javac' can't preload the 32bit libsandbox.so
<brad_mssw> I was wondering if it's feasible to compile 2 libsandboxes (1 32bit and 1 64bit) and dynamically choose which one gets loaded depending on the executable type
<brad_mssw> anyhow, that's my question ....
Comment 1 Brad House 2003-11-16 12:38:36 UTC

*** This bug has been marked as a duplicate of 32963 ***