Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] toolchain: detect external glibc in merged /usr
Date: Mon, 16 Oct 2017 23:58:26 +0200	[thread overview]
Message-ID: <87376irbzx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170903210043.19105-1-camh@xdna.net> (Cam Hutchison's message of "Mon, 4 Sep 2017 07:00:43 +1000")

>>>>> "Cam" == Cam Hutchison <camh@xdna.net> writes:

 > When using an external toolchain that was built with Buildroot and a
 > merged /usr, the dynamic linker is actually in /usr/lib.

 > But the check_glibc macro limits the depth it is looking for the dynamic
 > linker, and misses it when it is in /usr/lib because it is too deep.

 > We could fix that in two ways: increase the depth in which we look
 > for it, or follow symlinks. We choose the second solution.

 > Signed-off-by: Cam Hutchison <camh@xdna.net>
 > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
 > Cc: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
 > Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
 > ---
 > Changes v1 -> v2:
 >   - Reworded commit message (suggested by Yann)

Committed to 2017.08.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2017-10-16 21:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-03 21:00 [Buildroot] [PATCH v2 1/1] toolchain: detect external glibc in merged /usr Cam Hutchison
2017-09-04 16:09 ` Yann E. MORIN
2017-09-19 21:00 ` Arnout Vandecappelle
2017-10-16 21:58 ` Peter Korsgaard [this message]

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=87376irbzx.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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