From: Dmitry Vinokurov <d.vinokuroff@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: LPC3250, helloworld-image, configure: error: cannot run C compiled programs
Date: Thu, 20 Aug 2009 19:01:59 +0600 [thread overview]
Message-ID: <4A8D4947.5030108@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3631 bytes --]
Hello,
I'm trying to build helloworld-image for LPC3250 board and created
local.conf and lpc3250.conf (files attached) using prebuilt toolchain
and 'bitbake -v helloworld-image' give following error:
--------
NOTE: Running task 193 of 643 (ID: 636,
/home/raydan/work/oe/openembedded/recipes/gcc/gcc-cross-initial_4.2.4.bb,
do_compile)
ERROR: function do_compile failed
ERROR: see log in
/home/raydan/work/oe/build/tmp/work/arm-oe-linux-gnueabi/gcc-cross-initial-4.2.4-r7.1/temp/log.do_compile.15707
NOTE: Task failed:
/home/raydan/work/oe/build/tmp/work/arm-oe-linux-gnueabi/gcc-cross-initial-4.2.4-r7.1/temp/log.do_compile.15707
ERROR: TaskFailed event exception, aborting
ERROR: Build of
/home/raydan/work/oe/openembedded/recipes/gcc/gcc-cross-initial_4.2.4.bb
do_compile failed
ERROR: Task 636
(/home/raydan/work/oe/openembedded/recipes/gcc/gcc-cross-initial_4.2.4.bb,
do_compile) failed
NOTE: Tasks Summary: Attempted 192 tasks of which 186 didn't need to be
rerun and 1 failed.
ERROR:
'/home/raydan/work/oe/openembedded/recipes/gcc/gcc-cross-initial_4.2.4.bb'
failed
--------
Executing 'tail
tmp/work/arm-oe-linux-gnueabi/gcc-cross-initial-4.2.4-r7.1/temp/log.do_compile.15707'
give following:
--------
checking target system type... arm-oe-linux-gnueabi
checking for i686-linux-gcc...
/opt/nxp/gcc-4.3.2-glibc-2.7/arm-vfp-linux-gnu/../bin/arm-vfp-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C
compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
make[1]: *** [configure-fixincludes] Error 1
make[1]: Leaving directory
`/home/raydan/work/oe/build/tmp/work/arm-oe-linux-gnueabi/gcc-cross-initial-4.2.4-r7.1/gcc-4.2.4/build.i686-linux.arm-oe-linux-gnueabi'
make: *** [all] Error 2
FATAL: oe_runmake failed
--------
Looks like bitbake use ARM toolchain instead of X86 and of course it
cannot run ARM targets on my laptop. Could somebody explain, please, how
this mess with toolchains can be fixed?
By the way, I don't understand why bitbake build gcc-cross-initial when
I use external toolchain. Maybe I've configured something wrong and OE
tries to build it's own toolchain, but seems like config is correct
according to manual.
Thanks in advance.
--
Best Regards,
Dmitry Vinokurov
<d.vinokuroff@gmail.com>
DL_DIR = "${HOME}/sources"
BBFILES := "${HOME}/work/oe/openembedded/recipes/*/*.bb"
BBMASK = ""
PREFERRED_VERSION_virtual/kernel = "2.6.27"
ASSUME_PROVIDED += " virtual/${TARGET_PREFIX}gcc "
ASSUME_PROVIDED += " virtual/libc "
MACHINE = "lpc3250"
DISTRO = "minimal"
#CCACHE = "ccache "
CCACHE = " "
TOOLCHAIN_PATH = "/opt/nxp/gcc-4.3.2-glibc-2.7/arm-vfp-linux-gnu"
export CC="${CCACHE}${TOOLCHAIN_PATH}/../bin/arm-vfp-linux-gnu-gcc "
export CXX="${CCACHE}${TOOLCHAIN_PATH}/../bin/arm-vfp-linux-gnu-g++ "
export CPP="${TOOLCHAIN_PATH}/../bin/arm-vfp-linux-gnu-gcc -E "
export LD="${TOOLCHAIN_PATH}/../bin/arm-vfp-linux-gnu-ld "
export AR="${TOOLCHAIN_PATH}/../bin/arm-vfp-linux-gnu-ar "
export AS="${TOOLCHAIN_PATH}/../bin/arm-vfp-linux-gnu-as "
export RANLIB="${TOOLCHAIN_PATH}/../bin/arm-vfp-linux-gnu-ranlib "
export STRIP="${TOOLCHAIN_PATH}/../bin/arm-vfp-linux-gnu-strip "
TARGET_CPPFLAGS_append = " -I${TOOLCHAIN_PATH}/include "
TARGET_LDFLAGS_prepend = " -L${TOOLCHAIN_PATH}/lib -Wl,-rpath-link,${TOOLCHAIN_PATH}/lib "
TARGET_ARCH = "arm"
PACKAGE_EXTRA_ARCHS = "armv5te"
TARGET_CC_ARCH = "-fsigned-char -mfpu=vfp -mfloat-abi=softfp"
next reply other threads:[~2009-08-20 13:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 13:01 Dmitry Vinokurov [this message]
2009-08-20 13:23 ` LPC3250, helloworld-image, configure: error: cannot run C compiled programs Holger Hans Peter Freyther
2009-08-20 13:26 ` Holger Hans Peter Freyther
2009-08-20 18:42 ` Dmitry Vinokurov
2009-08-21 1:10 ` Holger Hans Peter Freyther
2009-08-21 1:43 ` Holger Hans Peter Freyther
2009-08-22 7:18 ` Dmitry Vinokurov
2009-08-22 7:45 ` Dmitry Vinokurov
2009-08-22 23:17 ` Khem Raj
2009-08-23 4:17 ` Dmitry Vinokurov
2009-08-23 6:53 ` Khem Raj
2009-08-23 13:25 ` Dmitry Vinokurov
2009-08-23 15:43 ` Khem Raj
2009-08-25 17:47 ` Dmitry Vinokurov
2009-08-29 9:09 ` Dmitry Vinokurov
2009-08-24 12:34 ` Rolf Offermanns
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=4A8D4947.5030108@gmail.com \
--to=d.vinokuroff@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.