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]
Date:	Fri, 29 Feb 2008 17:34:13 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	"John W. Linville" <linville@...driver.com>
Cc:	Michael Buesch <mb@...sch.de>, David Miller <davem@...emloft.net>,
	gordonfarquharson@...il.com, netdev@...r.kernel.org,
	linux-wireless@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: pull request: wireless-2.6 2008-02-27


On Fri, 2008-02-29 at 11:26 -0500, John W. Linville wrote:
> On Fri, Feb 29, 2008 at 01:16:59PM +0100, Michael Buesch wrote:
> 
> > I'm wondering if we can't simply pass a commandline parameter to file2alias
> > that tells it whether we are crosscompiling. It should simply omit the sanity check
> 
> Sounds reasonable to me.

In fact, file2alias shouldn't need a command line argument ...

> > in that case. Is there any easy and reliable way to find out whether we
> > are crosscompiling from a makefile (I don't know the makefile core that much)?
> 
> Non-empty CROSS_COMPILE definition?

... it can just check whether CROSS_COMPILE is set in its environment.
No?

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ