From: Randy Yates <yates@digitalsignallabs.com>
To: crossgcc@sourceware.org
Subject: Re: [crosstool-ng/crosstool-ng] 107e81: Add support for glibc 2.32
Date: Sun, 30 Aug 2020 10:16:04 -0400 [thread overview]
Message-ID: <23b151ff-e216-6a66-a3a5-9b8b5fe0bb82@digitalsignallabs.com> (raw)
In-Reply-To: <crosstool-ng/crosstool-ng/push/refs/heads/master/a2b4ea-4e5bc4@github.com>
T A K E M E O F F T H I S L I S T ! ! ! ! ! ! ! !
The instructions at the listserve do NOT work!
On 8/30/20 4:59 AM, Chris Packham via crossgcc wrote:
> Branch: refs/heads/master
> Home: https://github.com/crosstool-ng/crosstool-ng
> Commit: 107e8111c3f0dd394296d97cbaa20667b2e85e82
> https://github.com/crosstool-ng/crosstool-ng/commit/107e8111c3f0dd394296d97cbaa20667b2e85e82
> Author: Hans-Christian Noren Egtvedt <hegtvedt@cisco.com>
> Date: 2020-08-14 (Fri, 14 Aug 2020)
>
> Changed paths:
> A packages/glibc/2.32/0000-typedef-caddr.patch
> A packages/glibc/2.32/chksum
> A packages/glibc/2.32/version.desc
>
> Log Message:
> -----------
> Add support for glibc 2.32
>
> Forward ported 0000-typedef-caddr.patch from previous release (2.31).
>
> Dropped the 0001-Add-ARC-architecture.patch file, since ARC support is
> included in glibc release 2.32.
>
> Signed-off-by: Hans-Christian Noren Egtvedt <hegtvedt@cisco.com>
>
>
> Commit: 4e5bc43627582b11f11ebc1cedcfd1016f39c60e
> https://github.com/crosstool-ng/crosstool-ng/commit/4e5bc43627582b11f11ebc1cedcfd1016f39c60e
> Author: Chris Packham <judge.packham@gmail.com>
> Date: 2020-08-30 (Sun, 30 Aug 2020)
>
> Changed paths:
> A packages/glibc/2.32/0000-typedef-caddr.patch
> A packages/glibc/2.32/chksum
> A packages/glibc/2.32/version.desc
>
> Log Message:
> -----------
> Merge pull request #1371 from egtvedt/add-glibc-2.32
>
> Add support for glibc 2.32
>
>
> Compare: https://github.com/crosstool-ng/crosstool-ng/compare/a2b4eab30cbb...4e5bc4362758
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2020-08-30 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 8:59 Chris Packham
2020-08-30 14:16 ` Randy Yates [this message]
2020-08-30 16:57 ` Daniele Testa
2020-08-30 19:34 ` Christopher Faylor
2020-08-30 19:43 ` Daniele Testa
2020-08-30 19:58 ` Christopher Faylor
[not found] ` <6a6fa59c33b41435f6f907739d7d88cc1a153f33.camel@silogroup.org>
[not found] ` <24cde6c4-20c8-a583-fdd0-508f8ebd4dd4@digitalsignallabs.com>
[not found] ` <dad569fca04a8fcb23449f6f1e9836b6d468e6d7.camel@silogroup.org>
2020-08-30 20:04 ` Randy Yates
2020-08-30 20:15 ` Andrea Franceschini
2020-08-30 20:19 ` Unsubscribe problems apparently solved Christopher Faylor
2020-08-30 20:38 ` Bryan Hundven
2020-08-30 21:16 ` Christopher Faylor
2020-08-30 21:20 ` Chris Packham
2020-08-30 23:06 ` Christopher Faylor
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=23b151ff-e216-6a66-a3a5-9b8b5fe0bb82@digitalsignallabs.com \
--to=yates@digitalsignallabs.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).