"building binutils for target" question

Yann E. MORIN yann.morin.1998@anciens.enib.fr
Fri Mar 25 15:33:00 GMT 2011

Andy, Michael, All,

On Friday 25 March 2011 16:15:15 ANDY KENNEDY wrote:
> > To build the complete binutils to run on the target (eg. ar, ld...)
> > means to build a cross-native toolchain, which is not currently
> > supported by crostool-NG ( although I'm working on it, but there's
> > only 24h in a day! ).
> Ignorance talking here:  Isn't that basically a Canadian Cross?  I mean
> you've got Building on machine X a toolchain for machine Y which builds
> for machine Z.  Why does it matter that Y == Z? 

Almost. It mostly is a canadian cross. What differs between a cross-native
(what Michael wants) and a canadian cross, is:
- canadian cross:
  - install gcc as 'tuple-gcc', ar as 'tuple-ar', and so on...
  - use a sysroot
- cross-native   :
  - install gcc as 'gcc', ar as 'ar', and so on...
  - do not use a sysroot

This is because cross-native is expected to be the native toolchain on
the target, hence expects the standard libs+headers locations as /lib,
/usr/lib and /usr/include, and the non-tupled tools names, such as 'gcc'
and 'ar' and 'ld', as this toolchain is not a cross-toolchain.

A cross-native is basically a native toolchain that is cross-compiled.
But that's not so easy...

> Canadian Cross does work, doesn't it?

Mostly, it does. There are still optimisations and fixes needed, but it
does work quite OK for now. As a side note, I have a pending patch queue
that I'm working on (when time permits) that should make build a canadian
cross easier. And which also should pave the way for cross-native (and
maybe native as well...).

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

More information about the crossgcc mailing list