linux-kernel - Re: Recursive variable `KBUILD_CFLAGS' references itself (eventually).

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 24 Jan 2008 22:31:18 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Sam Ravnborg <sam@...nborg.org>
cc:	Dave Jones <davej@...hat.com>, lkml <linux-kernel@...r.kernel.org>
Subject: Re: Recursive variable `KBUILD_CFLAGS' references itself (eventually).


On Jan 24 2008 22:27, Sam Ravnborg wrote:
>>  > > Trying to do a 32bit build on a 64bit machine.
>>  > > I did..
>>  > >   make ARCH=i386 oldconfig
>>  > >   make ARCH=i386 arch/x86/
>>  > 
>>  > Walking through my mailbox I found this one.
>>  > I did not get similar reports and I cannot reproduce it.
>>  > Do you continue to see this or had it been fixed somehow?
>> 
>> Still happens for me with the latest tree from git.
>> 
>> $ make ARCH=i386 arch/x86/
>
>There is no easy fx for this one.
>You try to build one of the non-standard directories and it just
>fails because arch/x86/Makefile is not a regular Kbuild file.
>
>Try with any other directory (almost any other) and it works.
>Considered unfortunate but not a bug - so I will not try to fix it.

So, how are we going to build only arch/x86/ right now with kbuild?
--
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/