From: Dan Kegel <dank@kegel.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Marty Ridgeway <mridge@us.ibm.com>,
linux-kernel@vger.kernel.org, ltp-list@lists.sourceforge.net,
ltp-announce@lists.sourceforge.net
Subject: Re: [LTP] Re: [ANNOUNCE] April Release of LTP now Available
Date: Wed, 06 Apr 2005 08:05:39 -0700 [thread overview]
Message-ID: <4253FAC3.5010000@kegel.com> (raw)
In-Reply-To: <20050406043001.3f3d7c1c.akpm@osdl.org>
Andrew Morton wrote:
>> LTP-20050405
>
> It seems to have an x86ism in it which causes the compile to fail on ppc64:
>
> socketcall01.c: In function `socketcall':
> socketcall01.c:80: error: asm-specifier for variable `__sc_4' conflicts with asm clobber list
That might be a problem with your toolchain.
Other mentions of that error message on Google
suggest that it's due to a kernel header problem.
I bet your toolchain uses kernel headers from 2.4.21 or earlier...
check includes/asm-ppc64/unistd.h to see if it's got the
line
/* On powerpc a system call basically clobbers the same registers like a
in it. If not, it may be missing the patch mentioned below.
See
http://ozlabs.org/pipermail/linuxppc64-dev/2003-April/000211.html
http://ozlabs.org/pipermail/linuxppc-dev/2002-October/014492.html
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9379
http://www.hu.kernel.org/pub/linux/kernel/v2.4/snapshots/incr/patch-2.4.22-bk57-bk58
- Dan
--
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
next prev parent reply other threads:[~2005-04-06 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 19:13 [ANNOUNCE] April Release of LTP now Available Marty Ridgeway
2005-04-06 11:30 ` Andrew Morton
2005-04-06 15:05 ` Dan Kegel [this message]
2005-04-06 15:20 ` [LTP] " Arjan van de Ven
2005-04-07 0:52 ` Paul Mackerras
2005-04-07 1:11 ` Chris Friesen
2005-04-07 5:14 ` Alan Modra
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=4253FAC3.5010000@kegel.com \
--to=dank@kegel.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-announce@lists.sourceforge.net \
--cc=ltp-list@lists.sourceforge.net \
--cc=mridge@us.ibm.com \
/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.