bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/6727] Thumb interworking code zero when another section is posit


From: nickc at redhat dot com
Subject: [Bug ld/6727] Thumb interworking code zero when another section is positioned before positioning .text
Date: 21 Jul 2008 15:53:26 -0000

------- Additional Comments From nickc at redhat dot com  2008-07-21 15:53 
-------
Subject: Re:  Thumb interworking code zero when another section
 is     positioned before positioning .text

Hi Aaron,

> how do i build binutils from source for ARM?
> i followed instructions on http://www.gnuarm.com/support.html

Well those instructions should work, although obviously you can stop 
once you have built and installed your new set of binutils.

> # cd [binutils-build]
> # [binutils-source]/configure --target=arm-elf --prefix=[toolchain-prefix]
> #   --enable-interwork --enable-multilib
> # make all install
> 
> i found this to be incorrect. so, i changed it to:
> --program-prefix=arm-elf --prefix=${HOME}/local --target=arm-elf
> 
> however, i get a message that i am building for arm-unknown-elf.
> what should i do?

Is that a problem ?  The config.sub script automatically expands 
"arm-elf" into "arm-unknown-elf".  This is OK.  The middle part of the 
triplet is the manufacturer's name and "unknown" is a perfectly common 
value.  The binutils should still build correctly.

>> I should also point out that you should not be invoking the linker directly. 
> 
> however, if i use GCC to link, i will not be able to position the
> objects and libraries in the order i want.

OK, but please be careful to construct the linker command line 
correctly.  (I mentioned using gcc to drive the linker because quiet a 
few bug reports that we receive are due to people trying to run the 
linker directly and not appreciating the work that gcc does in 
constructing the command line).

Cheers
   Nick


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=6727

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]