Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain: fix using external toolchains built with buildroot
Date: Wed, 07 Apr 2010 09:51:13 +0200	[thread overview]
Message-ID: <878w8zr98u.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20100406225010.23853.36745.stgit@roazhon.bzh.lan> (Yann E. MORIN's message of "Wed, 07 Apr 2010 00:50:10 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@anciens.enib.fr> writes:

 Yann> From: Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
 Yann> The toolchains built with buildroot use specially crafted paths for their
 Yann> sysroot and prefix. Fix that by asking gcc where it finds a file we
 Yann> know by relative path to the sysroot.

 Yann> This has the side effect of greatly simplifying the sysroot detection
 Yann> in every cases tested so far (BR toolchains, CT-NG toolchains, and
 Yann> CodeSourcery toolchains).

Committed, thanks all of you. Yann, don' forget to sign off on your
patches (-s option).

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2010-04-07  7:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 22:50 [Buildroot] [PATCH] Fix external toolchain sysroot detection, take 2 Yann E. MORIN
2010-04-06 22:50 ` [Buildroot] [PATCH] toolchain: fix using external toolchains built with buildroot Yann E. MORIN
2010-04-07  7:00   ` Thomas Petazzoni
2010-04-07  7:51   ` Peter Korsgaard [this message]
2010-04-07 17:41     ` Yann E. MORIN
  -- strict thread matches above, loose matches on Subject: below --
2010-04-06 22:47 [Buildroot] [PATCH] Fix external toolchain sysroot detection Yann E. MORIN
2010-04-06 22:47 ` [Buildroot] [PATCH] toolchain: fix using external toolchains built with buildroot Yann E. MORIN

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=878w8zr98u.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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