Some questions on the configure scripts

[Jeroen Ruigrok/Asmodai <asmodai wxs nl>]

Hi,

I'm trying to resolve the last few problems for FreeBSD with glib and GTk+.

glib 1.2.0 configured and compiled just great.

However, configure of 1.2.0 of GTk+ is giving me a hard time.

[asmodai@daemon] (252) $ pwd
/usr/local/include

[asmodai@daemon] (253) $ ll libin*
4 -rw-r--r--  1 root  wheel  - 3715 Feb 28 20:02 libintl.h

ac_default_prefix of configure is set to /usr/local

so that would make includedir='${prefix}/include' be
includedir=/usr/local/include

yet:

[asmodai@daemon] (262) $ ./configure 

[ ..snip.. ]

checking whether NLS is requested... yes
checking for libintl.h... no

[ ..snip.. ]

configure tries to check for libintl.h by #include <libintl.h> it. Yet
config.log yields:

configure:3654: checking for libintl.h
configure:3664: gcc -E  conftest.c >/dev/null 2>conftest.out
configure:3660: libintl.h: No such file or directory

Yet if I make a program like this:

#include <libintl.h>
main(){};

and gcc test.c -I/usr/local/include

it compiles.

Funny thing is that Gnome-libs does this (from config.log):

configure:4814: checking for libintl.h
configure:4824: gcc -E  -I/usr/X11R6/include -I/usr/local/lib/glib/include
-I/usr/local/include conf
test.c >/dev/null 2>conftest.out

So apparantly the configure script is leaving the -I's out of the
compilation test phase. Although I don't have a clue where in the autoconf
stuff I have to look for that. Both configures are made by autoconf 2.13,
at least, that's what the comment headers say.

We already had to hack gettext in a few ways on FreeBSD 3.x and higher for
it to make the shared libraries. But this problem is a GTk+ configure
script problem (which I finally managed to hunt down).

Does this have to do with CPPFLAGS not being set properly?

config.status of gnome-libs: s%@CPPFLAGS@% -I/usr/X11R6/include
-I/usr/local/lib/glib/include -I/usr/local/include%g

config.status of GTk+: s%@CPPFLAGS@%%g

Bingo!

But why doesn't this get set automatically? I see CPPFLAGS in INSTALL being
mentioned, but isn't it logical that /usr/local/include should be usable
_without_ needing to specify CPPFLAGS before configure?

Thanks for any insights,

---
Jeroen Ruigrok van der Werven      http://www.freebsdzine.org> 
asmodai(at)wxs.nl        The idea does not replace the work...
Network/Security Specialist      <http://home.wxs.nl/~asmodai>
*BSD: Powered by Knowledge & Know-how <http://www.freebsd.org>