From: Holger Hans Peter Freyther <holger+oe@freyther.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: LPC3250, helloworld-image, configure: error: cannot run C compiled programs
Date: Fri, 21 Aug 2009 03:43:48 +0200 [thread overview]
Message-ID: <200908210343.48652.holger+oe@freyther.de> (raw)
In-Reply-To: <4A8D98FB.5000400@gmail.com>
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.
next prev parent reply other threads:[~2009-08-21 2: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 [this message]
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=200908210343.48652.holger+oe@freyther.de \
--to=holger+oe@freyther.de \
--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