Re: is --with-libexpat-prefix broken?

[Joel Brobecker <brobecker@adacore.com>]

> This is a horribly overcomplicated macro, originally from (IIRC)
> gettext.

Thank you for making me feel better, misery loves company :).

> I recommend running the configure script with sh -x to see what
> it's doing.

I was actually in the process of analyzing the output yesterday
when I had to scoot out. Will continue today.

> The only thing I noticed in the above was that there was no -I option,
> but the test file obviously compiled.  Could you have switched
> compilers and/or added an expat installation in /usr/local/include
> and /usr/local/lib?  GCC is ornery about searching /usr/local/include
> but not /usr/local/lib in some configurations.

Duh - You're right. I had switch from the slow AIX to a faster
sparc-solaris machine, but indeed, libexpat is installed in /usr/local.
It's still interesting to know that with the same compiler on the same
machine, 6.7.1 builds fine, whereas HEAD doesn't. And the cause is
double: No -I, and it doesn't try the archive, it requires the shared
library...

Back on AIX (sigh), the program doesn't compile, and configure
gives up immediately. So I can start again from there. Hopefully
more info on this soon.

-- 
Joel