public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vanboxem.ruben at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/50139] New: in-tree GMP/PPL/CLooG is misconfigured Date: Sat, 20 Aug 2011 15:46:00 -0000 [thread overview] Message-ID: <bug-50139-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50139 Bug #: 50139 Summary: in-tree GMP/PPL/CLooG is misconfigured Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: bootstrap AssignedTo: unassigned@gcc.gnu.org ReportedBy: vanboxem.ruben@gmail.com Created attachment 25062 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25062 Patch When building the Graphite prereqs in-tree mkdir $GCC_SRC/ppl mkdir $GCC_SRC/cloog ln -s $SRC/ppl-0.11.2/* $GCC_SRC/ppl ln -s $SRC/cloog)0.16.3/* $GCC_SRC/cloog All subdirectories are detected well, but as some may or may not know, GMP in tree does not play well with PPL/CLooG in tree, and CLooG(-isl) does not work well in-tree. Attached is a patch to add the necessary paths in the various places, using existing infrastructure. Some notes before you ask yourself what I did: - PPL-0.11.2 has a configure option --with-gmp-build, but it does not seem to work as MPFR/MPC's options do (ie only the linker uses it, the include path still needed to be set by CPPFLAGS). My way is a bit more secure for older versions of PPL as well. - CLooG has an half-documented feature (not in the online docs, but you get it from "configure --help"): --with-gmp-builddir, which is equally broken, as the C compiler test tries to link with gmp. - PPL also needs both the gmp source as gmp build path, because it checks for gmpxx.h, which is not in the build directory, but gmpxx.h includes gmp.h, which is only present in the build directory. The 4.5 and 4.6 branches also work with the CLooG/PPL versions I used here (if built out-of-tree) so a fix for those branches would be very helpful as well.
next reply other threads:[~2011-08-20 15:39 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-20 15:46 vanboxem.ruben at gmail dot com [this message] 2011-08-21 10:49 ` [Bug bootstrap/50139] " vanboxem.ruben at gmail dot com 2011-08-21 11:06 ` vanboxem.ruben at gmail dot com 2014-12-30 4:41 ` nightstrike at gmail dot com
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-50139-4@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: linkBe 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).