public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manfred99 at gmx dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/61792] [4.10 Regression] Bootstrap error with undeclared function isl_ast_expr_get_val
Date: Wed, 16 Jul 2014 10:02:00 -0000	[thread overview]
Message-ID: <bug-61792-4-zKpSif3z9X@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61792-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61792

--- Comment #10 from Manfred Schwarb <manfred99 at gmx dot ch> ---
Dominique, you are right.
The issue is not with isl-0.12 and isl-0.13.

It is isl-0.11 that is missing these include files. So with the
above mentioned check-in, building GCC using isl-0.11 does no longer work.

I just could build trunk successfully now, using isl-0.12.2.

One should rip isl-0.11 support out of configure etc. therefore.


OK, I see what could have happened to Thomas: GMP support in isl
is optional. If you build isl without gmp headers being present,
then probably you wont get the needed headers to compile GCC.

So it seems isl-0.12.2 with GMP support is needed to build graphite.


  parent reply	other threads:[~2014-07-16 10:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-13 11:40 [Bug bootstrap/61792] New: " tkoenig at gcc dot gnu.org
2014-07-13 11:40 ` [Bug bootstrap/61792] " tkoenig at gcc dot gnu.org
2014-07-13 13:34 ` tkoenig at gcc dot gnu.org
2014-07-13 18:12 ` tkoenig at gcc dot gnu.org
2014-07-14 10:32 ` rguenth at gcc dot gnu.org
2014-07-15 18:42 ` tkoenig at gcc dot gnu.org
2014-07-15 20:43 ` manfred99 at gmx dot ch
2014-07-15 22:33 ` dominiq at lps dot ens.fr
2014-07-15 23:03 ` manfred99 at gmx dot ch
2014-07-15 23:26 ` dominiq at lps dot ens.fr
2014-07-16 10:02 ` manfred99 at gmx dot ch [this message]
2014-07-16 12:11 ` grosser at gcc dot gnu.org
2014-11-19 13:57 ` [Bug bootstrap/61792] [5 " rguenth at gcc dot gnu.org

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-61792-4-zKpSif3z9X@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).