LPC3250, helloworld-image, configure: error: cannot run C compiled programs

LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Dmitry Vinokurov]

[-- 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"

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Holger Hans Peter Freyther]

On Thursday 20 August 2009 15:01:59 Dmitry Vinokurov wrote:
> 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:

I think you should explore using the external-toolchain. This way you will 
have to set the PATH to the toolchain and make "external-toolchain" the 
default provider...

And for the old way have you seen this: 
http://docs.openembedded.org/usermanual/html/commonuse_prebuilt_toolchain.html?

z.



>
> 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.

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Holger Hans Peter Freyther]

On Thursday 20 August 2009 15:01:59 Dmitry Vinokurov wrote:

> 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.

To figure out why OE is building the toolchain you can do

bitbake -g helloworld

and then look at the generated depends.dot. Looking at slugos.inc you will 
need to set more ASSUMED_PROVIDED or go the external-toolchain route (which 
sadly has not much documentation...)

z.

>
> Thanks in advance.

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Dmitry Vinokurov]

Holger Hans Peter Freyther wrote:

> I think you should explore using the external-toolchain. This way you will 
> have to set the PATH to the toolchain and make "external-toolchain" the 
> default provider...
> 
> And for the old way have you seen this: 
> http://docs.openembedded.org/usermanual/html/commonuse_prebuilt_toolchain.html?
> 
> z.

Yes, I've seen manual and seems like I did everything that was told
there. By the way I meant that I want to use exactly external toolchain.
I used LTIB building system earlier and wanted to use toolchain from there.

> On Thursday 20 August 2009 15:01:59 Dmitry Vinokurov wrote:
>
>   
>> 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.
>>     
>
> To figure out why OE is building the toolchain you can do
>
> bitbake -g helloworld
>
> and then look at the generated depends.dot. Looking at slugos.inc you will 
> need to set more ASSUMED_PROVIDED or go the external-toolchain route (which 
> sadly has not much documentation...)
>
> z.
>   

I've tested it (removed tmp dir and built from scratch): 'bitbake
helloworld' doesn't try to build toolchain, looks like it use toolchain
that I pointed. At least at the build log (I used -D) I can see
'CC=/opt/nxp/gcc-4.3.2-glibc-2.7/arm-vfp-linux-gnu/../bin/arm-vfp-linux-gnu-gcc', 


build commands with this compiler and similar. Configure scripts found
toolchain too. But the way how toolchain is used is really strange,
strings like following are in many packages (binutils-cross-2.18-r8.1, 
gcc-cross-initial-4.2.4-r7.1 and maybe some other, that I haven't seen):
--------
checking for i686-linux-ar... ar
checking for i686-linux-strip...
/opt/nxp/gcc-4.3.2-glibc-2.7/arm-vfp-linux-gnu/../bin/arm-vfp-linux-gnu-strip
checking for i686-linux-ranlib... ranlib
--------
or
--------
checking for i686-linux-gcc... 
/opt/nxp/gcc-4.3.2-glibc-2.7/arm-vfp-linux-gnu/../bin/arm-vfp-linux-gnu-gcc
--------

I.e. some utils are X86-native, other are cross. In the first example 
above configure use ARM strip, though I've got strip on my Debian system.

This mess lead to error, that I described in first letter of this chain:
--------
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.
--------

--
Best Regards,
Dmitry Vinokurov
<d.vinokuroff@gmail.com>

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Holger Hans Peter Freyther]

On Thursday 20 August 2009 20:42:03 Dmitry Vinokurov wrote:
> Holger Hans Peter Freyther wrote:
> > I think you should explore using the external-toolchain. This way you
> > will have to set the PATH to the toolchain and make "external-toolchain"
> > the default provider...
> >
> > And for the old way have you seen this:
> > http://docs.openembedded.org/usermanual/html/commonuse_prebuilt_toolchain
> >.html?
> >
> > z.
>
> Yes, I've seen manual and seems like I did everything that was told
> there. By the way I meant that I want to use exactly external toolchain.
> I used LTIB building system earlier and wanted to use toolchain from there.
>
> > On Thursday 20 August 2009 15:01:59 Dmitry Vinokurov wrote:
> >> 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.
> >
> > To figure out why OE is building the toolchain you can do
> >
> > bitbake -g helloworld
> >
> > and then look at the generated depends.dot. Looking at slugos.inc you
> > will need to set more ASSUMED_PROVIDED or go the external-toolchain route
> > (which sadly has not much documentation...)
> >
> > z.
>
> I've tested it (removed tmp dir and built from scratch): 'bitbake
> helloworld' doesn't try to build toolchain, looks like it use toolchain
> that I pointed. At least at the build log (I used -D) I can see
> 'CC=/opt/nxp/gcc-4.3.2-glibc-2.7/arm-vfp-linux-gnu/../bin/arm-vfp-linux-gnu
>-gcc',

To figure out why OE is building the toolchain you can do

bitbake -g helloworld

and then look at the generated depends.dot. Looking at slugos.inc you
will need to set more ASSUMED_PROVIDED or go the external-toolchain route
(which sadly has not much documentation...)


z.

PS: Seems the documentation was not updated when new depends got introduced... 
*sigh*

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Holger Hans Peter Freyther]

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.

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Dmitry Vinokurov]

[-- Attachment #1: Type: text/plain, Size: 4775 bytes --]

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.

--
Best Regards,
Dmitry Vinokurov
#
# local.conf
#
# Author: Dmitry Vinokurov <raydan@permlug.org>
#


DL_DIR = "${HOME}/sources"
BBFILES := "${HOME}/work/oe/openembedded/recipes/*/*.bb"
BBMASK = ""
PREFERRED_VERSION_virtual/kernel = "2.6.27"

TARGET_PREFIX = "arm-linux-gnueabi-"
ASSUME_SHLIBS = "libc.so.6:libc"

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/libc "
ASSUME_PROVIDED += " linux-libc-headers "
ASSUME_PROVIDED += " virtual/libintl "
ASSUME_PROVIDED += " virtual/libiconv "

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 "

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Dmitry Vinokurov]

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

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Khem Raj]

On (22/08/09 13:45), Dmitry Vinokurov wrote:
> 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.

its a cross package so host being i686-linux (I suppose you are building
on i686 box) is ok. Look into the config.log error message should be in
there

-Khem

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Dmitry Vinokurov]

Khem Raj wrote:
> On (22/08/09 13:45), Dmitry Vinokurov wrote:
>   
>> 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.
>>     
>
> its a cross package so host being i686-linux (I suppose you are building
> on i686 box) is ok. Look into the config.log error message should be in
> there
>
> -Khem
>   
Hm, "configure --help" says "--host=HOST cross-compile to build programs 
to run on HOST [BUILD]" and as I understand, I will run programs on ARM, 
so it should be 'arm-oe-linux-gnueabi'.

Anyway, even if host should be x86, instead of i686-linux-gcc it finds 
arm-vfp-linux-gcc and fails.
Here is config.log:
-----------------------------------------------------------------------------------------------------------
configure:1739: checking build system type
configure:1757: result: i686-pc-linux-gnu
configure:1779: checking host system type
configure:1794: result: i686-pc-linux-gnu
configure:1816: checking target system type
configure:1831: result: arm-oe-linux-gnueabi
configure:1876: checking for a BSD-compatible install
configure:1932: result: 
/home/raydan/work/oe/build-linux/tmp/staging/i686-linux/usr/bin/install -c
configure:1943: checking whether build environment is sane
configure:1986: result: yes
configure:2014: checking for a thread-safe mkdir -p
configure:2053: result: 
/home/raydan/work/oe/build-linux/tmp/staging/i686-linux/usr/bin/mkdir -p
configure:2066: checking for gawk
configure:2082: found /usr/bin/gawk
configure:2093: result: gawk
configure:2104: checking whether make sets $(MAKE)
configure:2125: result: yes
configure:2336: checking for i686-linux-gcc
configure:2363: result: 
/opt/nxp/gcc-4.3.2-glibc-2.7/arm-vfp-linux-gnu/../bin/arm-vfp-linux-gnu-gcc
configure:2641: checking for C compiler version
configure:2648: 
/opt/nxp/gcc-4.3.2-glibc-2.7/arm-vfp-linux-gnu/../bin/arm-vfp-linux-gnu-gcc 
--version >&5
arm-vfp-linux-gnu-gcc (crosstool-NG-1.3.1) 4.3.2
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:2651: $? = 0
configure:2658: 
/opt/nxp/gcc-4.3.2-glibc-2.7/arm-vfp-linux-gnu/../bin/arm-vfp-linux-gnu-gcc 
-v >&5
Using built-in specs.
Target: arm-vfp-linux-gnu
Configured with: /home/usb10132/ct1/bin/targets/src/gcc-4.3.2/configure 
--build=i386-build_redhat-linux-gnu --host=i386-build_redhat-linux-gnu 
--target=arm-vfp-linux-gnu 
--prefix=/home/usb10132/x-tools/arm-vfp-linux-gnu 
--with-sysroot=/home/usb10132/x-tools/arm-vfp-linux-gnu/arm-vfp-linux-gnu/sys-root 
--enable-languages=c,c++ --disable-multilib --with-arch=armv5te 
--with-abi=atpcs --with-cpu=arm926ej-s --with-fpu=vfp --with-float=soft 
--with-gmp=/home/usb10132/x-tools/arm-vfp-linux-gnu 
--with-mpfr=/home/usb10132/x-tools/arm-vfp-linux-gnu 
--with-pkgversion=crosstool-NG-1.3.1 --enable-__cxa_atexit 
--with-local-prefix=/home/usb10132/x-tools/arm-vfp-linux-gnu/arm-vfp-linux-gnu/sys-root 
--disable-nls --enable-threads=posix --enable-symvers=gnu --enable-c99 
--enable-long-long --enable-target-optspace
Thread model: posix
gcc version 4.3.2 (crosstool-NG-1.3.1)
configure:2661: $? = 0
configure:2668: 
/opt/nxp/gcc-4.3.2-glibc-2.7/arm-vfp-linux-gnu/../bin/arm-vfp-linux-gnu-gcc 
-V >&5
arm-vfp-linux-gnu-gcc: '-V' option must have argument
configure:2671: $? = 1
configure:2694: checking for C compiler default output file name
configure:2721: 
/opt/nxp/gcc-4.3.2-glibc-2.7/arm-vfp-linux-gnu/../bin/arm-vfp-linux-gnu-gcc 
-isystem/home/raydan/work/oe/build-linux/tmp/staging/i686-linux/usr/include 
-O2 -g 
-isystem/home/raydan/work/oe/build-linux/tmp/staging/i686-linux/usr/include 
-L/home/raydan/work/oe/build-linux/tmp/staging/i686-linux/usr/lib 
-Wl,-rpath-link,/home/raydan/work/oe/build-linux/tmp/staging/i686-linux/usr/lib 
-Wl,-rpath,/home/raydan/work/oe/build-linux/tmp/staging/i686-linux/usr/lib 
-Wl,-O1 conftest.c  >&5
configure:2724: $? = 0
configure:2762: result: a.out
configure:2779: checking whether the C compiler works
configure:2789: ./a.out
/home/raydan/work/oe/build-linux/tmp/work/arm-oe-linux-gnueabi/module-init-tools-cross-3.2.2-r5/module-init-tools-3.2.2/configure: 
line 2790: ./a.out: cannot execute binary file
configure:2792: $? = 126
configure:2801: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
-----------------------------------------------------------------------------------------------------------

--
Best Regards,
Dmitry Vinokurov

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Khem Raj]

On (23/08/09 10:17), Dmitry Vinokurov wrote:
> >>>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.
> >
> >its a cross package so host being i686-linux (I suppose you are building
> >on i686 box) is ok. Look into the config.log error message should be in
> >there
> >
> >-Khem
> Hm, "configure --help" says "--host=HOST cross-compile to build
> programs to run on HOST [BUILD]" and as I understand, I will run
> programs on ARM, so it should be 'arm-oe-linux-gnueabi'.
> 
> Anyway, even if host should be x86, instead of i686-linux-gcc it
> finds arm-vfp-linux-gcc and fails.

dont confuse pure cross with canadian cross. You are doing a normal
cross build here which means build machine is same as host machine.

Your problem is probably because you are overriding CC and friends
which could be confusing (already confused) configure even more.

Try setting CC_FOR_BUILD=<your native compiler on the build machine>

Thanks

-Khem

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Dmitry Vinokurov]

Khem Raj wrote:
> On (23/08/09 10:17), Dmitry Vinokurov wrote:
>   
>>>>> 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.
>>>>         
>>> its a cross package so host being i686-linux (I suppose you are building
>>> on i686 box) is ok. Look into the config.log error message should be in
>>> there
>>>
>>> -Khem
>>>       
>> Hm, "configure --help" says "--host=HOST cross-compile to build
>> programs to run on HOST [BUILD]" and as I understand, I will run
>> programs on ARM, so it should be 'arm-oe-linux-gnueabi'.
>>
>> Anyway, even if host should be x86, instead of i686-linux-gcc it
>> finds arm-vfp-linux-gcc and fails.
>>     
>
> dont confuse pure cross with canadian cross. You are doing a normal
> cross build here which means build machine is same as host machine.
>
> Your problem is probably because you are overriding CC and friends
> which could be confusing (already confused) configure even more.
>
> Try setting CC_FOR_BUILD=<your native compiler on the build machine>
>
> Thanks
>
> -Khem
>   
Thank you for your help. I'm newbie in OE and crosscompiling at all and 
may confuse some things.

Just now I've tried to build some not so simple as helloworld but not so 
complicated as kernel -- bc calculator. And I'd like to say that during 
configure stage it sets:
--build=i686-linux --host=arm-oe-linux-gnueabi --target=arm-oe-linux-gnueabi

Builded bc works fine on my board and this is normal, not canadian, 
cross build.

--
Best Regards,
Dmitry Vinokurov

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Khem Raj]

On (23/08/09 19:25), Dmitry Vinokurov wrote:
> Khem Raj wrote:
> >On (23/08/09 10:17), Dmitry Vinokurov wrote:
> >>>>>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.
> >>>its a cross package so host being i686-linux (I suppose you are building
> >>>on i686 box) is ok. Look into the config.log error message should be in
> >>>there
> >>>
> >>>-Khem
> >>Hm, "configure --help" says "--host=HOST cross-compile to build
> >>programs to run on HOST [BUILD]" and as I understand, I will run
> >>programs on ARM, so it should be 'arm-oe-linux-gnueabi'.
> >>
> >>Anyway, even if host should be x86, instead of i686-linux-gcc it
> >>finds arm-vfp-linux-gcc and fails.
> >
> >dont confuse pure cross with canadian cross. You are doing a normal
> >cross build here which means build machine is same as host machine.
> >
> >Your problem is probably because you are overriding CC and friends
> >which could be confusing (already confused) configure even more.
> >
> >Try setting CC_FOR_BUILD=<your native compiler on the build machine>
> >
> >Thanks
> >
> >-Khem
> Thank you for your help. I'm newbie in OE and crosscompiling at all
> and may confuse some things.
> 
> Just now I've tried to build some not so simple as helloworld but
> not so complicated as kernel -- bc calculator. And I'd like to say
> that during configure stage it sets:
> --build=i686-linux --host=arm-oe-linux-gnueabi --target=arm-oe-linux-gnueabi
> 
> Builded bc works fine on my board and this is normal, not canadian,
> cross build.

its a target package being built on build machine. Your build was failing to compile a package which
will run on your host (similar to cross compilers) they are not same
cases. module-init-tools would be analogically similar to bc but not
module-init-tools-cross which is the package you reported failing.


> 
> --
> Best Regards,
> Dmitry Vinokurov
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Dmitry Vinokurov]

Khem Raj wrote:
> On (23/08/09 19:25), Dmitry Vinokurov wrote:
>   
>> Khem Raj wrote:
>>     
>>> On (23/08/09 10:17), Dmitry Vinokurov wrote:
>>>       
>>>>>>> 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.
>>>>>>             
>>>>> its a cross package so host being i686-linux (I suppose you are building
>>>>> on i686 box) is ok. Look into the config.log error message should be in
>>>>> there
>>>>>
>>>>> -Khem
>>>>>           
>>>> Hm, "configure --help" says "--host=HOST cross-compile to build
>>>> programs to run on HOST [BUILD]" and as I understand, I will run
>>>> programs on ARM, so it should be 'arm-oe-linux-gnueabi'.
>>>>
>>>> Anyway, even if host should be x86, instead of i686-linux-gcc it
>>>> finds arm-vfp-linux-gcc and fails.
>>>>         
>>> dont confuse pure cross with canadian cross. You are doing a normal
>>> cross build here which means build machine is same as host machine.
>>>
>>> Your problem is probably because you are overriding CC and friends
>>> which could be confusing (already confused) configure even more.
>>>
>>> Try setting CC_FOR_BUILD=<your native compiler on the build machine>
>>>
>>> Thanks
>>>
>>> -Khem
>>>       
>> Thank you for your help. I'm newbie in OE and crosscompiling at all
>> and may confuse some things.
>>
>> Just now I've tried to build some not so simple as helloworld but
>> not so complicated as kernel -- bc calculator. And I'd like to say
>> that during configure stage it sets:
>> --build=i686-linux --host=arm-oe-linux-gnueabi --target=arm-oe-linux-gnueabi
>>
>> Builded bc works fine on my board and this is normal, not canadian,
>> cross build.
>>     
>
> its a target package being built on build machine. Your build was failing to compile a package which
> will run on your host (similar to cross compilers) they are not same
> cases. module-init-tools would be analogically similar to bc but not
> module-init-tools-cross which is the package you reported failing.
>   
Yes, you're right. Recently read documentation more attentively 
(http://docs.openembedded.org/usermanual/usermanual.html#recipes_variables) 
and understood that I was wrong.
Now appearing errors are more familiar to me and I hope soon image for 
LPC3250 will be built successfully and I'll report about it.

--
Best Regards,
Dmitry Vinokurov

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Dmitry Vinokurov]

Dmitry Vinokurov wrote:
> Khem Raj wrote:
>> On (23/08/09 19:25), Dmitry Vinokurov wrote:
>>  
>>> Khem Raj wrote:
>>>    
>>>> On (23/08/09 10:17), Dmitry Vinokurov wrote:
>>>>      
>>>>>>>> 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.
>>>>>>>             
>>>>>> its a cross package so host being i686-linux (I suppose you are 
>>>>>> building
>>>>>> on i686 box) is ok. Look into the config.log error message should 
>>>>>> be in
>>>>>> there
>>>>>>
>>>>>> -Khem
>>>>>>           
>>>>> Hm, "configure --help" says "--host=HOST cross-compile to build
>>>>> programs to run on HOST [BUILD]" and as I understand, I will run
>>>>> programs on ARM, so it should be 'arm-oe-linux-gnueabi'.
>>>>>
>>>>> Anyway, even if host should be x86, instead of i686-linux-gcc it
>>>>> finds arm-vfp-linux-gcc and fails.
>>>>>         
>>>> dont confuse pure cross with canadian cross. You are doing a normal
>>>> cross build here which means build machine is same as host machine.
>>>>
>>>> Your problem is probably because you are overriding CC and friends
>>>> which could be confusing (already confused) configure even more.
>>>>
>>>> Try setting CC_FOR_BUILD=<your native compiler on the build machine>
>>>>
>>>> Thanks
>>>>
>>>> -Khem
>>>>       
>>> Thank you for your help. I'm newbie in OE and crosscompiling at all
>>> and may confuse some things.
>>>
>>> Just now I've tried to build some not so simple as helloworld but
>>> not so complicated as kernel -- bc calculator. And I'd like to say
>>> that during configure stage it sets:
>>> --build=i686-linux --host=arm-oe-linux-gnueabi 
>>> --target=arm-oe-linux-gnueabi
>>>
>>> Builded bc works fine on my board and this is normal, not canadian,
>>> cross build.
>>>     
>>
>> its a target package being built on build machine. Your build was 
>> failing to compile a package which
>> will run on your host (similar to cross compilers) they are not same
>> cases. module-init-tools would be analogically similar to bc but not
>> module-init-tools-cross which is the package you reported failing.
>>   
> Yes, you're right. Recently read documentation more attentively 
> (http://docs.openembedded.org/usermanual/usermanual.html#recipes_variables) 
> and understood that I was wrong.
> Now appearing errors are more familiar to me and I hope soon image for 
> LPC3250 will be built successfully and I'll report about it.
Successfully builded kernel for LPC3250, it works on the board. But 
trouble with module-init-tools (configure try to use CC (set to arm 
compiler) as x86 compiler and fails due to "cannot run C compiled 
programs") still remains -- I temporarily solved it by explicitly 
setting CC=gcc in module-init-tools-cross_3.2.2.bb, though I don't think 
that it is good solution.

Maybe somebody more experienced could advise, how this trouble can be 
solved in the right way? I'm ready to give any needed logs.

Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs

[Rolf Offermanns]

Holger Hans Peter Freyther <holger+oe <at> freyther.de> writes:

> 
> 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?

I recently stumbled upon the same problems and in addition to the things above
(which I can all confirm) I had to add:

ASSUME_PROVIDED += " virtual/${TARGET_PREFIX}libc-initial "
ASSUME_PROVIDED += " virtual/${TARGET_PREFIX}gcc-initial " 
ASSUME_PROVIDED += " gcc-cross " 

to keep bitbake from including glibc / gcc from the build queue.

-Rolf