From: Laurent GUERBY <laurent@guerby.net>
To: Roberto Bagnara <bagnara@cs.unipr.it>
Cc: janis187@us.ibm.com, Ian Lance Taylor <iant@google.com>,
gcc@gcc.gnu.org,
The Parma Polyhedra Library developers' list
<ppl-devel@cs.unipr.it>
Subject: Re: Graphite build fails if PPL configured with --disable-shared
Date: Tue, 12 May 2009 19:31:00 -0000 [thread overview]
Message-ID: <1242153862.20334.54.camel@localhost> (raw)
In-Reply-To: <4A09A801.8070702@cs.unipr.it>
On Tue, 2009-05-12 at 18:46 +0200, Roberto Bagnara wrote:
> Any suggestion about how to improve the PPL is welcome. This, of course,
> applies also to the build machinery.
Hi Roberto,
I added some instructions on how to build to the GCC wiki (end of page):
http://gcc.gnu.org/wiki/Graphite_Build
They worked with ppl-0.10 and cloog-ppl-0.15 however they now
fail with ppl-0.10.2 and cloog-ppl-0.15.3 on cloog-ppl-0.15.3 configure:
...
checking for ppl_c.h... no
configure: error: Can't find PPL headers.
Looking at config.log:
configure:20698: gcc -c -g -O2 -I/include
-I/n/17/guerby/install-ppl2/gmp-4.2.4/include conftest.c >&5
configure is not adding the -I for ppl hence the failure. I checked
and the wanted ppl_c.h was correctly installed so I don't
think ppl-0.10.2 is the issue.
Looking more at cloog-ppl/configure I find stuff like:
<<
# Check whether --with-ppl or --without-ppl was given.
if test "${with_ppl+set}" = set; then
withval="$with_ppl"
fi;
# Check whether --with-polylib_prefix or --without-polylib_prefix was given.
if test "${with_polylib_prefix+set}" = set; then
withval="$with_polylib_prefix"
fi;
# Check whether --with-polylib_exec_prefix or --without-polylib_exec_prefix was given.
if test "${with_polylib_exec_prefix+set}" = set; then
withval="$with_polylib_exec_prefix"
fi;
# Check whether --with-polylib_builddir or --without-polylib_builddir was given.
if test "${with_polylib_builddir+set}" = set; then
withval="$with_polylib_builddir"
fi;
>>
Wich is obviously broken since all the tests are setting the same
variable $withval and so --with-ppl just doesn't work. I looked at
cloog-ppl-0.15 configure and it was ok.
Now I don't know how to fix configury stuff but may be someone
can help here.
Also it would be nice if cloog-ppl-0.15.3.tar.gz top level
directory was named with version "cloog-ppl-0.15.3" instead of the
current version-less "cloog-ppl".
Thanks for your help,
Laurent
next prev parent reply other threads:[~2009-05-12 18:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 20:13 Ian Lance Taylor
2009-05-11 20:13 ` Andrew Pinski
2009-05-11 20:14 ` Andrew Pinski
2009-05-11 23:45 ` H.J. Lu
2009-05-11 23:48 ` Janis Johnson
2009-05-12 17:45 ` Roberto Bagnara
2009-05-12 18:05 ` Ian Lance Taylor
2009-05-12 19:31 ` Laurent GUERBY [this message]
2009-05-12 19:49 ` Andreas Schwab
2009-05-12 20:03 ` Laurent GUERBY
2009-05-12 20:25 ` Andreas Schwab
2009-05-12 20:48 ` Laurent GUERBY
2009-07-08 19:18 ` Maik Beckmann
2009-05-12 21:39 ` Janis Johnson
2009-05-12 8:13 ` Laurent GUERBY
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=1242153862.20334.54.camel@localhost \
--to=laurent@guerby.net \
--cc=bagnara@cs.unipr.it \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=janis187@us.ibm.com \
--cc=ppl-devel@cs.unipr.it \
/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).