lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070503061533.GA13399@uranus.ravnborg.org>
Date:	Thu, 3 May 2007 08:15:33 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Christian Hesse <mail@...thworm.de>
Cc:	linux-kernel@...r.kernel.org,
	James Ketrenos <jketreno@...ux.intel.com>
Subject: Re: build system: no module target ending with slash?

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ