Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11246] New: Glibc 2.28 - fails to build host-bison and host-m4
Date: Fri, 17 Aug 2018 18:11:04 +0000	[thread overview]
Message-ID: <bug-11246-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 11246
           Summary: Glibc 2.28 - fails to build host-bison and host-m4
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: happycorsair at yandex.ru
                CC: buildroot at uclibc.org
  Target Milestone: ---

Bleeding edge Linux distros (such as Arch Linux or Fedora) have switched some
time ago to glibc 2.28. It has broken building of bison and m4 host packages.

It can be fixed by using these patches (the same problem was found in Fedora
and OpenWRT):

https://github.com/openwrt/openwrt/commit/8ae84899865ea14ce9d55cffa5de5ddd7167c680

https://github.com/openwrt/openwrt/blob/e5d47f32131849a69a9267de51a30d6be1f0d0ac/tools/bison/patches/110-glibc-change-work-around.patch

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

             reply	other threads:[~2018-08-17 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 18:11 bugzilla at busybox.net [this message]
2018-08-17 21:35 ` [Buildroot] [Bug 11246] Glibc 2.28 - fails to build host-bison and host-m4 bugzilla at busybox.net
2018-08-29 20:07 ` 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-11246-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox