FreeTDS Development Group

["Varley, David(CBorn at Alcoa)" <David.Varley AT alcoa.com.au>]

Thanks guys, I think I've got it now :)

"configure" is normally regarded as "source" and not changed
when building, so its in the right place and running it or
"make" should not change anything in the source tree.

However the problem I encountered was due to an incorrect
"configure" script, and so I needed to regenerate it using
autogen.sh

The rebuilt "configure" script should be the same on all
platforms, however it may vary depending on the tools used
to build it. In my case the autoconf was the same, but some
other tools had slightly different versions.

Another interesting thing I noted was that even when these
tools were built from the same source, they themselves could
have different versions depending  on the tools they were
built with (gcc 2.7/2.96/3.1/3.2 etc). And those tools
themselves required the autoconf tools to build, so achieving
consistency may require several build cycles. Much fun :)

Cheers,

David

> -----Original Message-----
> From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> Sent: Thursday, 10 October 2002 2:39 AM
> To: TDS Development Group
> Subject: [freetds] RE: WARNING: update your autoconf
> 
> 
> Il mer, 2002-10-09 alle 13:35, Varley, David(CBorn at Alcoa) 
> ha scritto:
> > Thanks again, Freddy, thats great, works now.
> > 
> > Brings up something that puzzles me, though.
> > I'm using a common freetds source directory, with separate
> > build trees on Linux and Tru64 systems. I thought that the
> > source tree would remain constant, same "configure" file,
> > as this is how a normal (non-CVS) distribution would be
> > packaged.
> > And I'm using AutoConf 2.54, again built from common source,
> > on each of the platforms.
> > However when I build with autogen.sh, I get a different
> > "configure" script in the freetds source directory depending
> > whether I build on Linux or Tru64, with the one built on Tru64
> > being 400086 bytes and the Linux-built one 412606 bytes.
> > 
> 
> autogen.sh execute some program (automake, autoconf, m4 and 
> other) so is
> normal that compiling in a different machine output is different.
> 
> You should just run autogen.sh in a machine where you have the most
> recent software and use configure to configure software (just pass
> --help param to autogen.sh and run configure).
> 
> Many software do not distribute autogen.sh (only configure), we
> distribute even autogen.sh only because people that want to rebuild
> configure stuff can do it.
> 
> freddy77
> 
> 
> 
> ---
> You are currently subscribed to freetds as: 
> [David.Varley AT alcoa.com.au]
> To unsubscribe, forward this message to 
> $subst('Email.Unsub')
>