This is the mail archive of the crossgcc@sourceware.org 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] |
Arnaud, Bryan, All, On Wednesday 29 December 2010 00:16:13 Arnaud Lacombe wrote: > On Tue, Dec 28, 2010 at 6:01 PM, Yann E. MORIN > <yann.morin.1998@anciens.enib.fr> wrote: > > On Tuesday 28 December 2010 20:31:04 Arnaud Lacombe wrote: > >> That said, it would seem that the default linker depends. As I'd > >> understand it so far, gcc maintain its own set of tools in its > >> internal directory structure (the one containing "as", "ld", ...) use > >> them to access the actual linker. > > > > I am not sure I understand this. Are you talking about a combined tree? > > We are not using a combined tree, and gcc does not have the source for > > as, ld gold, or [...] in its tree. > > > > But yet, when we build the 'core' gcc, we copy binutils' tools into the > > core gcc install dir, so that it can find them. > > > no, I was speaking about the final content of > ${PREFIX}/${TARGET_TUPLE}/bin, which seem to be a copy of the tools > available in ${PREFIX}/bin. Ah, OK, right. In fact, it's binutils installing them in this place and they are hardlinks to the tools in prefix/bin. Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |