Re: kbuild 2.5 is ready for inclusion in the 2.5 kernel

tomas szepe (kala@pinerecords.com)
Fri, 3 May 2002 01:25:55 +0200

> > '/usr/include/asm' points to '/usr/src/linux/include/asm', which doesn't
> > exist at this moment. It seems to me that kbuild 2.5 makes the assumption
> > that the 'asm' symlink in /usr/include already determines the machine
> > architecture type by pointing to a concrete asm-$arch
> > in /usr/src/linux/include.
> Sigh... Configurations with /usr/include/{linux,asm} being symlinks
> are BROKEN. Please, look through the archives - it had been discussed
> a lot of times. Userland has no business using kernel headers directly
> and that's precisely what had bitten you - setup where /usr/include/asm
> comes not from libc but from the (currently being built) kernel.

My apologies then... Actually, this is how Slackware-8.0 came (and
slackware-current AFAIK still comes). Apparently I must've missed
the transition, and so has Patrick Volkerding.

Also I'm sorry for bringing up the MODVERSIONS issue. If I had known
what flamewar it would trigger, I'd never have raised the topic. *sigh*

Now let's see what's to be found in glibc-2.2.5.tar.gz. :)

-Tomas

-- 
"hello it's not like i read my mail so that you have where to offer to sell me
a giant turnip or anything else thankyou." -tomas szepe <kala@pinerecords.com>          
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/