glibc

[Brian Densmore]

Hal,
	That brings up an interesting point. Since I'm recompiling the
kernel and the modules, do I need to move/link the new headers to
/usr/src/linux. Or does that just apply to changes in glibc and
libraries? Like if I compile a new version of glibc.

Thanks for the knowledge assist,
Brian

> -----Original Message-----
> From: Duston, Hal [mailto:hdusto01 at sprintspectrum.com]
> Sent: Friday, November 30, 2001 12:03 PM
> To: Brian Densmore
> Subject: RE: Kernel compile problems
> 
> 
> Brian,
> 
> Glibc is the main library used by nearly every program on 
> the system.  (Including rm, cp, and mv).  It was compiled 
> with a specific set of /usr/src/linux/include headers. 
> When you compile other stuff, they generally need to be 
> compiled with the same set of headers, hence my leaving 
> them alone.  And yes, all it need to compile other things 
> is the headers.
> 
> You can use `ldd /bin/mv' to see that libraries a binary 
> generally uses.  The list from that command will be complete
> unless one of the libaries listed is libdl.so.  That allows 
> a program to add even more libraries after it is running.
> 
> glibc show up labeled as libc.so.6.
> ld-linux.so.2 is the loader.
> 
> Hal
> 
> Brian Densmore [mailto:DensmoreB at ctbsonline.com] wrote:
> > 
> > Hal,
> > 
> >  Thanks! That's exactly what I wanted to hear. 
> > Interesting though, All I have in my /usr/src/linux 
> > directory is a tar.gz file of the Linux headers (I 
> > think that's all it has - I know I need to untar it to
> > compile anything), which untars to those two directories 
> > you mentioned.  What does glibc do anyway? It's some 
> > kind of library manager or something right?
> > 
> > Thanks,
> > Brian
>