public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 782b45: Supply "very old" and "very new" glibc versions
Date: Tue, 23 Oct 2018 05:38:00 -0000	[thread overview]
Message-ID: <5bceb3b02a012_5fe52af68a7b85942654e@hookshot-fe-cace476.cp1-iad.github.net.mail> (raw)

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

  Branch: refs/heads/master
  Home:   https://github.com/crosstool-ng/crosstool-ng
  Commit: 782b45d0dab33e910678ca2d01ca746041313348
      https://github.com/crosstool-ng/crosstool-ng/commit/782b45d0dab33e910678ca2d01ca746041313348
  Author: Alexey Neyman <stilor@att.net>
  Date:   2018-10-21 (Sun, 21 Oct 2018)

  Changed paths:
    M scripts/build/cc/gcc.sh

  Log Message:
  -----------
  Supply "very old" and "very new" glibc versions

... as 1.0 and 99.99, respectively, to gcc configure.

Fixes #1031.

Signed-off-by: Alexey Neyman <stilor@att.net>


  Commit: ee829c25eb374386ec1d5df2250a8a52f0f9d4a1
      https://github.com/crosstool-ng/crosstool-ng/commit/ee829c25eb374386ec1d5df2250a8a52f0f9d4a1
  Author: Alexey Neyman <stilor@att.net>
  Date:   2018-10-22 (Mon, 22 Oct 2018)

  Changed paths:
    M scripts/build/cc/gcc.sh

  Log Message:
  -----------
  Merge pull request #1065 from stilor/glibc-version

Supply "very old" and "very new" glibc versions


Compare: https://github.com/crosstool-ng/crosstool-ng/compare/6b53ad77c25f...ee829c25eb37
      **NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/

      Functionality will be removed from GitHub.com on January 31st, 2019.

                 reply	other threads:[~2018-10-23  5:38 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=5bceb3b02a012_5fe52af68a7b85942654e@hookshot-fe-cace476.cp1-iad.github.net.mail \
    --to=stilor@att.net \
    --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).