Date: Thu, 20 Mar 1997 10:33:34 +1030 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: dennis@etinc.com (dennis) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG Subject: Re: Kernel Object Dependencies Message-ID: <199703200003.KAA29076@genesis.atrad.adelaide.edu.au> In-Reply-To: <3.0.32.19970319103544.00b208b0@etinc.com> from dennis at "Mar 19, 97 10:35:48 am"
next in thread | previous in thread | raw e-mail | index | archive | help
dennis stands accused of saying:
> >
> >Er, Dennis. While I understand your pique, this isn't very helpful.
> >Would you prhaps care to share with us an example that would help in
> >_fixing_ this?
...
> in files.i386:
>
> i386/isa/filename.o optional dn device-driver
>
> in configuration file:
>
> device dn0 at isa? port 0x240 net irq 11 vector dnintr
>
> generates the following dependency in the Makefile in the build directory....
>
> filename.o:
> -cp $S/i386/isa/filename.o .
>
> which should clearly be.....
>
> filename.o: $S/i386/isa/filename.o
> -cp $S/i386/isa/filename.o .
Er, no it doesn't. To wit :
files.i386:
i386/isa/mdsio.c optional mdsio device-driver
kernel config:
device mdsio0 at isa? port "IO_COM3" tty irq 10 vector mdsiointr
Makefile:
mdsio.o: $S/i386/isa/mdsio.c
${DRIVER_C}
This is on a 2.2 system. I have been taking advantage of the fact that
these dependancies _do_ work (and the opt_foo.h stuff too) to simplify
maintaining a number of kernels in parallel.
Are you doing 'make depend' after you config your kernel? It _is_
necessary in order to generate the dependancies. Sorry about not
replying last night; I ran out of typing juice 8(
> Dennis
--
]] Mike Smith, Software Engineer msmith@gsoft.com.au [[
]] Genesis Software genesis@gsoft.com.au [[
]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[
]] realtime instrument control. (ph) +61-8-8267-3493 [[
]] Unix hardware collector. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703200003.KAA29076>