Skip to Content.
Sympa Menu

freetds - RE: WARNING: update your autoconf

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Castellano, Nicholas" <Nicholas_Castellano AT acml.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: WARNING: update your autoconf
  • Date: Wed, 9 Oct 2002 10:40:09 -0400


I get an identical "configure" file from running autogen.sh on my NetBSD and
OSF/1 systems.

Are all your build tools (autoconf, automake, libtool, m4, etc.) the same
version on both platforms?

Perhaps "diff -u" output would shed some light on the cause of the
discrepancy.

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Wednesday, October 09, 2002 7:35 AM
To: TDS Development Group
Subject: [freetds] RE: WARNING: update your autoconf


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.

I don't know whether this means I should always re-autogen
on each platform before building, surely that wouldn't make sense as then
distribution kits built on one platform would only work correctly on the
same platform, which isn't the case. Any AutoConf guru pearls of wisdom here
?

David


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.






Archive powered by MHonArc 2.6.24.

Top of Page