| 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
| ||
|
Message-Id: <20090904093846.a87bd198.randy.dunlap@oracle.com> Date: Fri, 4 Sep 2009 09:38:46 -0700 From: Randy Dunlap <randy.dunlap@...cle.com> To: "H. Peter Anvin" <hpa@...or.com> Cc: David Woodhouse <dwmw2@...radead.org>, Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org, mingo@...hat.com, sam@...nborg.org, tglx@...utronix.de, David.Woodhouse@...el.com, linux-tip-commits@...r.kernel.org Subject: Re: [tip:x86/kbuild] x86: Don't silently override CONFIG_64BIT in 'make oldconfig' On Fri, 04 Sep 2009 09:27:18 -0700 H. Peter Anvin wrote: > On 09/04/2009 08:33 AM, David Woodhouse wrote: > > On Fri, 4 Sep 2009, Ingo Molnar wrote: > > > > > >>> x86: Don't silently override CONFIG_64BIT in 'make oldconfig' > >> > >> -tip testing found that this commit broke the UML build: > >> > >> /home/mingo/tip/arch/um/Makefile:52: > >> /home/mingo/tip/arch/um/Makefile-x86: No such file or directory > >> make[1]: *** No rule to make target > >> `/home/mingo/tip/arch/um/Makefile-x86'. Stop. > >> make: *** [sub-make] Error 2 > > > > Hm, doesn't that mean that UML has always been broken for ARCH=x86? > > > > Quite possible. ARCH=x86 hasn't exactly been widely used. what does ARCH=x86 mean? --- ~Randy LPC 2009, Sept. 23-25, Portland, Oregon http://linuxplumbersconf.org/2009/ -- 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