On Jul 16, 2007, at 2:45 PM, Joao Miguel Ferreira wrote:
Hello,
Hello Joao Miguel,
another bump in may way through Solaris...it seems the ./configure of my helloworld application does not find theheader files of the LIB it needs to work (libbabel and some lang*.h headers) It works just fine on Linux and HP-UX. I'm quite sure the lib is installed and the headers are instaled (I installed them all). Both Linux and HP-UX are able to find them. Solaris isn't.I guess this should be some kind of /path/to/includes problem... well...maybe I will also bump into a /path/to/libs problem too.. Please see snipet bellow: -------------- ... checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking langs.h usability... no checking langs.h presence... no checking for langs.h... no configure: error: libbabel headers not found -bash-3.00$ ls /usr/local/include/ lang_en.h lang_fr.h lang_pt.h langs.h -bash-3.00$ -------------------
Well, I don't see why it should work. Maybe some Linux distros chose to put /usr/local/include in the default include path of their compiler, but I don't think this is mandatory. Moreover, your library is not necessarily installed under /usr/local (think of a user that ./configure your package with --prefix=$HOME/local).
The usual way to deal with this is to add a --with-libfoo=PATH option to your configure script that users will use to tell where libfoo has been installed. If they don't provide a --with-libfoo argument, you can assume that they expect to find libfoo in their compiler's standard include and lib directories.
Cheers, -- Benoit Sigoure aka Tsuna EPITA Research and Development Laboratory
Attachment:
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
