Openembedded Devel Discussions
 help / color / mirror / Atom feed
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: Tue, 25 Aug 2009 23:47:05 +0600	[thread overview]
Message-ID: <4A942399.2020106@gmail.com> (raw)
In-Reply-To: <20090823154300.GA9250@gmail.com>

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



  reply	other threads:[~2009-08-25 18:04 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
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 [this message]
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=4A942399.2020106@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