linux-kernel - Re: two architectures,same source tree

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, 22 Dec 2006 13:00:27 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	7eggert@....de
Cc:	Jörn Engel <joern@...ybastard.org>,
	Yakov Lerner <iler.ml@...il.com>,
	Kernel <linux-kernel@...r.kernel.org>
Subject: Re: two architectures,same source tree

On Fri, 22 Dec 2006 21:45:26 +0100 Bodo Eggert wrote:

> Jörn Engel <joern@...ybastard.org> wrote:
> > On Wed, 20 December 2006 20:32:20 +0200, Yakov Lerner wrote:
> 
> >> Is it easily possible to build two architectures in
> >> the same source tree (so that intermediate fles
> >> and resut files do not interfere ) ?
> > 
> > I'd try something like this:
> > make O=../foo ARCH=foo
> > make O=../bar ARCH=bar
> > 
> > But as I'm lazy I'll leave the debugging to you. :)
> 
> IIRC You'll have to specify ARCH= on each make call, but O= is saved in
> ../foo/Makefile.

Hm, top-level README file says:

   Please note: If the 'O=output/dir' option is used then it must be
   used for all invocations of make.


---
~Randy
-
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/