unrecognized option `-mcpu32'
Mike Dorin
bsddorin@yahoo.com
Thu Jul 20 11:18:00 GMT 2006
Hello,
Bill was right,
If I change my path so that the new 'as' is in the
front, I can compile and build.
I should have tried that before...
However, I have never needed to do that before.
We simply compiled with m68k-elf-gcc and it seems
m68k-elf-as was always called. Oh well.
Thanks everybody for the help.
-Mike
--- Dave Korn <dave.korn@artimi.com> wrote:
> On 18 July 2006 20:06, Mike Dorin wrote:
>
> > How should I configure binutils?
> > How should I configure gcc?
>
> Well, what you've got all looks good to me so far.
> The most important thing
> is to use the exact same prefix and target.
>
>
> > export TARGET=m68k-elf
> > export PREFIX=/home/tools
> >
> > --prefix=$PREFIX
> > --target=$TARGET
>
> Sound.
>
> >> Did you build them? Using what command line?
> >
> > make all
> > make install
>
> Fine.
>
> >> If you /did/ download binutils, and you /did/
> >> configure it, and the
> >> configuration /was/ for a cross binutils, and you
> >> did then build /AND/ install
> >> it, did you /then/ add the $prefix/bin dir to
> your
> >> $PATH?
> >
> > yes
> > export PATH=$PATH:${PREFIX}/bin
>
> Spot on.
>
> > > If you /did/ download binutils, and you /did/
> >> configure it, and the
> >> configuration /was/ for a cross binutils, and you
> >> did then build /AND/ install
> >> it, /AND/ you then did correctly add the
> $prefix/bin dir to your $PATH, did
> >> you then use the same prefix when you configured
> >> gcc?
> >
> > yes
>
> Hmmmm, confusing!
>
> Well, what do you see when you run "m68k-elf-gcc
> -print-search-dirs" and
> "m68k-elf-gcc -print-prog-name=as" ?
>
>
> cheers,
> DaveK
> --
> Can't think of a witty .sigline today....
>
>
> --
> For unsubscribe information see
> http://sourceware.org/lists.html#faq
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc
mailing list