From: Juergen Kreileder <jk@blackdown.de>
To: Andreas Schwab <schwab@suse.de>
Cc: Linus Torvalds <torvalds@osdl.org>,
Paul Mackerras <paulus@samba.org>,
akpm@osdl.org, anton@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ppc64: Fix PER_LINUX32 behaviour
Date: Thu, 09 Jun 2005 09:02:11 +0200 [thread overview]
Message-ID: <42A7E973.5080603@blackdown.de> (raw)
In-Reply-To: <jed5qwbhfw.fsf@sykes.suse.de>
Andreas Schwab wrote:
> Juergen Kreileder <jk@blackdown.de> writes:
>>The current code doesn't work like intended, on my G5 both 'linux32
>>uname -m' and 'linux32 sh -c "uname -m"' return 'ppc64' without the
>>patch.
>
> You appear to be using some very old version of glibc. I can't reproduce
> that here. Are you sure you aren't using syscall 109 (__NR_olduname)
> instead of 122 (__NR_uname)?
Debian unstable's glibc isn't exactly new but it isn't that old.
I guess others have the seen the problem too, otherwise anybody would
have ignored my bug report and the original patch.
Juergen
next prev parent reply other threads:[~2005-06-09 7:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
[not found] <20050608.121950.104038734.davem@davemloft.net.suse.lists.linux.kernel>
2005-06-08 20:50 ` Marcus Meissner
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=42A7E973.5080603@blackdown.de \
--to=jk@blackdown.de \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=schwab@suse.de \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.