From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Wangdawei (Sivan)" <sivan.wang@huawei.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: The problem of using the external toolchain
Date: Sat, 31 Mar 2012 16:44:26 +0100 [thread overview]
Message-ID: <1333208666.18082.242.camel@ted> (raw)
In-Reply-To: <7E29EF69110C17499E6B3A9844CD4FD913424EF9@szxeml526-mbx.china.huawei.com>
On Sat, 2012-03-31 at 09:55 +0000, Wangdawei (Sivan) wrote:
> The reason is that I want to use the binary toolchain I have own in
> yocto, and I don’t have the source code of the toolchain , then I do
> the steps below:
>
> 1. add a line in local.conf like this TCMODE ?= "external-csl2008q3"
> 2.modify the file tcmode-external-csl2008q3.inc, change
> EXTERNAL_TOOLCHAIN = "/opt/toolchain-be8/armeb-linux-gnueabi" to refer
> to where my binary toolchain stored
> 3. comment the line “#SRC_URI = "file://SUPPORTED"” in file
> “external-csl-toolchain_2008q3-72.bb”,because we don’t have the source
> code ,so I think the SRC_URI maybe will be NULL
>
> When I do this , but it failed , below is the log I have got:
>
> NOTE: package binutils-cross-2.21.1a-r0: task do_configure: Started
>
> ERROR: Function 'do_configure' failed
> (see /home/ccc/poky-second/build/tmp/work/i586-none-linux/binutils-cross-2.21.1a-r0/temp/log.do_configure.5085 for further information)
>
> ERROR: Logfile of failure stored
> in: /home/ccc/poky-second/build/tmp/work/i586-none-linux/binutils-cross-2.21.1a-r0/temp/log.do_configure.5085
>
> Log data follows:
>
> | DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc',
> | 'bit-64', 'x86_64-linux', 'common']
> | configure.ac:32: error: Please use exactly Autoconf 2.64 instead of
> 2.68.
> | config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded
> from...
> | configure.ac:32: the top level
> |
> autom4te: /home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/usr/bin/m4 failed with exit status: 1
> | NOTE:
> Running /home/ccc/poky-second/build/tmp/work/i586-none-linux/binutils-cross-2.21.1a-r0/binutils-2.21.1/configure --build=x86_64-linux --host=x86_64-linux --target=i586-none-linux --prefix=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/usr --exec_prefix=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/usr --bindir=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/usr/bin/i586-none-linux --sbindir=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/usr/bin/i586-none-linux --libexecdir=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-none-linux --datadir=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/usr/share --sysconfdir=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/etc --sharedstatedir=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/com --localstatedir=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/var --libdir=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/usr/lib/i586-none-linux --includedir=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/usr/include --oldincludedir=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/usr/include --infodir=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/usr/share/info --mandir=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux/usr/share/man --disable-silent-rules --with-libtool-sysroot=/home/ccc/poky-second/build/tmp/sysroots/x86_64-linux --with-sysroot=/home/ccc/poky-second/build/tmp/sysroots/qemux86 --program-prefix=i586-none-linux- --disable-install-libbfd --disable-werror --enable-poison-system-directories --enable-nls ...
>
> | checking build system type... x86_64-pc-linux-gnu checking host
> system
> | type... x86_64-pc-linux-gnu checking target system type...
> | i586-none-linux-gnu checking for a BSD-compatible install...
> | /usr/bin/install -c checking whether ln works... yes checking
> whether
> | ln -s works... yes checking for a sed that does not truncate
> output...
> | /bin/sed checking for gawk... gawk checking for x86_64-linux-gcc...
> | gcc checking for C compiler default output file name...
> | configure: error: in
> `/home/ccc/poky-second/build/tmp/work/i586-none-linux/binutils-cross-2.21.1a-r0/binutils-2.21.1/build.x86_64-linux.i586-none-linux':
> | configure: error: C compiler cannot create executables See
> | `config.log' for more details
> | ERROR: oe_runconf failed
> | ERROR: Function 'do_configure' failed (see
> | /home/ccc/poky-second/build/tmp/work/i586-none-linux/binutils-cross-2.
> | 21.1a-r0/temp/log.do_configure.5085 for further information)
> NOTE: package binutils-cross-2.21.1a-r0: task do_configure: Failed
> We can see the toolchain it checked is also the x86_64-linux-gcc , not
> the toolchain I assigned “EXTERNAL_TOOLCHAIN =
> "/opt/toolchain-be8/armeb-linux-gnueabi"”
This is for the *build* system (i.e. the system you are compiling on) so
its likely correct.
It then goes on to look at the target of "i586-none-linux-gnu" which
sounds wrong given you appear to have an armeb toolchain?
I suspect you need to target a big endian arm machine rather than
MACHINE=qemux86 which I suspect you're currently using?
Cheers,
Richard
next prev parent reply other threads:[~2012-03-31 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 9:55 The problem of using the external toolchain Wangdawei (Sivan)
2012-03-31 15:44 ` Richard Purdie [this message]
2012-04-01 2:33 ` Wangdawei (Sivan)
2012-04-07 5:58 ` Khem Raj
2012-04-09 13:59 ` Wangdawei (Sivan)
-- strict thread matches above, loose matches on Subject: below --
2012-04-05 3:15 Wangdawei (Sivan)
2012-04-05 3:23 ` Chris Larson
2012-04-05 3:36 ` Wangdawei (Sivan)
2012-04-05 3:19 Wangdawei (Sivan)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1333208666.18082.242.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=poky@yoctoproject.org \
--cc=sivan.wang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.