From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] toolchain: detect external glibc in symlinked /lib
Date: Sun, 3 Sep 2017 14:17:38 +0200 [thread overview]
Message-ID: <20170903141738.20c0d621@windsurf.lan> (raw)
In-Reply-To: <20170903120835.16190-1-camh@xdna.net>
Hello,
This generally looks ok, to me, except one paragraph of explanation,
see below.
On Sun, 3 Sep 2017 22:08:35 +1000, Cam Hutchison wrote:
> check_glibc checks for a valid glibc in an external toolchain, but
> assumes that the files indicating the presence of glibc (ld-linux*.so.*,
> ld.so.* or ld64.so.*) are in a top-level directory of the sysroot.
>
> When building a toolchain with buildroot and a merged /usr, /lib is
> a symlink to usr/lib. This is copied from the target to the staging
> directory, and then to the sysroot, and the ultimate location of the
> required files is in /usr/lib in the sysroot.
I don't understand this sentence. Nothing gets copied from target to
staging, and staging *is* the sysroot, so there's no copy. Could you
explain what you wanted to say here, we can perhaps find a better
phrasing.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-09-03 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 12:08 [Buildroot] [PATCH 1/1] toolchain: detect external glibc in symlinked /lib Cam Hutchison
2017-09-03 12:17 ` Thomas Petazzoni [this message]
2017-09-03 12:22 ` Cam Hutchison
2017-09-03 12:25 ` Thomas Petazzoni
2017-09-03 12:30 ` Cam Hutchison
2017-09-03 12:49 ` Yann E. MORIN
2017-09-03 20:30 ` Cam Hutchison
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=20170903141738.20c0d621@windsurf.lan \
--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