Re: Bug#2697: symlink /usr/include/asm in libc5-dev
On Wed, 17 Apr 1996, David Engel wrote:
> > When I get a new kernel, and re-make these symlinks, aren't the programs
> > that rely on the libc5 setup going to fail to build behind the now broken
> > libc5 links? Why can't libc5 rely on the natural placement of these
> > header files, or at least verify that they are there before it breaks
> > them (avoiding the break if they are there is preferable)
>
> Take a look at the top-level, kernel Makefile. You'll see the
> following lines.
>
> TOPDIR := $(shell if [ "$$PWD" != "" ]; then echo $$PWD; else pwd; fi)
> HPATH = $(TOPDIR)/include
> HOSTCC =gcc -I$(HPATH)
> CC =$(CROSS_COMPILE)gcc -D__KERNEL__ -I$(HPATH)
>
> These lines accomplish two things. First, the TOPDIR part means you
> don't have to put your kernel source in /usr/src/linux. You can put
> it anywhere. For example, I put mine in /usr/src/linux-X.Y.Z.
> Second, the HPATH part means that the headers that came with that
> kernel are used instead of the ones in /usr/include/{asm,linux}. I've
> been doing it this way on my system for >9 months. Believe me, it
> works.
>
So, I've been wasting my time, being very careful to remake these links
every time I get a new kernel, and the documentation with the kernel is
stale? Sounds like normal development software to me :-)
Thanks for the info,
Dwarf
------------ --------------
aka Dale Scheetz Phone: 1 (904) 877-0257
Flexible Software Fax: NONE
Black Creek Critters e-mail: dwarf@polaris.net
------------ If you don't see what you want, just ask --------------
Reply to: