![]() ![]() Last time I built it was this past August on macOS Mojave (Xcode 10.3) with Freetds 1.0.48 and 1.1.24. arch x86_64 again is just a holdover from years ago when I had to build both 32 and 64 bit libraries enable-sspi doesn't really matter on macOSĬC=clang direct clang and not the Apple gcc compatibility wrapper seems to work a little bit better for me enable-krb5 we use Kerberos database authentication disable-debug, -server, -pool I don't need these, so I explicitly disable them with-libiconv-prefix=/opt/sw I use the libiconv from the Fink software manager as I've had fewer issues with the more recent version it provides configure -with-iodbc=/usr/local/iodbc -prefix=/usr/local/freetds -with-libiconv-prefix=/opt/sw -disable-debug -disable-server -disable-pool -enable-krb5 -enable-sspi CC=clang CFLAGS="-arch x86_64" LDFLAGS="-arch x86_64" Last time I built it was this past August on macOS Mojave (Xcode 10.3) with iODBC 3.52.13.įreetds then builds for me with out issues. disable-libodbc since for my uses libiodbc had to coexist beside the unixodbc libraryĬFLAGS and -arch x86-64 is just a holdover from years ago where I had to build both 32 and 64 bit librariesĬC="gcc-9" I found years ago that the actual gnu c compiler worked better than Apple gcc compatibility wrapper around clang disable-gui to not bother with the gui and likely the frameworks which just complicates things, ie, I just treat it as a normal unix build with-iodbc-inidir=/Library/ODBC to make it more compatible with the way other apps tend to expect the ODBC configuration files I stick it in a separate directory in /usr/local/ to make it easier for me to maintain, but that is just me. ![]() configure -prefix=/usr/local/iodbc -with-iodbc-inidir=/Library/ODBC -disable-gui -disable-libodbc CFLAGS="-arch x86-64" CC="gcc-9" I have not had any issues building either libiodbc or freetds on Mac OS X. Next message (by thread): Failure to build on OSX.Previous message (by thread): Failure to build on OSX.Failure to build on OSX Merle Reinhart merlereinhart at mac.com
0 Comments
Leave a Reply. |