ESyS-Particle

Fedora 16 configure problem

Asked by Mark Stock

Hello,

I'm a computational scientist interested in trying out ESyS-Particle, and have been on Fedora for about a decade. I've ran into some snags building the software, some of which were resolved searching this site. But, when I run

./configure CC=mpiCC CXX=mpic++ LDFLAGS="-L/usr/lib64/ -lboost_system" --with-boost-libdir=/usr/lib64 LIBS="-lboost_system" --with-boost-filesystem=boost_filesystem

(I just threw everything on there, but the error is the same without the last two arguments.)

I get, right at the end:

...
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
=== configuring in libltdl (/home/mstock/progs/ESyS-Particle-2.1/libltdl)
configure: WARNING: no configuration information is in libltdl

And when I %make, I get

$ make
make all-recursive
make[1]: Entering directory `/home/mstock/progs/ESyS-Particle-2.1'
Making all in libltdl
make[2]: Entering directory `/home/mstock/progs/ESyS-Particle-2.1/libltdl'
make[2]: *** No rule to make target `all'. Stop.
make[2]: Leaving directory `/home/mstock/progs/ESyS-Particle-2.1/libltdl'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/mstock/progs/ESyS-Particle-2.1'
make: *** [all] Error 2

But I have a libltdl, it's in:

$ rpm -qa | grep libtool
libtool-2.4-9.fc16.x86_64
libtool-ltdl-2.4-9.fc16.x86_64

I'm not sure what's going wrong. Do you have any suggestions?

Mark

Question information

Language:
English Edit question
Status:
Solved
For:
ESyS-Particle Edit question
Assignee:
No assignee Edit question
Solved by:
Mark Stock
Solved:
Last query:
Last reply:
Revision history for this message
Vince Boros (v-boros) said : 		#1

Hi Mark.

The configuration script creates the Makefile for libltdl/ under /home/mstock/progs/ESyS-Particle-2.1/. Since configure failed at this point, you then had no make instructions for libltdl/, which is why make failed. It seems that there was not even a configure scipt for libltdl/.

When you ran ./autogen.sh before ./configure CC=..., were there any odd messages? The Autotools invoked from autogen.sh should have generated a configure script for the local libltdl/.

Can you send me a directory listing of /home/mstock/progs/ESyS-Particle-2.1/libltdl/?

There is also config.log in the top directory for ESyS-Particle. Look in there for more information about the configure error and send me what you find.

Regards,

Vince

Revision history for this message
Mark Stock (mstock-v) said : 		#2

Vince,

Thanks for the reply. I totally forgot about the erorrs from the autogen step:

One of these:
libtoolize: `COPYING.LIB' not found in `/usr/share/libtool/libltdl'

And a number of these:
configure.ac:266: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from...
../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:606: AS_IF is expanded from...
../../lib/autoconf/general.m4:2032: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2053: AC_CACHE_CHECK is expanded from...
Config/ax_boost_filesystem.m4:33: AX_BOOST_FILESYSTEM is expanded from...
configure.ac:266: the top level

And also this, though it probably is subordinate to the above:
[mstock@persephone ESyS-Particle-2.1]$ ls -l libltdl/
total 8
drwxrwxr-x. 2 mstock mstock 4096 Nov 16 09:12 config
drwxrwxr-x. 2 mstock mstock 4096 Nov 16 09:12 m4

The config.log shows some errors when testing the compiler for "mpiCC option to accept ISO C89", and "g++: error: unrecognized option '-qlanglvl=extc89'", and "g++: error: unrecognized option '-qlanglvl=ansi'" It seems that the C compiler detection went awry, as "-std=c89" has been an option in gcc for years, whereas "-qlanglvl=extc89" is for the IBM compiler.

I hope this helps debug the problem. I have been browsing the examples guide and am excited to see what this code can do.

Mark

Revision history for this message
Vince Boros (v-boros) said : 		#3

Hello Mark.

Instead of "mpiCC" use "mpicc" on the configure line. On my system (Ubuntu 12.04) mpiCC points to /usr/bin/mpic++.openmpi instead of to /usr/bin/mpicc.openmpi. This may explain why the C compiler options are not being recognized. You never know, this may resolve the libltdl problem too.

There have been some changes in the build system since ESyS-Particle 2.1 was released. If you check out the latest revision from the Bazaar repository the autoconf warnings should disappear. (See steps 4 to 6 in this FAQ: https://answers.launchpad.net/esys-particle/+faq/1613)

Vince

Revision history for this message
Mark Stock (mstock-v) said : 		#4

Using "mpicc" instead of "mpiCC" did help with the config, but the build results are the same.

I used Bazaar to check out the dev version, and the config did produce fewer errors, though it still has this first one:

[mstock@persephone esys-particle]$ sh autogen.sh
libtoolize: `COPYING.LIB' not found in `/usr/share/libtool/libltdl'
configure.ac:68: installing `./config.guess'
configure.ac:68: installing `./config.sub'
configure.ac:44: installing `./install-sh'
configure.ac:44: installing `./missing'
Fields/Makefile.am: installing `./depcomp'
Python/esys/Makefile.am:18: installing `./py-compile'
revision-id: <email address hidden>
date: 2012-10-31 16:48:29 +0100
build-date: 2012-11-18 22:37:09 -0500
revno: 1078
branch-nick: esys-particle
bzr version header generated
[mstock@persephone esys-particle]$

And the ./configure still returns, at the end:

config.status: executing libtool commands
=== configuring in libltdl (/home/mstock/progs/esys-particle/libltdl)
configure: WARNING: no configuration information is in libltdl

And make fails in exactly the same way:

[mstock@persephone esys-particle]$ make
make all-recursive
make[1]: Entering directory `/home/mstock/progs/esys-particle'
Making all in libltdl
make[2]: Entering directory `/home/mstock/progs/esys-particle/libltdl'
make[2]: *** No rule to make target `all'. Stop.

Is my libtool too old, or is Fedora's libtool incompatible with ubuntu?

Revision history for this message
Mark Stock (mstock-v) said : 		#5

Okay, I found it. I needed to install the libtool-ltdl-devel package. Both the .tar.gz and the Bazaar versions are building now. I am sorry I didn't think of that sooner.

Revision history for this message
Vince Boros (v-boros) said : 		#6

Very good. I was getting around to the opinion that something was wrong with the libltdl installation, but i had not quite made it to a missing dev. package. I will make a note of the solution, since the problem you reported has appeared before, but in that case the reporter changed to Ubuntu and i did not pursue the matter. Thanks for the feedback and all the information you supplied.

All the best with using ESyS-Particle for your DEM modeling.

Vince