I'm running kernel 2.6.0-test5-mm1 and glibc-2.3.2-r4 with nptl. The errno
badness hit Kylix because I get the following error:
/opt/kylix3/bin/bcblin: relocation error: /opt/kylix3/bin/libwine.borland.so:
symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time
If I try the LD_ASSUME_KERNEL=2.4.0 workaround, I get:
bcblin: error while loading shared libraries: libpthread.so.0: cannot open
shared object file: No such file or directory
I did install the Kylix-fixes on
but that doesn't alleviate the problem, alas.
Badness in libcompat? Something I'm missing?
Steps to Reproduce:
1. source /opt/kylix3/bin/kylixpath
2. export LD_ASSUME_KERNEL=2.4.0
Error messages listed above.
I've got Kylix3 running under SuSE 8.2 so this isn't a major blocker. It would
just be nice if I could get it running at home too!
Then you have to drop NPTL and downgrade to glibc-2.3.1, although
I WOULD _NOT_ RECOMMEND IT, as things will break. Only way I see to use
glibc-2.3.1 safely, will be to reinstall.
This is a 'cannot fix' as far as I am concerned. As Kylix is closed source,
we unfortunately have to wait for them to fix it :(
I downgraded to glibc 2.3.2 without nptl and so far so good. Kylix works, so I guess this is an nptl issue. Also, since C++BuilderX has been released (which uses gcc and icc, I might add!), I wonder if they'll ever update Kylix...
Would there be a way to make a compat-libc to fix broken binaries like this? Where would the clashes be if two libc's are installed on a system?
Look, since Borland's got a proprietary compiler with a proprietary C++, it's the least of my worries if Kylix doesn't run on my Gentoo box. But if this bug bites binary-only Linux games, I'm going to be very upset!