From: Sam Ravnborg <sam@ravnborg.org>
To: Eric Sandeen <sandeen@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
hch@infradead.org, linux-kernel@vger.kernel.org,
linux-xfs@oss.sgi.com
Subject: Re: xfs: Makefile-linux-2.6 => Makefile?
Date: Tue, 17 Jan 2006 00:19:52 +0100 [thread overview]
Message-ID: <20060116231952.GA8752@mars.ravnborg.org> (raw)
In-Reply-To: <43C3E222.7020203@sgi.com>
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
next prev parent reply other threads:[~2006-01-16 23:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 16:42 Sam Ravnborg
2006-01-09 16:46 ` Christoph Hellwig
2006-01-09 17:19 ` Sam Ravnborg
2006-01-09 21:01 ` Sam Ravnborg
2006-01-09 21:05 ` Christoph Hellwig
2006-01-09 21:18 ` Sam Ravnborg
2006-01-09 21:03 ` Eric Sandeen
2006-01-09 21:20 ` Sam Ravnborg
2006-01-09 21:23 ` Eric Sandeen
2006-01-09 21:45 ` Sam Ravnborg
2006-01-10 7:45 ` Andrew Morton
2006-01-10 15:14 ` Eric Sandeen
2006-01-10 16:34 ` Eric Sandeen
2006-01-10 20:02 ` Sam Ravnborg
2006-01-16 23:19 ` Sam Ravnborg [this message]
2006-01-17 3:40 ` Eric Sandeen
2006-01-10 20:00 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060116231952.GA8752@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=sandeen@sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome