Greetings,
I recently upgraded glibc on my Linux box from glibc-2.2.5 to glibc-2.3.2 (built from source). Unfortunately, this broke some rpm functionality. In the past when this has happened (after upgrading glibc), I was able to rebuild rpm without too much of a problem. Unfortunately, there seems to be an incompatibility between glibc-2.3.2 and rpm-4.x where 'make' is bombing out here:
/usr/local/bin/gcc3 -O2 -funroll-loops -ffast-math -fomit-frame-pointer -fno-exceptions -D_GNU_SOURCE -D_REENTRANT -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wno-char-subscripts -o rpm -static rpm.o ./build/.libs/librpmbuild.a ./lib/.libs/librpm.a ./rpmdb/.libs/librpmdb.a ./rpmio/.libs/librpmio.a -L/usr/local/lib -lz -lbz2 ./popt/.libs/libpopt.a
./lib/.libs/librpm.a(rpmchecksig.o)(.text+0x64b): In function `rpmReSign':
: warning: the use of `mktemp' is dangerous, better use `mkstemp'
/usr/lib/libbz2.a(bzlib.o)(.text+0x2a22): In function `bzopen_or_bzdopen':
: undefined reference to `__ctype_b'
collect2: ld returned 1 exit status
make[2]: *** [rpm] Error 1
make[2]: Leaving directory `/home/netllama/stuff/rpm-4.0.3'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/netllama/stuff/rpm-4.0.3'
make: *** [all-recursive-am] Error 2
I did quite a bit of googling, but unfortunately, the best I could find was this redhat bug report (i'm not using Redhat, but a linux distro that i built from scratch):
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=86465
It appears to talk about how __ctype_b was a symbol used in glibc's locale handling function, __ctype_b_loc(). However, the symbol has been removed. Comment #18 in the bugzilla report suggests a workaround: create a file named ctype_b.c that has the contents listed, somehow add it to the project, and rebuild the project. By adding this file, it will
cause __ctype_b to be found, presumably fixing the build failure. Unfortunately, i'm way out of my league in even figuring out how to add ctype_b.c to the rpm build process, and even if i knew how to do that, I'm not fully convinced it would solve the current problem.
So, i'm at the end of my virtual rope here. Does anyone have any suggestions on how I can successfully build rpm? thanks!
This is bzip2, not rpm, problem. Upgrade or rebuild bzip2.
73 de Jeff
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
