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: <20071109193702.e7bfa5fb.rdunlap@xenotime.net>
Date:	Fri, 9 Nov 2007 19:37:02 -0800
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Sam Ravnborg <sam@...nborg.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/11 v3] enable "make ARCH=x86"

On Fri, 09 Nov 2007 22:23:23 -0500 Jeff Garzik wrote:

> Sam Ravnborg wrote:
> > This is the patch that get rid of ARCH=i386 and ARCH=x86_64
> > and introduce ARCH=x86.
> > It touches several files but the changes are all one or two-liners.
> > 
> >       x86: drop backward compatibility symlinks to i386/boot and x86_64/boot
> >       kbuild: sanity check the specified arch
> 
> 
> IMO it negatives impacts the workflow when you -remove- the ability to 
> set 32/64-bit on the make command line.
> 
> Building and testing for both architectures now requires the additional 
> step of editing .config, which is a clear workflow negative impact at 
> least for me.
> 
> I switch between other cross-compiled arches (alpha, usually) on the 
> makefile command line
> 
> Yes, I know other 32/64-bit arches require .config editing.  That 
> doesn't change the basic fact that this is a workflow regression.

Thanks.  Well said.  I strongly agree.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ