rpm & glibc catch22

Chong Yu Meng chongym
Mon May 17 11:56:17 PDT 2004


Hmm...

My understanding is that rpm 4.x works with glibc 2.3.x. At least, 
that's what I'm using on my RH9 system. I used rpm 3.x on my TurboLinux 
server which was running the older glibc 2.2.x. Didn't upgrade my rpm 
then, so I cannot tell you if it will work or not.

Regards,
pascal chong



Net Llama! wrote:

> A week ago I upgraded glibc from 2.2.5 to 2.3.2, without any problems. 
> I forgot at the time that glibc upgrades tend to break rpm.  So today 
> I was pleasantly reminded of that fact when I attempted to rebuild a 
> SRPM, and rpm just segfaulted.
>
> I've been down this road before, although not neccerily with the same 
> versions of glibc or rpm.  On the current box, i have rpm-3.0.6, and 
> my understanding is that this is the only version that is compatible 
> with both rpm-3.x & rpm-4.x, so moving to rpm-4.x would not be an 
> option, unless I wanted to toss my rpm database goodbye, and start 
> from scratch.  So, i'm attempting to build rpm-3.0.6, however make 
> keeps bombing out:
>
> /usr/bin/gcc-2.95.3 -DHAVE_CONFIG_H -I. -I. -I. -I. -g -O2 -c popt.c 
> -fPIC -DPIC -o .libs/popt.lo
> popt.c: In function `poptGetNextOpt':
> popt.c:596: `FLT_MAX' undeclared (first use in this function)
> popt.c:596: (Each undeclared identifier is reported only once
> popt.c:596: for each function it appears in.)
> popt.c:598: `FLT_MIN' undeclared (first use in this function)
> make[4]: *** [popt.lo] Error 1
> make[4]: Leaving directory `/home/netllama/stuff/rpm-3.0.6/popt'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/home/netllama/stuff/rpm-3.0.6/popt'
> make[2]: *** [all-recursive-am] Error 2
> make[2]: Leaving directory `/home/netllama/stuff/rpm-3.0.6/popt'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/netllama/stuff/rpm-3.0.6'
> make: *** [all-recursive-am] Error 2
>
> From what i've found by Googling, this is caused by either a botched 
> glibc, or borked /usr/include/[linux,asm,scsi] symlinks.  Well, the 
> symlinks are definitely ok, and while i'm not 100% certain, i think my 
> glibc is fine, seeing as how everything else works just fine on this 
> box.  So, i'm wondering if rpm-3.0.6 is just too old to build against 
> glibc-2.3.2.
>
> Anyone have the wisdom to shine any light on this conundrum?
>



More information about the Linux-users mailing list