From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12076] New: Patchelf can link against an incompatible libc++ version
Date: Thu, 01 Aug 2019 16:06:27 +0000 [thread overview]
Message-ID: <bug-12076-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12076
Bug ID: 12076
Summary: Patchelf can link against an incompatible libc++
version
Product: buildroot
Version: 2019.05.1
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: bradley.gamble at ncipher.com
CC: buildroot at uclibc.org
Target Milestone: ---
Attempting a build of buildroot can fail if the host machine is using an older
version of libstdc++. In this instance I was using a Docker container with
libstdc++ 3.4.13 (GLIBCXX_3.4.13).
The truncated output from the build is as follows:
>>> Sanitizing RPATH in target tree
/home/bgamble/buildroot-2019.05.1/support/scripts/fix-rpath target
Error: can't execute patchelf utility
'/home/bgamble/buildroot-2019.05.1/output/host/bin/patchelf'
make[1]: *** [target-finalize] Error 1
make: *** [_all] Error 2
Attempting to manually execute the patchelf binary will give the following
error message:
$ ./output/host/bin/patchelf
./output/host/bin/patchelf: /usr/lib/libstdc++.so.6: version
`GLIBCXX_3.4.20' not found (required by ./output/host/bin/patchelf)
This means that it is not possible to perform a build with an older version of
the libstdc++ library.
It is possible to build and execute patchelf manually using the host compiler
so I believe this is a Buildroot-specific issue and not caused by the upstream
Patchelf source.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-08-01 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 16:06 bugzilla at busybox.net [this message]
2019-08-01 16:22 ` [Buildroot] [Bug 12076] Patchelf can link against an incompatible libc++ version bugzilla at busybox.net
2019-08-02 8:44 ` bugzilla at busybox.net
2019-08-02 14:44 ` bugzilla at busybox.net
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-12076-163@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.