From: "Ahsan, Noor" <Noor_Ahsan@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: External toolchain
Date: Tue, 22 Feb 2011 10:47:01 +0100 [thread overview]
Message-ID: <989A078976CDAD4CB2DC976EEF70E2A5051FA815@eu2-mail.mgc.mentorg.com> (raw)
In-Reply-To: <12689458.696811298366163560.JavaMail.defaultUser@defaultHost>
Hello Luca,
Probably you need to create symbolic links of arm-angstrom-linux-
gnueabi-gcc to arm-none-linux-gnueabi-gcc. OE assumes that the compiler name is arm-angstrom-linux-gnueabi-gcc. You can see the "CC" variable value by take environment of libtool-cross (using -e options) that how OE is creating the name of compiler.
Regards,
Noor
-----Original Message-----
From: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of Luca Bolognini
Sent: Tuesday, February 22, 2011 2:16 PM
To: Open Embedded Mailing List
Subject: [oe] External toolchain
Hi,
I would like to use an external toolchain (CodeSourcery2009q1) to
cross-compile some packages for my beagleboard (more or less the same
that happens in Arago) and then I expect not to download glibc package
and cross-compile again libc, libpthread and so on. I would like to use
the libraries inside my external CodeSourcery SDK.
I followed some
hints by Denys and Tom ( http://lists.linuxtogo.
org/pipermail/openembedded-devel/2010-April/019521.html ) and I put
#
LUCA
TARGET_VENDOR = "-none"
TOOLCHAIN_TYPE ?= "external"
TOOLCHAIN_BRAND ?= "csl"
TOOLCHAIN_PATH = "/opt/ti/codesourcery"
TOOLCHAIN_SYSPATH = "${TOOLCHAIN_PATH}/arm-none-linux-gnueabi"
PATH_prepend = "${TOOLCHAIN_PATH}/bin:"
require
conf/distro/include/toolchain-external.inc
inside my
openembedded/conf/distro/angstrom-2008.1.conf
As you know, cross-
compiler provided by CodeSoucery is arm-none-linux-gnueabi-gcc but I
get the following error with libtool-cross_2.2.6b.bb:
Build
Configuration:
BB_VERSION = "1.8.19"
METADATA_BRANCH =
"release-2010.12"
METADATA_REVISION = "dec3967"
TARGET_ARCH =
"arm"
TARGET_OS = "linux-gnueabi"
MACHINE =
"beagleboard"
DISTRO = "angstrom"
DISTRO_VERSION =
"2010.7-test-20110221"
TARGET_FPU = "hard"
[...]
| checking for
arm-angstrom-linux-gnueabi-gcc... arm-angstrom-linux-gnueabi-gcc -
march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-
interwork -mno-thumb
| checking whether the C compiler works... no
|
configure: error: in `/home/bolognini/diskp2/diskp2.4/pure-
oe/build/tmp/work/armv7a-angstrom-linux-gnueabi/libtool-cross-2.2.6b-
r27.1/libtool-2.2.6b':
| configure: error: C compiler cannot create
executables
Obviously OE doesn't have to find arm-angstrom-linux-
gnueabi-gcc, but why does it search for arm-angstrom-linux-gnueabi-gcc
instead of arm-none-linux-gnueabi-gcc ?
What's wrong inside angstrom-
2008.1.conf or what am I missing?
Thank you for your support
Luca
Supera i limiti: raddoppia la velocità da 10 a 20 Mega! Risparmia con Tutto Incluso: telefono + adsl 20 mega a soli 29,95 € al mese per due anni! SCONTO DI 240 EURO! http://abbonati.tiscali.it/telefono-adsl/prodotti/tc/tuttoincluso/?WT.mc_id=01fw
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2011-02-22 9:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 9:16 External toolchain Luca Bolognini
2011-02-22 9:47 ` Ahsan, Noor [this message]
2011-02-23 11:49 Luca Bolognini
2011-02-23 19:28 ` Khem Raj
2011-02-24 4:07 ` Denys Dmytriyenko
2011-02-24 9:13 Luca Bolognini
2012-07-12 19:20 external toolchain Dallas Clement
2012-07-12 19:23 ` Chris Larson
2014-03-28 10:20 External Toolchain Anjandeep Sahni
2014-03-28 16:42 ` Denys Dmytriyenko
2015-10-28 18:37 External toolchain Virgilia Eigner
2015-10-28 18:46 ` Khem Raj
2015-11-18 9:26 external toolchain Virgilia Eigner
2015-11-19 7:01 ` Khem Raj
2015-11-20 9:18 ` Virgilia Eigner
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=989A078976CDAD4CB2DC976EEF70E2A5051FA815@eu2-mail.mgc.mentorg.com \
--to=noor_ahsan@mentor.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.