Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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:34:41 +0000	[thread overview]
Message-ID: <bug-10091-163-nPr8LcYbQT@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 #4 from Ivan <ivan.nazarenko@gmail.com> ---
Build of gcc 7.1, with graphite support enabled, failed in the "checking isl >=
0.15" pass.

Disabling graphite allowed gcc build.

See https://gcc.gnu.org/install/prerequisites.html

While 6.x, 5.x and 4.9 still builds with isl 0.14, the gcc webpage specify isl
0.15 as the current minimum.

Verifying the ChangeLog-2016, 2015, etc files shows that in 2014 the dependency
of cloog was removed. This is true for the last gcc5.x, 6.x and 7.x.

But gcc4.x still depends on cloog.

So the options seems to be either:

- keep cloog, with corresponding old isl, and gcc4.x users have graphite, or
- removes cloog, new isl, and gcc7.1 users have graphite.

I am not aware if isl 0.15 would disrupt graphite in 5,x or 6.x. Improbable,
though, since 0.15 is from 2015 and the last gcc5.x from 2016.

I feel myself bit overwhelmed by builroot, and do not think I would be able to
experiment with anything beyond the trivial "make menuconfig". I do not event
know bash. But I would help where I can.





While I am completely bewildered by all this buildroot stuff (I am not even
familiar with bash), I though it would be nice to report failed builds. But do
not feel

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2017-07-17 17:34 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
2017-07-17 17:34 ` bugzilla at busybox.net [this message]
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-nPr8LcYbQT@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