lkml.org 
[lkml]   [2005]   [Jun]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH] ppc64: Fix PER_LINUX32 behaviour
Date
On Middeweken 08 Juni 2005 19:24, Linus Torvalds wrote:

> I think this is a feature, not a bug, and I suspect you just broke
> compiling a 64-bit kernel by default on ppc64.
>
> Dammit, the system _is_ ppc64. The fact that the uname binary is not is
> neither here nor there. It's like x86 that reports i386/i486/.. depending
> on what the machine is. If uname wants to make it clear that uname has
> been compiled for 32-bit ppc, then it can damn well output "ppc" on its
> own without asking the kernel what the kernel is.

The whole point of the LINUX32 personality is to mangle the output of
uname, it doesn't do anything else on the architectures I have worked
with (s390, x86_64 and ppc64).

Even with the patch, the normal operation would be to use PER_LINUX
for everything, so the kernel build works as expected unless you pass
the obsolete "fakeppc" boot parameter.

With the LINUX32 personality, you can build 32 bit binaries through
autoconf, rpmbuild, or the kernel without pretending to be
cross-compiling. It may not be the best solution, but people seem to
rely on it and the patch brings ppc64 in line with how it works on
the other architectures.

Arnd <><
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-06-08 21:20    [W:0.262 / U:1.628 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site