On Mon, 4 Jul 2005, Maciej W. Rozycki wrote:
> On Sat, 2 Jul 2005, Geert Uytterhoeven wrote:
> > > Looks like I am running procps version 2.0.7. The latest is 3.2.5, so I
> > > am
> > > a bit out of date. I would like to upgrade, but I am having trouble cross
> > > compiling the latest. I get this error:
> > > Proc/libproc-3.2.5.so: undefined reference to '__ctype_b'
> >
> > Is the version of glibc your cross-toolchain links against the same as the
> > version of glibc on the target?
> >
> > Last time I saw that one was when trying to run `old' (i.e. dynamically
> > linked
> > against an older glibc) binaries on a system with a new glibc.
>
> This is strange -- while there are such problems with static libraries
> (archives) consisting of objects built using headers of glibc 2.2.x when
> used for linking against static glibc 2.3.x, there should be none with
> shared objects. That '__ctype_b' reference should get resolved using a
> versioned symbol that is still available for run-time linking from shared
> libc. Perhaps that libproc has been built incorrectly, without a
> reference to libc? Or there is a problem with binutils...
Oops, I was wrong.
I was not running old applications, but linking an old *.a or *.o file using a
new glibc.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|