FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: stephen.hsu AT donovandata.com [mailto:stephen.hsu AT donovandata.com]
> Sent: September 16, 2002 3:32 PM
> 
> Hey,

Hi!  Thanks for the PR.  

> I'm trying to make FreeTds on OS X.  I'm getting the following 
> 
> I../../include    -g -O2 -DTDS50 -c asprintf.c
> cc -DHAVE_CONFIG_H -I. -I. -I../../include -I../../include -g 
> -O2 -DTDS50
> -c asprintf.c -o asprintf.o
> asprintf.c: In function `vasprintf':
> asprintf.c:67: `_SC_PAGESIZE' undeclared (first use in this function)

Yes.  OS X perhaps has another variation on the theme for SC_PAGESIZE?
What do you get for the following:

$ grep -r SC_PAGESIZE /usr/include
/usr/include/sys/unistd.h:#define       _SC_PAGESIZE            28
/usr/include/sys/unistd.h:#define       _SC_PAGE_SIZE           _SC_PAGESIZE

More interesting, what says "man asprintf" and "man vasprintf"?  Are they
not implemented by Darwin?  The FreeTDS asprintf.c module should not come
into play unless the OS does not provide these functions.  

I would be happy to fix FreeTDS to accomodate OS X, if we can find the
equivalent of SC_PAGESIZE or correctly assess the presence of vasprintf(3).


In the meanwhile, you can patch src/tds/asprintf.c as follows:

On line 41, you'll see:

        #ifdef _REENTRANT

change that to:

        #if 1  /* always very true */

and rebuild.  This change will force use of a slower (and threadsafe)
version of asprintf(), without invoking other threadsafe functions.  

But I would like to fix your build properly.  

HTH

--jkl


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.