On Sun, Jul 04, 2004 at 03:45:38AM +0900, GOTO Masanori wrote: > At Fri, 2 Jul 2004 21:40:11 -0700, > John Wong wrote: > > > At Sat, 27 Sep 2003 04:39:53 -0400, > > > Andrew K. Bressen wrote: > > > > I'm running an x86 debian system, mostly woody with a few sarge > > > > packages. > > > > The transition from libc6 and locales 2.3.1-16 to 2.3.2-7 broke > > > > non-debian stuff for me too; I had to back it out. > > > > > > > > Among the affected apps were compupic (v5.1 build 1063), > > > > netrek (Paradise Client 2000rc2) and unison (static textui 2.9.1). > > > > > > > > All are static compiles, and strace seemed to indicate > > > > things were breaking at or just after nss stuff; > > > > a strace of compupic follows... > > > > > > > > I have a system that I could roll the change back into temporarily > > > > if further testing is desired. > > > > > > We have 2.3.2.ds1-13. It's upper version of 2.3.2. However, NSS code > > > was changed in 2.3.2.ds1-1 and many static linked application was > > > broken. We can't fix this problem. If you want to use such > > > applications, please use LD_LIBRARY_PATH environment variable to point > > > to the old glibc 2.3.1 extracted directory. > > > > > > I think there's no bug in glibc. The workaround LD_LIBRARY_PATH > > > should avoid your problem. If you have no objection, I'll close this > > > bug. > > > > I can't test this solution now since the sarge system was rolled back to > > woody with a reinstall. > > I have experience to make commercial apps work with this technique. > So I guess it can be appliable for you, so I believe this bug can be > closed without any changes for glibc. Can I close this bug? Or do > you have any ways to investigate this problem? We can't touch this > bug without any sources, test programs or information.
Yes, close this bug as the problem is not with glibc. John > Regards, > -- gotom
