From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 96ff82: Linaro's 4.9 requires ISL 0.14 or older
Date: Thu, 19 Jan 2017 07:18:00 -0000 [thread overview]
Message-ID: <5880681549462_38313f8089abf13c1089c0@hookshot-fe1-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 96ff82e9ecee602d09390a9a911d2371228a6cad
https://github.com/crosstool-ng/crosstool-ng/commit/96ff82e9ecee602d09390a9a911d2371228a6cad
Author: Alexey Neyman <stilor@att.net>
Date: 2017-01-17 (Tue, 17 Jan 2017)
Changed paths:
M config/companion_libs/isl.in
Log Message:
-----------
Linaro's 4.9 requires ISL 0.14 or older
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 725fcbe1a7578ac331950b9e047d4098fb7bce49
https://github.com/crosstool-ng/crosstool-ng/commit/725fcbe1a7578ac331950b9e047d4098fb7bce49
Author: Alexey Neyman <stilor@att.net>
Date: 2017-01-17 (Tue, 17 Jan 2017)
Changed paths:
A patches/gcc/linaro-4.8-2015.06/132-build_gcc-5_with_gcc-6.patch
A patches/gcc/linaro-4.9-2016.02/132-build_gcc-5_with_gcc-6.patch
Log Message:
-----------
Linaro 4.9 does not have a fix for build with GCC5/6.
.. and 4.8 needs it, too.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 2bd87c8614fbb80225b91c0ab5315ecf80e3d308
https://github.com/crosstool-ng/crosstool-ng/commit/2bd87c8614fbb80225b91c0ab5315ecf80e3d308
Author: Alexey Neyman <stilor@att.net>
Date: 2017-01-18 (Wed, 18 Jan 2017)
Changed paths:
M config/companion_libs/isl.in
A patches/gcc/linaro-4.8-2015.06/132-build_gcc-5_with_gcc-6.patch
A patches/gcc/linaro-4.9-2016.02/132-build_gcc-5_with_gcc-6.patch
Log Message:
-----------
Merge pull request #546 from stilor/linaro-isl-dep
Linaro GCC dependencies & patches
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/c7b1e2957608...2bd87c8614fb
reply other threads:[~2017-01-19 7:18 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=5880681549462_38313f8089abf13c1089c0@hookshot-fe1-cp1-prd.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).