public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Alexey Neyman <noreply@github.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] af2f3a: libc: glibc 2.28 needs make 4.0
Date: Wed, 02 Oct 2019 04:17:00 -0000	[thread overview]
Message-ID: <crosstool-ng/crosstool-ng/push/refs/heads/master/b01fbc-715591@github.com> (raw)

  Branch: refs/heads/master
  Home:   https://github.com/crosstool-ng/crosstool-ng
  Commit: af2f3ac9c5454cb89d081405468ee5df58994ab4
      https://github.com/crosstool-ng/crosstool-ng/commit/af2f3ac9c5454cb89d081405468ee5df58994ab4
  Author: Chris Packham <judge.packham@gmail.com>
  Date:   2019-09-04 (Wed, 04 Sep 2019)

  Changed paths:
    M config/libc/glibc.in

  Log Message:
  -----------
  libc: glibc 2.28 needs make 4.0

Fixes: #1210

Per the release notes for the GNU C library 2.28[1] make 4.0 or newer is
required. Previously the logic was applied to glibc 2.29 or newer.

[1] - https://www.sourceware.org/ml/libc-alpha/2018-08/msg00003.html

Signed-off-by: Chris Packham <judge.packham@gmail.com>


  Commit: 715591306ff97f2838d15b5ac641db9098d7bf6f
      https://github.com/crosstool-ng/crosstool-ng/commit/715591306ff97f2838d15b5ac641db9098d7bf6f
  Author: Alexey Neyman <stilor@att.net>
  Date:   2019-10-01 (Tue, 01 Oct 2019)

  Changed paths:
    M config/libc/glibc.in

  Log Message:
  -----------
  Merge pull request #1231 from cpackham/glibc-2.28-make-4.0

libc: glibc 2.28 needs make 4.0


Compare: https://github.com/crosstool-ng/crosstool-ng/compare/b01fbcb8b05b...715591306ff9

                 reply	other threads:[~2019-10-02  4:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=crosstool-ng/crosstool-ng/push/refs/heads/master/b01fbc-715591@github.com \
    --to=noreply@github.com \
    --cc=crossgcc@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).