From: Dmitry Vinokurov <d.vinokuroff@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs
Date: Sat, 22 Aug 2009 13:45:19 +0600 [thread overview]
Message-ID: <4A8FA20F.5050401@gmail.com> (raw)
In-Reply-To: <4A8F9BE3.1020606@gmail.com>
Dmitry Vinokurov wrote:
> Holger Hans Peter Freyther wrote:
>> On Thursday 20 August 2009 20:42:03 Dmitry Vinokurov wrote:
>>
>> I will update the documentation with these bits:
>>
>>
>> ASSUME_PROVIDED += " virtual/${TARGET_PREFIX}gcc "
>> ASSUME_PROVIDED += " virtual/libc "
>> ASSUME_PROVIDED += "linux-libc-headers "
>> ASSUME_PROVIDED += "virtual/${TARGET_PREFIX}gcc "
>> ASSUME_PROVIDED += "virtual/${TARGET_PREFIX}gcc-initial "
>> ASSUME_PROVIDED += "virtual/${TARGET_PREFIX}gcc-intermediate "
>> ASSUME_PROVIDED += "virtual/${TARGET_PREFIX}binutils "
>> ASSUME_PROVIDED += "virtual/${TARGET_PREFIX}libc-for-gcc "
>> ASSUME_PROVIDED += "virtual/libintl "
>> ASSUME_PROVIDED += "virtual/libiconv "
>>
>> TARGET_PREFIX = "arm-linux-gnueabi-"
>> ASSUME_SHLIBS = "libc.so.6:libc"
>>
>>
>> The main difference are. Assume provided more binaries/libraries, use
>> the TARGET_PREFIX instead of CC, CXX, NM....
>>
>>
>> does this work any better?
>> z.
>>
>>
> I changed my config according to your advises, final version attached.
> Tried to build helloworld application: 'bitbake -v -DDD helloworld',
> it compiles and runs on target board fine. Tried to build linux
> kernel: 'bitbake -v -DDD linux-2.6.27', it fails with
> --------
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking target system type... arm-oe-linux-gnueabi
> checking for a BSD-compatible install...
> /home/raydan/work/oe/build-linux/tmp/staging/i686-linux/usr/bin/install
> -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p...
> /home/raydan/work/oe/build-linux/tmp/staging/i686-linux/usr/bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> 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.
> + oefatal 'oe_runconf failed'
> + echo FATAL: 'oe_runconf failed'
> FATAL: oe_runconf failed
> + exit 1
> ERROR: function do_configure failed
> ERROR: see log in
> /home/raydan/work/oe/build-linux/tmp/work/arm-oe-linux-gnueabi/module-init-tools-cross-3.2.2-r5/temp/log.do_configure.30320
>
> NOTE: Task failed:
> /home/raydan/work/oe/build-linux/tmp/work/arm-oe-linux-gnueabi/module-init-tools-cross-3.2.2-r5/temp/log.do_configure.30320
>
> ERROR: TaskFailed event exception, aborting
> ERROR: Build of
> /home/raydan/work/oe/openembedded/recipes/module-init-tools/module-init-tools-cross_3.2.2.bb
> do_configure failed
> ERROR: Task 107
> (/home/raydan/work/oe/openembedded/recipes/module-init-tools/module-init-tools-cross_3.2.2.bb,
> do_configure) failed
> NOTE: Tasks Summary: Attempted 86 tasks of which 21 didn't need to be
> rerun and 1 failed.
> ERROR:
> '/home/raydan/work/oe/openembedded/recipes/module-init-tools/module-init-tools-cross_3.2.2.bb'
> failed
> --------
>
> I.e. bitbake again confused cross-gcc and x86-gcc. Updated my OE with
> git pull, removed tmp/ and made rebuild -- same result.
Looks like error is in wrong ./configure parameter: --host=i686-linux
instead of --host=arm-oe-linux-gnueabi .
Now I'm trying to find, why --host was set to i686 and where it can be
changed.
--
Best Regards,
Dmitry Vinokurov
next prev parent reply other threads:[~2009-08-22 8:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 13:01 LPC3250, helloworld-image, configure: error: cannot run C compiled programs Dmitry Vinokurov
2009-08-20 13:23 ` 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 [this message]
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=4A8FA20F.5050401@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox