From: "Andrew Dennison" <andrew.dennison@motec.com.au>
To: "'Björn Östby'" <Bjorn.Ostby@combitechsystems.com>,
linuxppc-embedded@ozlabs.org
Subject: RE: RTAI+ELDK Compile Problems
Date: Wed, 9 Feb 2005 08:58:28 +1100 [thread overview]
Message-ID: <001e01c50e29$52738e80$4000a8c0@CAT> (raw)
In-Reply-To: <004B1D7A5257174C9044A1B7BD0E60ED0178CBE7@ratatosk.combitechsystems.com>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
On Tuesday, 8 February 2005 10:09 PM, linuxppc-embedded-bounces@ozlabs.org
wrote:
> I've got a major problem trying to compile RTAI using the
> ELDK cross compiler.
> I'm using ELDK version 3.1, and my target is ppc_8xx (823). I
> have followed the instructions given at
> ftp://ftp.denx.de/pub/RTAI/24.1.12/README.install
> <ftp://ftp.denx.de/pub/RTAI/24.1.12/README.install> , using the
>
> linuxppc_2_4_devel kernel (2004_04_30_1320) and rtai-24.1.12-denx.
>
> Now, the rtai patch works fine, and the kernel compiles, but
> when I try to compile rtai
> The following error occurs:
>
> /opt/eldk-3.1/ppc_8xx/usr/src/rtai-24.1.12/include/asm/rtai_srq.h: In
> function `rtai_srq':
> /opt/eldk-3.1/ppc_8xx/usr/src/rtai-24.1.12/include/asm/rtai_srq.h:32:
> error: asm-specifier for variable `__sc_3' conflicts with asm clobber
> list
>
I had a problem like this a while ago with gcc 3.3.2 (see this list from
22 March 2004) - seems later gcc versions are more pedantic about the way
the clobber list is specified, at least that is what some googling seemed
to indicate.
Attached patch worked for me when I was using linuxppc_devel patched with
patch-denx-linuxppc_2_4_devel-LABEL_2003_12_22_1500-ltt and
rtai-24.1.12-denx.tar.bz2.
[-- Attachment #2: rtai-24.1.12-denx.patch --]
[-- Type: application/octet-stream, Size: 547 bytes --]
diff -ur rtai-24.1.12.orig/include/asm-ppc/rtai_srq.h rtai-24.1.12/include/asm-ppc/rtai_srq.h
--- rtai-24.1.12.orig/include/asm-ppc/rtai_srq.h Tue Oct 24 11:32:28 2000
+++ rtai-24.1.12/include/asm-ppc/rtai_srq.h Thu Mar 18 14:38:35 2004
@@ -33,8 +33,7 @@
("trap \n\t"
: "=&r" (__sc_3), "=&r" (__sc_4)
: "0" (__sc_3), "1" (__sc_4),
- "r" (__sc_0)
- : "r0", "r3", "r4" );
+ "r" (__sc_0));
((unsigned long *)&retval)[0] = __sc_3;
((unsigned long *)&retval)[1] = __sc_4;
return retval;
prev parent reply other threads:[~2005-02-08 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 11:09 RTAI+ELDK Compile Problems Björn Östby
2005-02-08 11:35 ` Re : " grave
2005-02-08 21:58 ` Andrew Dennison [this message]
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='001e01c50e29$52738e80$4000a8c0@CAT' \
--to=andrew.dennison@motec.com.au \
--cc=Bjorn.Ostby@combitechsystems.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).