From: Marcus Meissner <meissner@suse.de>
To: "David S. Miller" <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ppc64: Fix PER_LINUX32 behaviour
Date: Wed, 8 Jun 2005 22:50:17 +0200 (CEST) [thread overview]
Message-ID: <20050608205017.861757D1D4@grape.suse.de> (raw)
In-Reply-To: <20050608.121950.104038734.davem@davemloft.net.suse.lists.linux.kernel>
In article <20050608.121950.104038734.davem@davemloft.net.suse.lists.linux.kernel> you wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> Date: Wed, 8 Jun 2005 20:49:48 +0200
>
>> 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.
>
> I totally agree, this has a large precedence on many platforms
> and there are even gcc frontends that check the uname output
> to decide what code model to output by default.
Actually what you then do (which is the standard way) is
powerpc32 bash --login
which gives you a shell with 32bit personality and work from
this.
Ciao, Marcus
next parent reply other threads:[~2005-06-08 20:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050608.121950.104038734.davem@davemloft.net.suse.lists.linux.kernel>
2005-06-08 20:50 ` Marcus Meissner [this message]
2005-06-08 11:59 [PATCH] ppc64: Fix PER_LINUX32 behaviour Paul Mackerras
2005-06-08 17:24 ` Linus Torvalds
2005-06-08 18:49 ` Arnd Bergmann
2005-06-08 19:19 ` David S. Miller
2005-06-08 20:45 ` Olaf Hering
2005-06-08 20:45 ` Andreas Schwab
2005-06-08 20:54 ` Juergen Kreileder
2005-06-08 22:40 ` Andreas Schwab
2005-06-09 7:02 ` Juergen Kreileder
2005-06-08 23:12 ` Paul Mackerras
2005-06-08 23:16 ` David S. Miller
2005-06-11 11:24 ` Andi Kleen
2005-06-08 23:28 ` Linus Torvalds
2005-06-08 23:12 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050608205017.861757D1D4@grape.suse.de \
--to=meissner@suse.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox