On PA-RISC machines running in 64-bit mode, uname -m returns `parisc64' instead of `parisc.' Thus, we must sed this to match like a few other platforms. From: Kyle McMartin <kyle@parisc-linux.org> Signed-off-by: Kyle McMartin <kyle@parisc-linux.org> diff --git a/Makefile b/Makefile index 2b057b8..16a026d 100644 --- a/Makefile +++ b/Makefile @@ -14,7 +14,7 @@ include scripts/Kbuild.include export CC := gcc NOSTDINC_FLAGS := -nostdlib -nostdinc -isystem $(shell $(CC) -print-file-name=include) -export ARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ -e s/arm.*/arm/ -e s/sa110/arm/) +export ARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/parisc64/parisc/ -e s/sun4u/sparc64/ -e s/arm.*/arm/ -e s/sa110/arm/) export HOSTCC := gcc export HOSTCFLAGS := -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
Kyle McMartin wrote:> On PA-RISC machines running in 64-bit mode, uname -m returns `parisc64' > instead of `parisc.' Thus, we must sed this to match like a few > other platforms.Should we be building 64-bit parisc binaries in this case? -hpa
On Tue, Jan 03, 2006 at 08:28:09PM -0800, H. Peter Anvin wrote:> Should we be building 64-bit parisc binaries in this case? >Unfortunately not, parisc is still quite a ways from having a usable 64-bit userspace. Cheers, Kyle
Kyle McMartin wrote:> > Unfortunately not, parisc is still quite a ways from having a usable > 64-bit userspace. >OK. klibc, by the way, has been found to be a very good way to bring up userspace on a new platform. -hpa