[Dillo-dev]Bug #349

[Manuel M. <mm...@hu...>]

Hey,

While porting Dillo to the new implementation of POSIX threads for
GNU/Hurd (code name: "Rubbish, I asked for mine with Minced Garlic,
Please Take this back"), I found some minor  « bugs » in the Dillo
"installation system". The first bug I found out was a bug that was
already reported as #349 in the Dillo bug report system. It seems a
quite simple and not so annoying bug, but in fact it is quite pervert,
as it makes the configure misdetect what is installed in the system:
when it checks for jpeglib.h (& others), it tries to preprocess a simple
C file which only includes jpeglib.h, and check if there is some
output. If there is some output, then it assumes there is no
jpeglib.h. Which is not true in this case: the output is just warning
of cpp, which complains about the « -I/usr/local/include » (cpp 3.1
already has /usr/local/include it its system directories). 

 There is a simple way to fix it, though. And Here is a patch:

diff -pru old/dillo-0.6.6/configure dillo-0.6.6/configure
--- old/dillo-0.6.6/configure   2002-09-29 12:41:20.000000000 +0200
+++ dillo-0.6.6/configure       2002-09-29 12:40:57.000000000 +0200
@@ -1494,8 +1494,8 @@ ac_config_headers="$ac_config_headers co
 ac_config_commands="$ac_config_commands default-1"


-CPPFLAGS="$CPPFLAGS -I/usr/local/include"
-LDFLAGS="$LDFLAGS -L/usr/local/lib"
+CPPFLAGS="$CPPFLAGS -idirafter=/usr/local/include"
+LDFLAGS="$LDFLAGS -idirafter=/usr/local/lib"

idirafter makes cpp check /usr/local/include AFTER its system
directories (and the other -I'ed directories), so it doesn't complain
any more, and though it does include /usr/local/include on systems where
cpp doesn't have it in its system directories. This seems to fix my bug
and #349's reporter one. 

HTH,

-- 
Manuel Menal