This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: assembler errors compiling arm-none-elf


> > You have either built your assembler incorrectly, or gcc is 
> > not finding it 
> > and is using the native one (most likely).  Have you got 
> > <prefix>/bin on 
> > your PATH?  <prefix> is the prefix you used to configure the 
> > assembler.
> 
> Yes, it looked to me as though it was using the wrong assembler, too, but
> the install path (~/bin) definitely was in my path.

Hmm, sounds odd.  A cross compiler will only try to invoke 'as' if it is 
unable to locate <target>-as, where <target> is the --target= option that 
you used to configure gcc (you did use identical configure strings, didn't 
you).

> I finally built binutils+gcc successfully by configuring with a prefix of
> /usr/local instead of ~.  This really was the only difference.
> 
> I'm wondering if it could be that the new assembler couldn't find libopcodes
> or something like that, but I don't understand the whole gcc architecture
> enough to know what I'm talking about.  :)

Nope, the ARM assembler doesn't use libopcodes.

R.




------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]