[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problem with ctl.h from libctl package

From: Ralf Wildenhues
Subject: Re: problem with ctl.h from libctl package
Date: Thu, 17 Aug 2006 20:42:27 +0200
User-agent: Mutt/1.5.12-2006-07-14

Hello Rhys,

Thanks for the bug report.

* Rhys Morris wrote on Thu, Aug 17, 2006 at 05:59:51PM CEST:
> I have been trying to build the mpb-1.4.2 package from MIT,

> and after much time in dependency hell, I have got all the 
> dependencies, and the final configure invocation is:
>  ./configure --with-lapack=/usr/local/LAPACK/lapack_LINUX.a 
> --with-hdf5=/usr/local/hdf5-1.8.0-alpha4/hdf5/lib/libhdf5.a 
> --with-libctl=/usr/local/share/libctl --includedir=/usr/local/include

If you are using a software distribution on your system, it may
be easier for you to install a precompiled package (or at least its
dependencies) from there.  For example, Debian ships mpb and its
dependencies.  (This is not to advertise, it's just that I don't
know which other software distributions do so as well, neither
which operating system you use.)

> and the last few lines of output are:

> checking ctl.h usability... yes
> checking ctl.h presence... no
> configure: WARNING: ctl.h: accepted by the compiler, rejected by the 
> preprocessor!
> configure: WARNING: ctl.h: proceeding with the preprocessor's result
> checking for ctl.h... no
> configure: error: Couldn't find the libctl header.

The underlying error for the WARNINGS this can be found in the
corresponding part of the file 'config.log'.  Without it, I'm afraid
we cannot tell you what exactly went wrong.

But even with the file, usually either you or the maintainer of the
package will know much better how to deal with remaining problems.

If in doubt, please report back here; but the maintainer of mpb knows
his way with Autoconf pretty well, so my guess would be that he can help
you better than we could.  You could suggest to him to use a newer
Autoconf version (2.60 is the current one) for the next release.

> I attach the clt.h file and the configure file.

Please don't send such large messages.  Also note that the configure
script itself is pretty useless (we could have loaded it from the web
site ourself), what would have been useful is the part of the config.log
file that contains the test that failed, including command line and
error output.  If in doubt, it can be useful to send a whole config.log
file, but I for one would then prefer it packed (with gzip, for

Hope that helps.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]