Re: relocation error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol __libc_readline_unlocked version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

2019-03-25 Thread stupidate
lowing error? > > > "relocation error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol > __libc_readline_unlocked version GLIBC_PRIVATE not defined in file libc.so.6 > with link time reference" > > > > > After the libc6:amd64 (2.27-8, 2.28-1) update, I c

relocation error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol __libc_readline_unlocked version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

2018-12-03 Thread Office onFocus
Hi! How can I correctly report the following error? "relocation error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol __libc_readline_unlocked version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference" After the libc6:amd64 (2.27-8, 2.28-1) update, I can no lo

Re: version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

2009-08-11 Thread Sven Joachim
On 2009-08-11 19:15 +0200, Rob Gom wrote: > [cut] > I compared libnsl versions, not libc. I see, I had misunderstood you. Yes, nm lists __libc_clntudp_bufcreate as undefined in libnsl. > I _guess_ that some lib is linked against libnsl, but not libc6 (is > that possible?). Theoretically it may

Re: version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

2009-08-11 Thread Rob Gom
[cut] I compared libnsl versions, not libc. I _guess_ that some lib is linked against libnsl, but not libc6 (is that possible?). Then on older versions, it would work fine. On new, it would try to load libnsl and fail because on new referred symbol present in libc6. What else may that be? I restar

Re: version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

2009-08-11 Thread Sven Joachim
On 2009-08-11 16:21 +0200, Rob Gom wrote: > On Tue, Aug 11, 2009 at 2:40 PM, Rob Gom wrote: >> I workarounded that by copying old libnsl-2.7.so to /lib (and second >> version to /lib/i686/cmov/) and modified symbolic links libnsl.so.1. >> And smb access started working again ... >> Shall I report

Re: version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

2009-08-11 Thread Rob Gom
On Tue, Aug 11, 2009 at 2:40 PM, Rob Gom wrote: > I workarounded that by copying old libnsl-2.7.so to /lib (and second > version to /lib/i686/cmov/) and modified symbolic links libnsl.so.1. > And smb access started working again ... > Shall I report a bug against libc6? > > Regards, > Robert > I d

Re: version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

2009-08-11 Thread Rob Gom
I workarounded that by copying old libnsl-2.7.so to /lib (and second version to /lib/i686/cmov/) and modified symbolic links libnsl.so.1. And smb access started working again ... Shall I report a bug against libc6? Regards, Robert -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org

Re: version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

2009-08-11 Thread Rob Gom
On Tue, Aug 11, 2009 at 11:45 AM, Sven Joachim wrote: [cut] > > That does not seem to happen for me: > > , > | % objdump -T /lib/i686/cmov/libc.so.6 | grep __libc_clntudp_bufcreate > | 0010ad30 g    DF .text  0399  GLIBC_PRIVATE __libc_clntudp_bufcreate > ` > >> What can I do with that?

Re: version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

2009-08-11 Thread Sven Joachim
stay with that version - it's fine for my purposes). Log > message is: > Could not open library '/usr/lib/kde3/kio_smb.la'. > /lib/i686/cmov/libnsl.so.1: symbol __libc_clntudp_bufcreate, version > GLIBC_PRIVATE not defined in file libc.so.6 with link time refe

version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

2009-08-11 Thread Rob Gom
ssage is: Could not open library '/usr/lib/kde3/kio_smb.la'. /lib/i686/cmov/libnsl.so.1: symbol __libc_clntudp_bufcreate, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference What can I do with that? Does it seem to be a KDE3 bug or libc6 bug? I searched google but