From: Alexey Neyman <noreply@github.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 047260: Require 2.29 if building glibc for RISC-V64
Date: Wed, 10 Apr 2019 20:32:00 -0000 [thread overview]
Message-ID: <crosstool-ng/crosstool-ng/push/refs/heads/master/51f1db-b2151f@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 0472602b51f5baf5906c70d5a430233b0e8379f9
https://github.com/crosstool-ng/crosstool-ng/commit/0472602b51f5baf5906c70d5a430233b0e8379f9
Author: Alexey Neyman <stilor@att.net>
Date: 2019-04-10 (Wed, 10 Apr 2019)
Changed paths:
M config/arch/riscv.in
Log Message:
-----------
Require 2.29 if building glibc for RISC-V64
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: a90046a056e4bf43114d0fed8f1f909baa6ce054
https://github.com/crosstool-ng/crosstool-ng/commit/a90046a056e4bf43114d0fed8f1f909baa6ce054
Author: Alexey Neyman <stilor@att.net>
Date: 2019-04-10 (Wed, 10 Apr 2019)
Changed paths:
M testing/docker/ubuntu16.04/Dockerfile
M testing/docker/ubuntu18.04/Dockerfile
M testing/docker/ubuntu18.10/Dockerfile
Log Message:
-----------
Install python3, needed by recent GLIBC
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: b2151f1dba2b20c310adfe7198e461ec4469172b
https://github.com/crosstool-ng/crosstool-ng/commit/b2151f1dba2b20c310adfe7198e461ec4469172b
Author: Alexey Neyman <stilor@att.net>
Date: 2019-04-10 (Wed, 10 Apr 2019)
Changed paths:
M config/arch/riscv.in
M testing/docker/ubuntu16.04/Dockerfile
M testing/docker/ubuntu18.04/Dockerfile
M testing/docker/ubuntu18.10/Dockerfile
Log Message:
-----------
Merge pull request #1182 from stilor/master
Last fixes for 1.24
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/51f1db5c0aed...b2151f1dba2b
reply other threads:[~2019-04-10 20:32 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/51f1db-b2151f@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).