FreeTDS Development Group

["Xander Maas (GMAIL)" <xjmaas AT gmail.com>]

Daniel,

When I perform command against the lib I am lining to, I see the fopen, not 
fopen$UNIX2003. For your interest, also the libs I built before for regilar 
OS X apps, also list fopen, and not fopen$UNIX2003.

Somehow my project is trying to call fopen$UNIX2003, but it isn't used in my 
libraries and/or code.

Regards,

Xander


On 15 feb 2011, at 16:28, Daniel Fazekas wrote:

> On Feb 15, 2011, at 16:04, Xander Maas (GMAIL) wrote:
> 
>> I do have another FreeTDS install on my Mac, in /usr/local/freetds. But 
>> none of these libraries are used, as these are not in my default search 
>> path for libraries. Second, these libraries are i386 and x86_64 built.
> 
> The iPhone Simulator is also i386 and we have already established you are 
> linking to an i386 Mac build of the libraries somehow.
> That's the only situation where fopen$UNIX2003 exists, a 10.6+, i386 Mac OS 
> X build.
> It stays fopen for 10.5 or earlier Mac builds, for any x86_64 build, for 
> any iOS build (arm), for any iOS Simulator (i386) build…
> 
> /usr/local/freetds should be safe though as that isn't in the standard 
> search path — yet a rogue i386 Mac build of freetds must be somewhere on 
> your system and getting linked to.
> 
> Check in your iPhone Simulator freetds build directory:
> 
> nm -g src/tds/locale.o | grep fopen                                  
>                 U _fopen
> 
> If this is correct (as opposed to U _fopen$UNIX2003) then your build is 
> correct and you are simply not linking to it.
> If it's wrong, then you are building for Mac OS X 10.6 i386 rather than the 
> iOS Simulator.
> 
>> I am referencing the libraries directly from the location I build them.
>> I am not seeing any FreeDTS libs linked when performing the otool -L on my 
>> built app.
> 
> So you are linking statically.
> 
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds