==================================== 1 of 1 test failed Please report to bagnara@cs.unipr.it ==================================== Hello, As requested by the compilation/tests/installation journal, I send you the complete installation journal. I hope it will be usefull. Host system is: uname -a ---> Linux amd64-3000.alphanet 2.6.32-71.24.1.el6.i686 #1 SMP Fri Apr 8 01:07:04 CDT 2011 i686 i686 i386 GNU/Linux following variables are forced build=host=target=i386-pc-linux-gnu for your information: softwares are installed on a private partition /slackware-data with prefix=/slackware-data/usr/local/arch-independent/i386-pc-linux-gnu/Linux_amd64-3000.alphanet_2.6.32-71.24.1.el6.i686 exec_prefix=/slackware-data/usr/local/arch-dependent/Linux_amd64-3000.alphanet_2.6.32-71.24.1.el6.i686/pc/amd64/athlon64/i386-pc-linux-gnu/ running different linux systems /slackware-data beeing only mount-point of partition, which has been created under linux-slackware-13.0 and contains an "ext4" filesystem "ppl-0.11.2" has been build running "Scientific-Linux-6.0" software which has been downloaded from http://ftp1.scientificlinux.org/linux/scientific/6/i386/iso/SL-60-i386-2011-... http://ftp1.scientificlinux.org/linux/scientific/6/i386/iso/SL-60-i386-2011-... thank you for your "ppl" software 2 configure/make/install processes were run =========================================== 1) Failure ---------- ==================================== 1 of 1 test failed Please report to bagnara@cs.unipr.it ==================================== export enable_more_assertions=yes export enable_ppl_lcdd=yes export enable_ppl_lpsol=yes export enable_ppl_pips=yes export with_libgmp_prefix=$gmp__lib_dir1 export with_libgmpxx_prefix=$gmp__lib_dir1 options0="--enable-option-checking=yes --disable-silent-rules --enable-dependency-tracking=yes --enable-debugging=yes --enable-profiling=yes --enable-coverage=yes --enable-assertions=yes --enable-optimization=yes --enable-arch=$architecture --disable-rpath --enable-watchdog=yes --enable-valgrind-tests=yes --enable-shared=yes --enable-static=yes --with-gnu-ld -srcdir=$srcdir --prefix=$prefix --exec-prefix=$exec_prefix" build=host=target=i386-pc-linux-gnu $srcdir/configure $options0 --build=$build --host=$host --target=$target complete journal in 20110516-2251____compile__pack__ppl____ppl-0.11.2____2bagnara____--enable-uname -a ---> =yes.zip 2) success : suppressing the "valgrind-tests" ------- export enable_more_assertions=yes export enable_ppl_lcdd=yes export enable_ppl_lpsol=yes export enable_ppl_pips=yes export with_libgmp_prefix=$gmp__lib_dir1 export with_libgmpxx_prefix=$gmp__lib_dir1 options0="--enable-option-checking=yes --disable-silent-rules --enable-dependency-tracking=yes --enable-debugging=yes --enable-profiling=yes --enable-coverage=yes --enable-assertions=yes --enable-optimization=yes --enable-arch=$architecture --disable-rpath --enable-watchdog=yes --enable-valgrind-tests=no --enable-shared=yes --enable-static=yes --with-gnu-ld -srcdir=$srcdir --prefix=$prefix --exec-prefix=$exec_prefix" build=host=target=i386-pc-linux-gnu $srcdir/configure $options0 --build=$build --host=$host --target=$target complete journal in 20110519-0837____compile__pack__ppl____ppl-0.11.2____2bagnara____--enable-valgrind-tests=no.out.zip Objectives of "options0" choice =============================== It was to verify coherence of a possible maximal combination of options, to "charge" the "ppl" software down from the "configure" possibilities, to avoid further disappointment when building "gcc". When I began to try to build the newest version of "gcc" , I discovered the existence of prerequisite "ppl", software and interesting researches I would never have heard about if not needed by "gcc". But this makes "ppl" software very visible for "gcc" users and builders, and every new package which is introduced comes with it's functionalities, possible bugs, and releases compatibility problems. The only way to avoid combination errors and waste of developpers' time, when merging all these softwares is to test strongly each of the prerequired softwares. Warning : conditions of tests ======= following variables are forced to build=host=target=i386-pc-linux-gnu though the host system is uname -a ---> Linux amd64-3000.alphanet 2.6.32-71.24.1.el6.i686 #1 SMP Fri Apr 8 01:07:04 CDT 2011 i686 i686 i386 GNU/Linux I reduced capabilities of built software, as I used "i386" which I see as a subset of "i686". Could reducing the "host" capabilities to "i386" on a host-system that is configured as a "i686" explain the failure of the configure/compilations/installation process of "ppl" when requiring "valgrind-tests" option? Charles --------------