Summary: | glibc-2.3.5 fails to build-x86-x86_64-pc-linux-gnu-linuxthreads with unresolved symbols in libpthread.so | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ron Sommers <rsommers2> |
Component: | [OLD] Core system | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | eradicator, hvjunk |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ron Sommers
2005-04-22 19:20:54 UTC
Well another bogus bug same problem I was having with wine. I had a bothced set of emul-x86 files in /emul/linux/x86/usr/lib/ Funny how they never were a problem before. Maybe the new emul-2.1 files missed uninstalling them. I will list them for posterity Mcrt1.o libbsd.a libnsl.a Scrt1.o libc.a libpthread.a crt1.o libc.so libpthread.so crti.o libc_nonshared.a libpthread_nonshared.a crtn.o libcrypt.a libresolv.a gcrt1.o libdl.a librpcsvc.a libBrokenLocale.a libg.a librt.a libGL.la libieee.a libutil.a libanl.a libm.a libz.so libbsd-compat.a libmcheck.a misc <---- folder These files were left over from something. Cause all my emul has been updated and my gcc glibc has been rebuilt since 03/06/2005. And I'm on 2005.0 amd64 rebuilt from the ground up. *** Bug 96608 has been marked as a duplicate of this bug. *** any idea what could cause/fix this? this bug is quite old, perhaps it has gone away with 2.3.5-r2? no answer for over a month, assuming the problem has gone |