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]

Re: canadian build


Tobias, Samuel, All,

On Wednesday 07 March 2012 20:36:41 Samuel Martin wrote:
> Last week, building canadian cross-compiler using the head/top of the
> crosstool-NG repository,
> i got the same error.
> I did find a bug in: script/crosstool-NG.sh
> Quick fix is:
> sed -e 's/CT_TTOLCHAIN_TYPE/CT_TOOLCHAIN_TYPE/' \
>   -i script/crosstool-NG.sh

I just greped for TTOLCHAIN in 1.14 and current tree, and found
no match at all:
  $ hg grep --follow TTOLCHAIN |wc -l
  0

What tree are you speaking about?
Are you using a pristine tree, or do you have local patches?

> It seems that there is another bug at least about build-system-prefix
> and/or the host one.
> To quickly fix this (i was/am a bit in the rush), i added the bin
> directory for both the
> build-to-host cross-compiler and the build-to-target one to my PATH
> and correctly set the
> build-system-tuple as well as the host-system-tuple.

There are two ways you can handle this:

1- enter only the tuple- name of the two cross-compilers, and them
   in the PATH, as you did, eg.:
     CT_HOST_PREFIX="arm-unknown-linux-gnueabi-"
     CT_TARGET_PREFIX="mips-unknwon-linux-gnu-"
     PATH="/path/to/arm-compiler/bin:/path/to/mips-compiler:${PATH}"

2- enter the fully qualified path to your compiler, so there is no need
   to change your PATH, eg.:
     CT_HOST_PREFIX="/path/to/arm-compiler/bin/arm-unknown-linux-gnueabi-"
     CT_TARGET_PREFIX="/path/to/mips-compiler/mips-unknwon-linux-gnu-"

> So you need to have these 2 cross-compilers built before starting the canadian.

Yes, currently the canadian infrastrucutre requires that two cross-compiler
pre-exist:
 - the build->host cross-compiler, to be able to build the tools that will
   ultimately run on host (gcc, binutils...)
 - the build->target cross-compiler, to be able to build the libraries and
   tools that will ultimately run on the target (glibc, libgcc...)

> Have a look at: http://sourceware.org/ml/crossgcc/2011-03/msg00069.html

This thread is about the on-going revamp of the canadian infrastructure (yes,
it's been on-going for that long, even much longer...). It does not really
apply in this case...

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]