First it couldn't find libast. That was legitimate - so I install libast and expect all to be well.
So now it constructs a compiler command line that gcc chokes on.
That's fine, I tell it to use cc instead and it can't find libast. The reason is simple - it's putting the
-lastahead of the
-Lswitch to tell it where the library is.
So I fix that and the compile just blows up. Looking more closely:
cc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/i clude
-I/usr/local/i clude -I/usr/ope wi /i clude -O -c
actions.c -KPIC -DPIC -o .libs/actions.lo
Look closely: it's whacked all the
n's out of the include directories.
So I randomly shuffle my PATH (presumably it's found a sed it doesn't like, but isn't that the sort of thing that autoconf is supposed to solve?) and eventually get it to work.
Won't compile. The code simply isn't liked by the Sun compiler.
Ho hum. Back to gcc - let's try a different version. OK, so I get it to configure and make, but it still fails, this time with an Undefined symbol error.
The upshot of all this is that autoconf has just wasted 10 minutes of my time and completely failed to produce a successful result at the end of it all.
Sadly, this is becoming the norm.