From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] First hack for external toolchain support based on sysroot
Date: Wed, 3 Dec 2008 09:31:03 +0100 [thread overview]
Message-ID: <20081203093103.3aab088d@surf> (raw)
In-Reply-To: <COL102-DS16312FCA60C7EA2DB82A0CDC030@phx.gbl>
Le Wed, 3 Dec 2008 08:14:00 +0000,
"Daniel Laird" <danieljlaird@hotmail.com> a ?crit :
> I had done the first bit and not the second. I will start to look at
> this. Perhaps the CFLAGS and LDFLAGS can go back to how they were
> when new started all this.
> eg LD="$(TARGET_LD) $(TARGET_LDFLAGS)"
>
> Does that work for DirectFB?
Maybe, I haven't tried.
> Cheers foe this good work, maybe we will have external toolchain
> working properly soon?
I hope so :-)
The nice advantage of the --sysroot solution is that it should work in
all cases, while the -rpath-link solution didn't work for Qtopia, for
example.
> My next question is - with sysroot set do we really need to set the
> SYSROOT option to pkgconfig? and do we need to sed all the .la files?
I'd say we still need them. Otherwise in a .la file you'll
have /usr/lib/libfoobar.a, and I don't think gcc will interpret that
relative to its --sysroot. But it remains to be checked.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2008-12-03 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 22:21 [Buildroot] [RFC] First hack for external toolchain support based on sysroot Thomas Petazzoni
2008-12-03 8:14 ` Daniel Laird
2008-12-03 8:31 ` Thomas Petazzoni [this message]
2008-12-10 8:24 ` Thomas Petazzoni
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=20081203093103.3aab088d@surf \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox