Summary: | glibc-2.3.5 fails-> "lib32/libsandbox.so: undefined symbol: __dlsym" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sebastian Spaeth <Sebastian> |
Component: | New packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | amd64, azarah, eradicator |
Priority: | High | ||
Version: | 2005.0 | ||
Hardware: | AMD64 | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sebastian Spaeth
2005-04-28 03:51:23 UTC
btw, default-linux/amd64/2005.0 is not "pure 64bit". If you want a 32bit free system, use 2005.0/no-multilib... Can you please try rebuilding sys-apps/sandbox? What version of sandbox are you using? I re-emerged sandbox already. No change. still not working. emerge info was already provided :) sys-apps/sandbox: 1.2.1-r3 Thanks for the no-multilib tip. I'll try that soon... Can you please try sandbox-1.2.3? sys-apps/sandbox-1.2.3 is installed now. Exact same error as reported above when emerging glibc. I am assuming that is the 64bit glibc building .. should it then be using the 32bit sandbox lib? Jeremy, ideas? yes, when executing 32bit programs, it uses the 32bit libsandbox... so this is probably when compiling the 32bit glibc... I really wish I could see the line above the top of your log. You need to atleast show the whole command that causes the failure... Sorry, I tried the no-multilib profile (after this bug occurred on a "normal" box), noticed that I still need multilib to run openoffice, and tried to go back. Have a hell of a time right now and can't do reliable and sane tests now. I'll let this bug suspend for a while and report back, once the machine is back in a sane state. Sorry for the delay... Jeremy, its not maybe because the full path is not used to open libc, etc? With the new tests, the issues involved with that may be of the past (can't remember the exact issues)? Not using the full path uses the ld.so.cache, and it's grabbing the one in /usr/lib32/libsandbox.so which is where sys-apps/sandbox installs itself to... The thing is... I don't have that symbol in my 32bit libsandbox, so I'm a bit confused how he's got it. $ readelf -s /usr/lib32/libsandbox.so | grep dl 17: 00000000 170 FUNC GLOBAL DEFAULT UND dlvsym@GLIBC_2.1 (4) 24: 00000000 158 FUNC GLOBAL DEFAULT UND dlsym@GLIBC_2.0 (5) 56: 00000000 618 FUNC GLOBAL DEFAULT UND dlerror@GLIBC_2.0 (5) Sebastian, are you still suffering from this? I have sandbox 1.2.11 installed now and glibc 2.3.5 worked fine at a later stage (don't know exactly when though). Feel free to close from my point of view k ... |