Re: canadian build

[Tobias Arp <tobiasarp@web.de>]

Yann,

i am still not able to build the canadian cross compiler. I have both 
cross compiler (build -> host and build ->target)
My config file (the part with CT_HOST_PREFIX...) is this:

# CT_NATIVE is not set
# CT_CROSS is not set
# CT_CROSS_NATIVE is not set
CT_CANADIAN=y
CT_TOOLCHAIN_TYPE="canadian"

#
# Build system
#
CT_BUILD=""
CT_BUILD_PREFIX=""
CT_BUILD_SUFFIX=""

#
# Host system
#
CT_HOST=""
CT_HOST_PREFIX="/home/tobias/x-tools/i586-pc-linux-gnu/bin/i586-pc-linux-gnu-"
CT_HOST_SUFFIX=""

#
# Target system
#
CT_TARGET_PREFIX="/home/tobias/x-tools/arm-i686-linux-gnueabi/bin/arm-linux-"
CT_TARGET_SUFFIX=""

I am getting now this error:

[INFO ]  Performing some trivial sanity checks
[INFO ]  Build started 20120308.083859
[INFO ]  Building environment variables
[EXTRA]  Preparing working directories
[00:01] / Invalid configuration `': machine `' not recognized
[ERROR]
[ERROR] >>
[ERROR] >>  Build failed in step '(top-level)'
[ERROR] >>
[ERROR] >>  Error happened in: CT_DoConfigSub[scripts/functions@940]
[ERROR] >>        called from: main[scripts/crosstool-NG.sh@372]
[ERROR] >>
[ERROR] >>  For more info on this error, look at the file: 'build.log'
[ERROR] >>  There is a list of known issues, some with workarounds, in:
[ERROR] >>      'docs/B - Known issues.txt'
[ERROR]
[ERROR]  (elapsed: 0:01.14)

Best regards

Tobias
Am 07.03.2012 21:16, schrieb Yann E. MORIN:
> 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.
>


--
For unsubscribe information see http://sourceware.org/lists.html#faq