public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: dominiq@lps.ens.fr (Dominique Dhumieres)
To: howarth@bromo.med.uc.edu, dominiq@lps.ens.fr
Cc: tobias@grosser.es, rguenther@suse.de, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Allow new ISL/CLooG versions
Date: Mon, 14 Jan 2013 20:29:00 -0000	[thread overview]
Message-ID: <20130114202853.20F6D3BC70@mailhost.lps.ens.fr> (raw)
In-Reply-To: <20130114202039.GA22255@bromo.med.uc.edu>

Jack,

Without the change for isl, I get at configure time:

-g -O2 -I/opt/mp/include -I/opt/mp/include
checking for version 0.10 of ISL... no
-g -O2 -I/opt/mp/include -I/opt/mp/include
checking for version 0.11 of ISL... (cached) no
configure: error: Unable to find a usable ISL.  See config.log for details.

and after it but without the change for CLooG

checking for version 0.10 of ISL... yes
checking for version 0.17.0 of CLooG... no
checking for version 0.18.0 of CLooG... (cached) no

I don't know if this support your claim or not.

Dominique

  reply	other threads:[~2013-01-14 20:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 19:27 Dominique Dhumieres
2013-01-14 20:20 ` Jack Howarth
2013-01-14 20:29   ` Dominique Dhumieres [this message]
2013-01-14 20:45     ` Jack Howarth
2013-01-15  9:24   ` Richard Biener
2013-01-15 10:06     ` Richard Biener
2013-01-15 12:58       ` Jakub Jelinek
2013-01-15 14:07       ` Jack Howarth
2013-01-16  9:31         ` Richard Biener
2013-01-16  9:36           ` Richard Biener
  -- strict thread matches above, loose matches on Subject: below --
2013-01-14 20:18 Dominique Dhumieres
2013-01-14 14:29 Richard Biener
2013-01-14 15:44 ` Tobias Grosser
2013-01-14 16:03   ` Jack Howarth
2013-01-14 16:29     ` Jack Howarth
2013-01-14 18:20       ` Richard Biener
2013-01-14 20:04         ` Jack Howarth
2013-01-20 10:15 ` Eric Botcazou
2013-01-20 13:27   ` Richard Biener

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=20130114202853.20F6D3BC70@mailhost.lps.ens.fr \
    --to=dominiq@lps.ens.fr \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=howarth@bromo.med.uc.edu \
    --cc=rguenther@suse.de \
    --cc=tobias@grosser.es \
    /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).