On Tue, May 29, 2001 at 06:40:34PM +0000, Richard Adams wrote:
> On Tue, 29 May 2001, Mike Castle wrote:
> > The problem is libc.
> 
> As far as i see it, it is NOT a lib problem, anyway how could it be a libc
> problem when in this day and age we use "glibc".

libc IS glibc

nexus@thune[12:12pm]~(501) ls -l /lib/libc*
-rwxr-xr-x    1 root     root      4851005 May 29 12:09 /lib/libc-2.2.3.so

nexus@thune[12:12pm]~(502) ls -l /lib/glib*
ls: No match.

> > Many distributions have /usr/src/{asm,linux} as symlinks into the
> > /usr/src/linux/include heirarchy.
> 
> I think we need to know that its not a distribution who creates these symlinks
> but the actual make program itself, once again 'make mrproper' does this for us
> does it not.?. It was not so long ago that one needed to create these links
> him/herself.

That was a typo on my part.  And one I mistakenly carried though out the
mail.  Damn.

That should have read "man distributions have /usr/include/{asm,linux} as
                                                   ^^^^^^^
symlinks into the /usr/src/linux/include heirarchy."

> I think you have miss interpreted the whole point of this tread, no one
> mentioned "directorys" under "linux" as in /usr/src/linux, they (the ones you
> say) are all symlinks period. Header files reside in /usr/include which is then
> linked to /usr/src/linux/include/(whatever).

That's the thing.

There should be NO symlinks from /usr/include to
/usr/src/linux/include/(whatever).


> I just dont see the problem. Maybe my 10 years of Linux use is too much for me
> to understand just what the problem is that you/others think is there.?

And I've been using it for 7 years... your point?

mrc
-- 
       Mike Castle       Life is like a clock:  You can work constantly
  [EMAIL PROTECTED]  and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day.  -- mrc
    We are all of us living in the shadow of Manhattan.  -- Watchmen
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs

Reply via email to