Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain built by buildroot no longer supported.
Date: Tue, 6 Apr 2010 18:19:31 +0000 (UTC)	[thread overview]
Message-ID: <hpftvj$3b3$2@dough.gmane.org> (raw)
In-Reply-To: 201004061842.53138.yann.morin.1998@anciens.enib.fr

On 2010-04-06, Yann E. MORIN <yann.morin.1998@anciens.enib.fr> wrote:

>>> Grant> use of of external toolchains built by buildroot is no longer
>>> Grant> possible.
>
> We've discussed the issue on IRC yesterday evening, and I'm looking
> if I can make a quick fix (something in between a proper fix and a
> nice hack), but I'm not close to that yet.

I was going try changing the --prefix that buildroot uses to configure
toolchain stuff to be consistent with the --sysroot value but...

>> AFAICT, the recent commit relies on the assumption that both --prefix
>> and --sysroot values are correct and that the "prefix" is a child of
>> "sysroot".
>
> No, the other way around: prefix is a parent of sysroot
> (directory-wise).

For some reason I always have that backwared in my head.

>> That's not the case for buildroot toolchains.  They have a prefix of
>> "/usr" and a sysroot pointing to the output/staging directory.  I'm
>
> Yes, that's because buildroot plays trick with those values. The code
> dates back June 2007, and the exact reason for doing so is not yet
> known.
>
> I'm trying to bring buildroot toolchains more in sync with a
> /standard/ way of handling paths, but I have to check regressions.
>
> Anyway, I think that 'old' toolchains build prior the change I'm
> doing will not work.

No worries.  I'll either use crosstool-NG or we can fix the way
buildroot configures toolchains.

>> guessing that setting the buildroot toolchain's --prefix value to
>> output/staging/usr should fix the problem,
>
> More complex than that, unfortunately... :-( I tried, and it does not
> work so far (a few other things to change as well, eg. binutils).

Let me know if there's anything I can do to help.

-- 
Grant Edwards               grant.b.edwards        Yow! ONE LIFE TO LIVE for
                                  at               ALL MY CHILDREN in ANOTHER
                              gmail.com            WORLD all THE DAYS OF
                                                   OUR LIVES.

  reply	other threads:[~2010-04-06 18:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 14:41 [Buildroot] External toolchain built by buildroot no longer supported Grant Edwards
2010-04-06 15:02 ` Peter Korsgaard
2010-04-06 15:15   ` Grant Edwards
2010-04-06 16:42     ` Yann E. MORIN
2010-04-06 18:19       ` Grant Edwards [this message]
2010-04-06 16:42 ` Yann E. MORIN
2010-04-06 18:10   ` Grant Edwards
2010-04-06 18:12 ` 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='hpftvj$3b3$2@dough.gmane.org' \
    --to=grant.b.edwards@gmail.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