FreeTDS Development Group

[Jonathan Monroe <monroej_freetds AT actualtechnologies.com>]

On Feb 14, 2005, at 11:00 AM, Frediano ZIGLIO wrote:

> I still don't understand the relationship between darwin and Mac OS X.
> Darwin it's the core of Mac OS X. However which darwin version use, for
> instance, Mac OS X 10.1 ??

As Mark mentioned, darwin distributions are kept in sync with Mac OS X 
releases:

darwin 5 -> OS X 10.1
darwin 6 -> OS X 10.2
darwin 7 -> OS X 10.3
darwin 7.8 -> OS X 10.3.8

I think for the most part you just have to keep track of the darwin 
releases, since "uname -spr" under OS X reports the darwin version 
number, not the OS X version number.

> If you want to try to produce a .dylib with current snapshot using two
> level namespace simply do this:
> - execute configure
> - in src/odbc/Makefile
>  - find "-module"
>  - remove "-module"
>  - add "-Wl,-twolevel_namespace"
> - make as usual
> The library compiled load successfully? Are you able to do a 
> connection?

Using 0.63 RC 10, I executed "configure" with default options and 
followed your instructions.  The "make" stops with the error:

ld: can't specify both -twolevel_namespace and -flatname_space

when it tries to link.  There is no reference to -flatname_space in the 
Makefile, so I assume it is specified in the libtool stuff (it is 
present in the configure script).  I manually executed the link step 
from the Makefile with the -flatname_space option removed.  I then get 
the following error:

ld: -undefined error or -undefined define_a_way must be used when 
-twolevel_namespace is in effect

The link step includes the "-undefined suppress" option, which also 
does not appear in the Makefile.  I manually execute the link step 
again with the -undefined option removed, and it succeeds.

I can then execute all the ODBC unit tests with both the dylib and 
bundle (.so) versions of the libraries.  They give identical results.  
Most of the unit tests pass - almost all the ones that fail are because 
of iODBC driver manager cursor state errors.  I assume this is an 
artifact of differences between unixODBC and iODBC.

Jonathan