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]

Re: Gcc calling wrong assembler


On Mon, Aug 13, 2001 at 08:11:01PM -0500, Grant Edwards wrote:

> I'm trying to build gcc 2.95.2 for an arm-elf target.  I've
> done this before a couple times, but it was largely by accident
> and I've never understood why it worked.
> 
> I've spent all day reading FAQs and trying different configure
> options, and I'm stumped.  No matter what I do, I can't get
> arm-elf-gcc to call arm-elf-as.
> 
> They only way I've ever gotten a cross-gcc build to work is to
> put copies of the binutils binaries in /usr/local/arm-elf/bin/as 
> and so on.
>
> But, none of the FAQ entries or the instructions I've seen say
> you have to do this.  Why do I have to when nobody else does? :(

OK -- binutils "make install" puts links to the binaries under

  /usr/local/${target}/bin/${program}
 and
  /usr/local/bin/${target}-${program}

I've come to the conclusion that what I was trying to do (have
only /usr/local/bin/arm-elf-as, and having gcc use that
pathname) is just not possible.  Why I had convinced myself it
was possible is another question...

> Can somebody point me to an explanation of how gcc decides what
> assembler to call?

Question:

If gcc knows that it has to call /usr/local/arm-elf/bin/as, why
isn't it an error when it's not there?  

Falling back to /usr/bin/as doesn't seem like the best thing to
do. The compiler knows that it's a cross compiler, right?  I
can't think of any situations where a cross-compiler calling
/usr/bin/as is a very useful thing to do.

-- 
Grant Edwards
grante@visi.com

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


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