On Tue, Jan 10, 2006 at 10:34:42AM -0600, Eric Sandeen wrote:
> Andrew Morton wrote:
> >It'd be nice to fix this:
> >
> >bix:/usr/src/25> make fs/xfs/linux-2.6/xfs_iops.o
> > SPLIT include/linux/autoconf.h -> include/config/*
> > SHIPPED scripts/genksyms/lex.c
> > SHIPPED scripts/genksyms/parse.h
> > SHIPPED scripts/genksyms/keywords.c
> > HOSTCC scripts/genksyms/lex.o
> > SHIPPED scripts/genksyms/parse.c
> > HOSTCC scripts/genksyms/parse.o
> > HOSTLD scripts/genksyms/genksyms
> > HOSTCC scripts/mod/file2alias.o
> > HOSTCC scripts/mod/modpost.o
> > HOSTLD scripts/mod/modpost
> >scripts/Makefile.build:15: /usr/src/devel/fs/xfs/linux-2.6/Makefile: No
> >such file or directory
> >make[1]: *** No rule to make target
> >`/usr/src/devel/fs/xfs/linux-2.6/Makefile'. Stop.
> >make: *** [fs/xfs/linux-2.6/xfs_iops.o] Error 2
>
> Hm, maybe Sam can correct me if I'm wrong, but I'm not sure that kbuild
> will support more than one Makefile/Kbuild file per module; so if we have
> some code in a subdirectory, I think it all needs to be driven from the
> parent directory's Makefile... and then the above doesn't work.
>
> Sam, is there any way to make this work with some code for the module in a
> subdirectory?
Hi Eric.
I forgot to point out one ugly solution for this.
You can include a dummy Kbuild (Makefile) in each directory to support
this. I recall that reiser4 had similar question and this was the
solution I pointed out for them too.
No - I am not in favour of it. But for local development it could make
sense.
So it may solve the "Eric" part of it, but not the "Andrew" part of it
since these file will never get in the mainstream kernel (hopefully).
Sam
|