Issues

This page should provide a little help dealing with compilation issues.

Library Files

Remember to add the location of the library files to the load path:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:{lib_location}

You can do this via the command line or by putting it in your .bashrc

pkg-config Issues

The following error happens if the pkg-config macros cannot be found by automake.

./configure: line 10638: PKG_PROG_PKG_CONFIG: command not found
checking for library containing pow... -lm
./configure: line 10703: syntax error near unexpected token `DEPS,'
./configure: line 10703: `PKG_CHECK_MODULES(DEPS, muparser >= 2.2.2 gmp >= 4.13)'

The macros are contained in the file pkg.m4. You should be able to add them to the local macro file by using something like aclocal --install -I /usr/share/aclocal. This command will install macro files that it finds in the directory provided. If you provide it with the directory containing pkg.m4, then the above issue should be resolved. You should then run the following, and the configuration should complete.

$ autoconf
$ ./configure

Running valgrind

To run valgrind on an executable generated by autotools, you should add libtool --mode=execute valgrind before runnning the executable, as below.

libtool --mode=execute valgrind ./launcher -e params.txt -a iwls

This is equivalent to

libtool e valgrind ./launcher -e params.txt -a iwls

Installing muParser for all users

To install any package for all users, it must be installed to /usr/bin, or for library files to /usr/include. In our case, we wish to have all the .h files that muParser uses in the /usr/include directory. The following will do this for us.

./configure --prefix=/usr
make
make install