Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/m4: fix build in host with glibc-2.28
Date: Fri, 24 Aug 2018 10:46:12 +0200	[thread overview]
Message-ID: <878t4wjgob.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180817123803.13807-1-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Fri, 17 Aug 2018 14:38:03 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > glibc-2.28 did quite some lifting in their headers, which breaks the
 > way some packages were detecting glibc, like gnulib.

 > However, packages do bundle gnulib (it was meant to be bundled),
 > and so does m4.

 > Since m4 hasn't seen the slightest commit since 2017-01-09, it is
 > bundling an old gnulib version, that predates glibc-2.28, and thus
 > breaks. It also means that upstream hasn't already fixed the issue.

 > Furthermore, as upstream is using a git submodule for gnulib, and
 > that the paths are not the same in the release tarball (in lib/)
 > and in the git ttree (in gnulib/), we can't do a plain backport.

 > So, we selectively backport the two patches from gnulib upstream,
 > restricted to only the files that happen to be used in m4.

 > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
 > Reported-by: c32 on IRC

Committed to 2018.02.x and 2018.05.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2018-08-24  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 12:38 [Buildroot] [PATCH] package/m4: fix build in host with glibc-2.28 Yann E. MORIN
2018-08-17 16:57 ` Peter Korsgaard
2018-08-17 21:34 ` Thomas Petazzoni
2018-08-24  8:46 ` Peter Korsgaard [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=878t4wjgob.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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