This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
unresolved symbols when link an application statically
- From: Alexey Morozov <morozov at novosoft dot ru>
- To: libc-alpha at sources dot redhat dot com
- Date: Wed, 16 Apr 2003 12:43:11 +0700
- Subject: unresolved symbols when link an application statically
Hi!
First of all I have to be your pardon, if I send this mail to the wrong
ML. Anyway, I coudn't find a glibc list completely suitable for my
problem.
Yesterday, I tried to compile my application statically against
RedHat8's libc (glibc-2.3.2-4.80) and Oracle9 OCI libraries
(libclntst9.a, 9.2.0.1) (that's my customer requirement). I got error
messages like these:
/opt/oracle/lib/libclntst9.a(kgl.o): In function `kglpdn':
kgl.o(.text+0xf312): undefined reference to `__ctype_toupper'
kgl.o(.text+0xf437): undefined reference to `__ctype_b'
...
After performing a small googling, I found the following discussion in
the debian-glibc ML
http://lists.debian.org/debian-glibc/2002/debian-glibc-200210/msg00093.html
I got the source RPM for RH glibc and saw that RH had already patched
ctype-info.c ("compat-symbol" lines are under #if 0), so everything
should be Ok now, but it's not. Unfortunately I'm not a glibc-internals
guru and can't quickly understand how to fix things. So if anybody help
me to solve the problem, I'll be very gladful
Alexey Morozov