From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Issue for the integration of Codesourcery external toolchains
Date: Wed, 6 Jan 2010 08:59:53 +0200 [thread overview]
Message-ID: <20100106065952.GA12127@jasper.tkos.co.il> (raw)
In-Reply-To: <20100104162422.5b7e7bf6@surf>
Hi Thomas,
Thanks for you work on this. My comment below.
On Mon, Jan 04, 2010 at 04:24:22PM +0100, Thomas Petazzoni wrote:
[snip]
> Possible solutions
> ==================
>
> * Build a more normal sysroot in $(STAGING_DIR) by combining the
> contents of armv4t and the header files. But this would require
> telling gcc that the libraries aren't in armv4t anymore. This is
> probably possible using a custom spec file, but is quite
> complicated.
How about generating symlinks in the staging directory:
armv4t/usr/include -> ../../usr/include
thumb2/usr/include -> ../../usr/include
and then using the output of -print-sysroot for each target?
>
> * Reconsider the solution of copying the sysroot, and try harder with
> the more traditionnal -L/-I solutions.
>
> * Another solution ?
>
> Thanks for reading such a long mail, and thanks in advance for your
> ideas!
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2010-01-06 6:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 15:24 [Buildroot] Issue for the integration of Codesourcery external toolchains Thomas Petazzoni
2010-01-04 23:23 ` Lionel Landwerlin
2010-01-12 10:52 ` Thomas Petazzoni
2010-01-12 22:09 ` Yann E. MORIN
2010-01-12 23:39 ` Thomas Petazzoni
2010-01-12 23:40 ` Lionel Landwerlin
2010-01-06 6:59 ` Baruch Siach [this message]
2010-01-12 10:54 ` Thomas Petazzoni
2010-01-12 12:48 ` Baruch Siach
2010-01-12 12:56 ` Lionel Landwerlin
2010-01-12 13:25 ` Baruch Siach
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=20100106065952.GA12127@jasper.tkos.co.il \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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.