FreeTDS Development Group

["James K. Lowden" <jklowden AT speakeasy.org>]

James Cameron wrote:

> Brian Bruns wrote:
> > James, if you're reading this we may just want to say something in the
> > FAQ about why those messages appear and that they are harmless.
>
> If you mean me ... I think the cause of Andrew Bowman's problem might be
> the lag in autoconf or automake versions.  Rather than executing the
> configure straight out, he might like to try executing automake and
> autoconf first.
>

Actually, I think Brian was refering to me, as self-appointed FAQ master.

However, your answer shed a little light on it for me.  I've tried half a 
dozen times
to make any sense of the autoconf info pages.  I never can seem to hold 
enough of it
in my head at once to make any one part stick to any other two.  I'm sure 
that's at
least partly because I've never had to solve the problem it addresses.  Or it 
suffers
from what a lot of meta-meta-meta modeling does: discussion in great detail of
zero-mass hyper-abstractions.  Or, I suffer from lateness of hour.  Sigh.

I'm happy to fax the FAQ, if I can say something intelligent.  Which 
unfortunately I
can't just yet, but I'll read the libtool info pages (with more focus this 
time) and
try to come up with something.  I'm not even sure at this moment which 
message Brian
means to ignore.  I guess: AC_TRY_RUN.

I know there're a few hangers out here, who have discussed autoconf stuff and 
seem to
know something.  Maybe some kind soul will try to fix your Tru64 UNIX cc 
problem and
this libtool thing.  So we, uh, can call ourselves (ahem) a true multiplatform
project?

All that said, what exactly do you mean by " the lag in autoconf or automake
versions"?  If you could spell it out for your somewhat dim-witted editor, 
he'd be
ever so much obliged.

--jkl