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 12596] host-e2fsprogs: tune2fs incompatibility on older glibc version
Date: Mon, 18 May 2020 06:45:31 +0000	[thread overview]
Message-ID: <bug-12596-163-ZtsYL2hs4Q@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12596-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=12596

Thomas Petazzoni <thomas.petazzoni@bootlin.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #4 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
Unfortunately, this is not something that we can really solve. You have to
build your SDK in a host that is equal or older to the host machines where the
SDK will be used.

https://stackoverflow.com/a/2858996/643208 has a possible solution, but it
requires making ugly changing to the source code of packages.

https://stackoverflow.com/a/52550158/643208 proposes to build your own glibc.

Hm, https://github.com/wheybags/glibc_version_header seems interesting though,
but it says that it doesn't work for C++, "If you want C++, you'll need to
build libstdc++ with this enabled. That can be a little involved, but I'm
working on a solution, to be available "soon"".

pthread also might be causing problems, you must use -pthread and not
-lpthread.

So, this seems like a potential source of great pain :-/

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

      parent reply	other threads:[~2020-05-18  6:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02 21:00 [Buildroot] [Bug 12596] New: host-e2fsprogs: tune2fs incompatibility on older glibc version bugzilla at busybox.net
2020-03-02 21:35 ` [Buildroot] [Bug 12596] " bugzilla at busybox.net
2020-03-02 21:54 ` bugzilla at busybox.net
2020-03-03 21:38 ` bugzilla at busybox.net
2020-05-18  6:45 ` bugzilla at busybox.net [this message]

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-12596-163-ZtsYL2hs4Q@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.