From: Sam Ravnborg <sam@ravnborg.org>
To: Christian Hesse <mail@earthworm.de>
Cc: linux-kernel@vger.kernel.org, James Ketrenos <jketreno@linux.intel.com>
Subject: Re: build system: no module target ending with slash?
Date: Thu, 3 May 2007 08:15:33 +0200 [thread overview]
Message-ID: <20070503061533.GA13399@uranus.ravnborg.org> (raw)
In-Reply-To: <20070503042511.GB12644@uranus.ravnborg.org>
On Thu, May 03, 2007 at 06:25:11AM +0200, Sam Ravnborg wrote:
> On Thu, May 03, 2007 at 12:43:43AM +0200, Christian Hesse wrote:
> > Hi James, hi everybody,
> >
> > playing with iwlwifi I try to patch it into the kernel and to build it from
> > there. But I have a problem with the build system.
> >
> > The file drivers/net/wireless/mac80211/Makefile contains one single line:
> >
> > obj-$(CONFIG_IWLWIFI) += iwlwifi/
> >
> > When CONFIG_IWLWIFI=m in scripts/Makefile.lib line 29 the target is filtered
> > as it ends with a slash. That results in
> > drivers/net/wireless/mac80211/built-in.o not being built and the build
> > process breaks with an error. What is the correct way to handle this? Why are
> > targets ending with a slash filtered?
>
> Looks buggy. I will take a look tonight.
After some coffee...
Line 29 in Kbuild.include find all modules and a directory is not a module.
In line 26 in same file the directory iwlwifi is included in the list
of directories to visit.
So there is something else going on.
Anywhere I can get access to the combined source or could you try to post the full
Makefile.
Sam
next prev parent reply other threads:[~2007-05-03 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 22:43 build system: no module target ending with slash? Christian Hesse
2007-05-03 4:25 ` Sam Ravnborg
2007-05-03 6:15 ` Sam Ravnborg [this message]
2007-05-03 7:17 ` Christian Hesse
2007-05-03 19:37 ` Sam Ravnborg
2007-05-04 8:56 ` Christian Hesse
2007-05-04 9:47 ` 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=20070503061533.GA13399@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@earthworm.de \
/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