Dave Korn wrote:
Roberto Bagnara wrote:
Dave Korn wrote:
Target: i686-pc-cygwin, cygwin-1.7.0-42, gcc-4.3.2, ppl configured with
--enable-shared --disable-static, no -fexceptions, no --enable-cxx.
I am not following here. There are no "-fexceptions" and "--enable-cxx"
in the PPL configuration procedure. In contrast, "--enable-cxx"
is an option of GMP's configuration procedure. Moreover, if GMP was
not compiled with the C++ interface enabled there is no way the PPL
can work (even though compilation should fail in such case).
Apologies for being unclear. This is the commandline I used to configure
with (from my bash history):
456 ./configure --prefix=/opt/gcc-tools -v --disable-static
--enable-shared 2>&1 | tee conf.log
I assume --disable-static is OK for Cygwin.
This is the tail of conf.log
configure: WARNING: CANNOT PROPAGATE EXCEPTIONS BACK FROM GMP:
*** MEMORY EXHAUSTION MAY RESULT IN ABRUPT TERMINATION.
*** This is OK, if you do not plan to use the bounded memory capabilities
*** offered by the PPL. Otherwise, if you are using GCC or the Intel C/C++
*** compiler, please make sure you use a version of GMP compiled with the
*** `-fexceptions' compiler option.
*** To build such a version, you can configure GMP as follows:
*** CPPFLAGS=-fexceptions ./configure --enable-cxx --prefix=/usr/local
I just meant to say that I had seen this warning and /not/ acted on it.
That's OK. I mean, CLooG does not use that capabilities, so there is no
problem here.
We also need the files config.log and
config.h generated by PPL's configure script.
Do you still want these in light of the above information?
Yes, please.
Thanks,
Roberto
--
Prof. Roberto Bagnara
Computer Science Group
Department of Mathematics, University of Parma, Italy
http://www.cs.unipr.it/~bagnara/
mailto:bagn...@cs.unipr.it
