This is the mail archive of the
mailing list for the GCC project.
Re: Graphite build fails if PPL configured with --disable-shared
- From: Roberto Bagnara <bagnara at cs dot unipr dot it>
- To: janis187 at us dot ibm dot com
- Cc: Ian Lance Taylor <iant at google dot com>, gcc at gcc dot gnu dot org, "The Parma Polyhedra Library developers' list" <ppl-devel at cs dot unipr dot it>
- Date: Tue, 12 May 2009 18:46:57 +0200
- Subject: Re: Graphite build fails if PPL configured with --disable-shared
- References: <email@example.com> <1242072864.6516.18.camel@janis-laptop>
Janis Johnson wrote:
On Mon, 2009-05-11 at 13:07 -0700, Ian Lance Taylor wrote:
Another Graphite build issue: it appears that I must not use
--disable-shared when I configure PPL. If I do use --disable-shared, I
/home/iant/gnu/ppl-0.10.2-install/lib/libppl_c.a(ppl_c_implementation_common.o): In function `finalize':
/home/iant/gnu/ppl-0.10.2/interfaces/C/../../src/ppl.hh:1842: undefined reference to `operator delete(void*)'
followed by thousands of similar errors. This is unfortunate, as it
means that I must manually set LD_LIBRARY_PATH to the directory where
the PPL library is installed. This also makes it harder for anybody
else to run the compiler that I build. This needs to be fixed.
I get around this by setting LDFLAGS for the ppl configure:
I am not sure I understand: we trust that Libtool, which provides us
with the --disable-shared option, will do the right thing. And it
seems it does here: the static library is built and passes its checks.
Perhaps you want something different from what --disable-shared promises,
that is, not to build any shared libraries?
I copy libstdc++.a into the directory with the other GCC host
Building these libraries is indeed quite painful.
Any suggestion about how to improve the PPL is welcome. This, of course,
applies also to the build machinery.
All the best,
Prof. Roberto Bagnara
Computer Science Group
Department of Mathematics, University of Parma, Italy