From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9771] toolchain-external misses lib directory when copying sysroot
Date: Tue, 28 Mar 2017 20:43:17 +0000 [thread overview]
Message-ID: <bug-9771-163-vQGqVIWK2R@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9771-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9771
--- Comment #5 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
OK, so the issue is that some libraries are in <sysroot>/lib64 (C library) and
some others are in <sysroot>/lib (gcc runtime), which is not something
Buildroot handles I believe.
Buildroot does a:
$ ./bin/x86_64-unknown-linux-gnu-gcc -print-file-name=libc.a
/home/thomas/dl/x86_64-unknown-linux-gnu/bin/../x86_64-unknown-linux-gnu/sysroot/usr/lib/../lib64/libc.a
And therefore decides that ARCH_LIB_DIR is "lib64", and therefore looks only in
<sysroot>/lib64 for libraries and not in <sysroot>/lib.
Is this a recent change in Crosstool-NG ? The old Crosstool-NG toolchain we
have at
http://autobuild.buildroot.net/toolchains/tarballs/x86_64-ctng_locales-linux-gnu.tar.xz
has everything in <sysroot>/lib, with <sysroot>/lib64 being a symbolic link to
<sysroot>/lib.
So, are we looking at a Buildroot bug, or a Crosstool-NG bug?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-03-28 20:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 9:23 [Buildroot] [Bug 9771] New: toolchain-external misses lib directory when copying sysroot bugzilla at busybox.net
2017-03-22 20:35 ` [Buildroot] [Bug 9771] " bugzilla at busybox.net
2017-03-28 6:44 ` bugzilla at busybox.net
2017-03-28 20:04 ` bugzilla at busybox.net
2017-03-28 20:35 ` bugzilla at busybox.net
2017-03-28 20:43 ` bugzilla at busybox.net [this message]
2017-03-29 16:45 ` bugzilla at busybox.net
2017-03-30 9:30 ` bugzilla at busybox.net
2018-06-07 14:07 ` bugzilla at busybox.net
2019-08-10 23:38 ` bugzilla at busybox.net
2019-08-12 18:32 ` bugzilla at busybox.net
2024-06-15 14:47 ` bugzilla
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=bug-9771-163-vQGqVIWK2R@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.