From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12076] Patchelf can link against an incompatible libc++ version
Date: Fri, 02 Aug 2019 08:44:35 +0000 [thread overview]
Message-ID: <bug-12076-163-XDuJ7U9mnU@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12076-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12076
--- Comment #2 from Bradley Gamble <bradley.gamble@ncipher.com> ---
The build is completed in a single container without any sort of file
migration. My build commands are:
wget https://buildroot.org/downloads/buildroot-2019.05.1.tar.gz
tar -xvf ./buildroot-2019.05.1.tar.gz
cp ./baseimage/defconfig ./buildroot-2019.05.1/configs/custom_defconfig
make -C buildroot-2019.05.1 custom_defconfig
make -C buildroot-2019.05.1
This completes successfully, for example, on my host machine with newer
libraries.
In the container I am able to build and C++ applications without issue - We
compile many C++ binaries from source and this example of Patchelf is the only
failure we've encountered. I have demonstrated this by building a hello world
example:
$ cat helloworld.cpp
#include <iostream>
using namespace std;
int main()
{
cout << "Hello, World!";
return 0;
}
$ g++ helloworld.cpp -ohelloworld
$ ./helloworld
Hello, World!
I have uploaded the files here: https://gofile.io/?c=INwQ9u (Apologies for the
third-party host, the binaries are too big to upload even when compressed.)
This tarball contains the Patchelf binary and log from Buildroot, as well as
one I have manually compiled in the container. The Buildroot binary fails to
execute from within the container, whereas the manually built one executes
without issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-08-02 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 16:06 [Buildroot] [Bug 12076] New: Patchelf can link against an incompatible libc++ version bugzilla at busybox.net
2019-08-01 16:22 ` [Buildroot] [Bug 12076] " bugzilla at busybox.net
2019-08-02 8:44 ` bugzilla at busybox.net [this message]
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-XDuJ7U9mnU@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox