This is the mail archive of the
crossgcc@sourceware.org
mailing list for the crossgcc project.
See the CrossGCC FAQ for lots
more information.
crosstool-ng: No CT_TOOLS_WRAPPER set when building a standard CROSS...
- From: Joachim Nilsson <jocke at vmlinux dot org>
- To: crossgcc at sourceware dot org
- Date: Sun, 06 Sep 2009 10:18:27 +0200
- Subject: crosstool-ng: No CT_TOOLS_WRAPPER set when building a standard CROSS...
Hi everyone!
Using crosstool-ng I selected to build a standard cross toolchain using
GCC 4.4.1. To that end I imported some gcc patches from buildroot and
everything seemed fine. Until I got to the final part of the build.
[EXTRA] Installing toolchain wrappers
[ALL ] ln: accessing `.armeb-redfox-linux-uclibc-wrapper': No such
file or directory
[ERROR] Build failed in step 'Cleaning-up the toolchain's directory'
[ERROR] Error happened in
'/home/INTRANET/joachim/crosstool-ng/scripts/functions' in function
'CT_DoExecLog' (line unknown, sorry)
[ERROR] called from
'/home/INTRANET/joachim/crosstool-ng/scripts/build/internals.sh' at line
# 76 in function 'do_finish'
[ERROR] called from
'/home/INTRANET/joachim/crosstool-ng/scripts/crosstool-NG.sh' at line #
544 in function 'main'
It seems that in scripts/build/internals.sh if CT_WRAPPER_NEEDED is set
it also needs CT_TOOLS_WRAPPER to be set, but for my standard cross
setup the CT_TOOLS_WRAPPER is not set in the .config file.
The build fails a couple of lines later in scripts/build/internals.sh
when it tries to hardlink every tool to a wrapper that was not built for
my cross setup (in the previous case).
I would have liked to include a patch, but I cannot make heads or tails
of this wrapper business, are wrappers even needed for standard cross
toolchains? If so, then maybe there should be a default *) in the
CT_TOOLS_WRAPPER case.
Any ideas?
Regards
/Jocke
--
For unsubscribe information see http://sourceware.org/lists.html#faq