[Fwd: [ale] Re: modules fail symbol lookup]

[michael mcdermott]

arrrghhh
I could have sworn i was allready using the latest version of glibc

Thanks, I will try that over the holidays


Benjamin Scherrey wrote:
> 
> Yes - anyone moving to the new kernels needs to move to glib rather than
> libc5. This is going to be tougher on the slackware and debian folks than
> it is the redhat users (AFAIK) but its well worth the effort once done.
> People moving from libc5 will have to rebuild a lot of their code.
> Unfortunately, this often causes people to believe that glib is less
> stable than libc5 was but that really isn't the case at all. Better start
> getting ready for 2.2 now....
> 
>     regards,
> 
>         Ben Scherrey
> 
> "Eric Z. Ayers" wrote:
> 
> > Someone was asking about problems after installing the
> > modutils-2.1.121 with kernel symbols not being recognized.
> >
> > I just upgraded a slackware (old) box to use the 2.1.131.  I upgraded
> > all the stuff mentioned in the 'Changes' file, but kept getting the
> > same errors when I tried to load in modules I had built.
> >
> > After a lot of pain upgrading to the latest binutils + the latest
> > libc5 + the latest everything else mentioned in the Changes file
> > (except I didn't upgrade gcc past 2.7.2)

-- 
"Don't make me use the spank ray"      -Tad Ghostal