From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10091] gcc7.1 does not build with graphite support due to old isl
Date: Mon, 17 Jul 2017 17:00:23 +0000 [thread overview]
Message-ID: <bug-10091-163-XuR09TzFpi@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10091-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10091
--- Comment #3 from Andrey Yurovsky <yurovsky@gmail.com> ---
I just tried bumping ISL and was able to build GCC7 with graphite (for ARMv5 in
this case), I'm trying to better understand the dependencies here but perhaps
ISL 0.18 doesn't need cloog or can work with the older version.
diff --git a/package/isl/isl.hash b/package/isl/isl.hash
index e2c14ad14..22941de42 100644
--- a/package/isl/isl.hash
+++ b/package/isl/isl.hash
@@ -1,2 +1,4 @@
# Locally computed
sha256 8882c9e36549fc757efa267706a9af733bb8d7fe3905cbfde43e17a89eea4675
isl-0.14.1.tar.xz
+sha256 0f35051cc030b87c673ac1f187de40e386a1482a0cfdf2c552dd6031b307ddc4
isl-0.18.tar.xz
+
diff --git a/package/isl/isl.mk b/package/isl/isl.mk
index 74de125b6..85d013723 100644
--- a/package/isl/isl.mk
+++ b/package/isl/isl.mk
@@ -7,7 +7,7 @@
# The latest 0.15 version is not yet compatible with cloog 0.18.3, so
# bumping isl is not possible until a new version of cloog is
# published.
-ISL_VERSION = 0.14.1
+ISL_VERSION = 0.18
ISL_SOURCE = isl-$(ISL_VERSION).tar.xz
ISL_SITE = http://isl.gforge.inria.fr
ISL_LICENSE = MIT
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-07-17 17:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 14:24 [Buildroot] [Bug 10091] New: gcc7.1 does not build with graphite support due to old isl bugzilla at busybox.net
2017-07-17 14:26 ` [Buildroot] [Bug 10091] " bugzilla at busybox.net
2017-07-17 15:15 ` bugzilla at busybox.net
2017-07-17 17:00 ` bugzilla at busybox.net [this message]
2017-07-17 17:34 ` bugzilla at busybox.net
2017-07-17 18:59 ` bugzilla at busybox.net
2017-07-17 20:54 ` bugzilla at busybox.net
2017-07-17 23:26 ` bugzilla at busybox.net
2017-07-17 23:39 ` bugzilla at busybox.net
2017-07-18 1:54 ` bugzilla at busybox.net
2017-07-18 17:58 ` bugzilla at busybox.net
2017-07-18 18:07 ` bugzilla at busybox.net
2017-07-18 19:42 ` bugzilla at busybox.net
2017-07-19 18:46 ` bugzilla at busybox.net
2017-07-21 12:19 ` bugzilla at busybox.net
2017-07-24 20:36 ` bugzilla at busybox.net
2017-08-02 20:17 ` bugzilla at busybox.net
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=bug-10091-163-XuR09TzFpi@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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