All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 01 Aug 2019 16:22:58 +0000	[thread overview]
Message-ID: <bug-12076-163-2zFGa0OI3U@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 #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
I don't really see how this can happen, since Buildroot is building patchelf
for the host before running it. The only reasons why it could fail like this is
if:

 - The patchelf binary is built on one system, and move to another, which has
an older libstdc++ library

 - The system on which you're doing the build has some kind of
configuration/installation issue, and the C++ programs being built cannot be
executed.

All what Buildroot is doing is to build host-patchelf, which basically uses
your system g++ compiler.

Could you attach the broken patchelf binary ? Could you also attach the build
log of the host-patchelf package ?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2019-08-01 16:22 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 ` bugzilla at busybox.net [this message]
2019-08-02  8:44 ` [Buildroot] [Bug 12076] " 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-2zFGa0OI3U@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.