From: Wolfgang Denk <wd@denx.de>
To: Theo Gjaltema <gjalt007@chello.nl>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: eldk bug?how to fix
Date: Fri, 30 Dec 2005 22:13:52 +0100 [thread overview]
Message-ID: <20051230211352.D73E7352597@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 29 Dec 2005 22:48:53 +0100." <43B459C5.1060206@chello.nl>
In message <43B459C5.1060206@chello.nl> you wrote:
>
> I've seen these messages before. They were gone when I compiled using
> ppc_8xx-gcc compiler of a different ELDK version.
> What version of ELDK are you using? Which gcc version?
This has nothing to do with ELDK versions, or any other toolchain
issues.
> >[root@localhost atmlz]# ppc_6xx-gcc -c -o temp atm_aalx.c
> >atm_aalx.c: In function `main':
> >atm_aalx.c:201: warning: return type of `main' is not `int'
> >/tmp/cciJlehe.s: Assembler messages:
> >/tmp/cciJlehe.s:916: Error: unsupported relocation against r3
...
> > mfmsr r3
> > ori r3,r3,0x8000
> > andi. r3,r3,0xffbf
> > mtmsr r3
It's a user only problem (using symbolic names like "r3" in inline
assember statements without incuding the proper header files to
resolve thise names).
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
We fight only when there is no other choice. We prefer the ways of
peaceful contact.
-- Kirk, "Spectre of the Gun", stardate 4385.3
next prev parent reply other threads:[~2005-12-30 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 8:20 eldk bug?how to fix zengshuai
2005-12-18 14:44 ` Wolfgang Denk
2005-12-29 21:48 ` Theo Gjaltema
2005-12-30 21:13 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-09 7:35 S. Egbert
2006-02-09 9:07 ` Wolfgang Denk
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=20051230211352.D73E7352597@atlas.denx.de \
--to=wd@denx.de \
--cc=gjalt007@chello.nl \
--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).