linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "S. Egbert" <s.egbert@sbcglobal.net>
To: linuxppc-embedded@ozlabs.org
Subject: eldk bug?how to fix
Date: Wed, 08 Feb 2006 23:35:14 -0800	[thread overview]
Message-ID: <43EAF0B2.2070902@sbcglobal.net> (raw)

> In message <43B459C5.1060206 at 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 at 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).

I had that exact same problem, ESPECIALLY when pulling in a fresh kernel
tree from kernel.org.

Fixed it by defining the CROSS_COMPILE environment variable or modifying
the Makefile's CROSS_COMPILE to the correct file prefix name, in your
case, it is probaly either

    # export CROSS_COMPILE=ppc_8xx-  (DENK gcc 3.3.3)
or
    # export CROSS_COMPILE=powerpc-linux-  (GNU gcc)

Check your PATH... make sure its picking up the right version...

  # whereis ppc_8xx-gcc

  # ppc_8xx-gcc --version
or
  # powerpc-linux-gcc --version


S. Egbert

             reply	other threads:[~2006-02-09  7:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09  7:35 S. Egbert [this message]
2006-02-09  9:07 ` eldk bug?how to fix Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2005-12-18  8:20 zengshuai
2005-12-18 14:44 ` Wolfgang Denk
2005-12-29 21:48 ` Theo Gjaltema
2005-12-30 21:13   ` 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=43EAF0B2.2070902@sbcglobal.net \
    --to=s.egbert@sbcglobal.net \
    --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).