FreeTDS Development Group

["Castellano, Nicholas" <Nicholas_Castellano AT acml.com>]

No, I don't think your position is unreasonably conservative.  Hopefully one
of our Mac OS X friends will verify that a current libtool actually solves
the problem, and then we can just document this as you suggest.

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 16, 2002 10:55 AM
To: TDS Development Group
Subject: [freetds] Re: Shared libs on Mac OS X Server 10.2


> From: Castellano, Nicholas [mailto:Nicholas_Castellano AT acml.com]
> Sent: October 16, 2002 9:30 AM
> 
> I think we might need to go to the bleeding edge to support
> Mac OS X.  I
> took a look at the bug report filed yesterday by John Brewer. 
>  A little bit
> of poking around on the libtool pages reveals that there have 
> been some
> important fixes for Darwin shared library support and 
> convenience library
> support, committed in just the past few days.  

Gadzooks.  

I don't know I want to chase that dragon tail; I don't like the idea of
hoping a 3-day-old libtool is completely regression compatible with the
stable release.  I definitely don't want to subscribe to the libtool mailing
list, which is what I would normally do for anything I'm using that's not a
stable release.  

It's important to me that the nightly snapshot be available, and reliable
execution is more likely if the build environment isn't changing every few
days.  

I'm tempted to tell our Apple friends that for the time being, you have to
use anoncvs and have your own autotools installed, "including yesterday's
libtool".  As a matter of fact, we include autogen.sh in the distribution
tarball, so you don't really need to cvs access to regen the configure
script.  

But you tell me.  Is that unreasonably conservative?  What have other
projects done about libtool and OS X?  


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.