From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain problem with svn revision 24694
Date: Mon, 5 Jan 2009 22:54:35 +0100 [thread overview]
Message-ID: <20090105225435.0aa68b1a@surf> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE1909FA4C84@mi8nycmail19.Mi8.com>
Hi hartleys,
Le Mon, 5 Jan 2009 16:47:53 -0500,
"hartleys" <hartleys@visionengravers.com> a ?crit :
> My bash scripting is not quite up to par but I think the
> $(copy_toolchain_sysroot) macro is doing the following:
>
> 1) calls '$(TARGET_CC) -v'
> 2) greps the output for the "Configured ...." information
> 3) greps that information for the "--with-sysroot ..." string
> 4) cuts the string following --with-sysroot and assigns it to
> SYSROOT_DIR
> 5) copies the entire $${SYSROOT_DIR} to ${STAGING_DIR}
> 6) chmod's all the directories to 755
Exactly.
> The problem I have is my external toolchain does not have a
> --with-sysroot configuration option.
Which probably means that your toolchain hasn't been compiled with
sysroot support.
> Any ideas?
Yes and no.
Yes: I can make sure that we test if sysroot is supported by the
toolchain and if not fail out instead of doing stupid things. I will
commit a patch that implements this soon.
No: I don't see a proper way of supporting external toolchains if they
don't support sysroot. Our previous attempts of using --rpath-link have
all failed, and --sysroot seems to be the best option we've seen until
now.
Thanks for the report!
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:[~2009-01-05 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 20:49 [Buildroot] Problem with svn revision 24694 hartleys
2009-01-05 21:47 ` [Buildroot] External toolchain problem " hartleys
2009-01-05 21:54 ` Thomas Petazzoni [this message]
2009-01-12 11:16 ` Daniel James Laird
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=20090105225435.0aa68b1a@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