Re: Need help with build on Windows

Daniel Fazekas <[email protected]>
Newsgroups gmane.comp.db.tds.freetds
Message-ID <[email protected]>
This looks like an issue of targeting mismatched OS releases by the different projects.
Merely issuing "./configure" will by default target running on the current OS version or later, whereas the other project may be configured to target supporting an earlier release.

The strlcpy → __strlcpy_chk switcheroo took place between OS X 10.8 and OS X 10.9.
So the other project could be set to target OS X 10.9 or newer, or FreeTDS rebuilt to target a matching older OS release.

For example,
CFLAGS="-mmacosx-version-min=10.8" ./configure
make

alternatively:

export MACOSX_DEPLOYMENT_TARGET=10.8
./configure
make

> On Apr 18, 2016, at 20:02, Frediano Ziglio <[email protected]> wrote:
> 
> Weird. Mac OS X defines strlcpy using __strlcpy_chk which should be a
> system function so should be contained in the standard .dylibs. Looks
> like linker is not picking up standard libraries.
> 
> Frediano
> 
> 2016-04-18 16:42 GMT+01:00 Velichko Yuriy <[email protected]>:
>> One moe issue.
>> Now for build on mac.
>> 
>> I build FreeTds for MacOS with:
>> 
>> ./configure
>> make
>> make install
>> 
>> Than take lib to my project and get link error
>> 
>> Undefined symbols for architecture x86_64:
>> 
>>  "___strlcpy_chk", referenced from:
>>      _tdsdbopen in libsybdb_64.a(dblib.o)
>>      _db_env_chg in libsybdb_64.a(dblib.o)
>>      _dbcolinfo in libsybdb_64.a(dblib.o)
>>      _dbtablecolinfo in libsybdb_64.a(dblib.o)
>>      _tds_alloc_dynamic in libsybdb_64.a(mem.o)
>>      _tds7_get_instance_port in libsybdb_64.a(net.o)
>>      _tds_get_locale in libsybdb_64.a(locale.o)
>>      ...
>> 
>> Any ideas? Because I can't find this method in sources.

_______________________________________________
FreeTDS mailing list
[email protected]
http://lists.ibiblio.org/mailman/listinfo/freetds
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.