Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchain and sysroot
Date: Fri, 26 Mar 2010 20:24:42 +0100	[thread overview]
Message-ID: <20100326202442.7ef0e1ae@surf> (raw)
In-Reply-To: <hoh171$jf0$1@dough.gmane.org>

On Fri, 26 Mar 2010 01:04:33 +0000 (UTC)
Grant Edwards <grant.b.edwards@gmail.com> wrote:

> >  * We pass --sysroot $(STAGING_DIR) to every gcc/ld invocation, so that
> >    gcc/ld find the libraries and header files correctly.
> 
> Perhaps that's what's supposed to happen, but there appear to be a lot
> of packages where it doesn't happen (at least for some of us).

As I said in my other mail in this thread, yes, there are many packages
that are broken with regard to --sysroot. Packages that use the
Makefile.autotools.in infrastructure should all work, but for all the
other packages, they should be fixed one by one.

Cheers,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-03-26 19:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 15:28 [Buildroot] external toolchain and sysroot Yury Luneff
2010-03-25 16:14 ` Grant Edwards
2010-03-25 17:12   ` Yury Luneff
2010-03-25 17:16     ` Yury Luneff
2010-03-25 18:08       ` Grant Edwards
2010-03-25 22:34         ` Thomas Petazzoni
2010-03-26  1:04           ` Grant Edwards
2010-03-26 19:24             ` Thomas Petazzoni [this message]
2010-03-27  1:10               ` Grant Edwards
2010-03-27  8:22                 ` Thomas Petazzoni
2010-03-27 15:05                   ` Grant Edwards
2010-04-14 13:42           ` Grant Edwards
2010-03-25 22:32   ` 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=20100326202442.7ef0e1ae@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