On 3/17/15 12:51 PM, Tom Lane wrote:
> Peter Eisentraut writes:
>> It looks like ar isn't even the preferred method to build static
>> libraries on OS X anymore. Instead, one should use libtool (not GNU
>> libtool), which has a -no_warning_for_no_symbols option.
>
> I looked into this a little b
Peter Eisentraut writes:
> It looks like ar isn't even the preferred method to build static
> libraries on OS X anymore. Instead, one should use libtool (not GNU
> libtool), which has a -no_warning_for_no_symbols option.
I looked into this a little bit, but that option seems to be a somewhat
rec
On 3/14/15 12:58 PM, Tom Lane wrote:
> I'm getting rather tired of reading these warning messages in OS X builds:
>
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib:
> file: libpgport.a(dirmod.o) has no symbols
> /Applications/Xcode.app/Contents/Deve
On Sun, Mar 15, 2015 at 1:58 AM, Tom Lane wrote:
> I'm getting rather tired of reading these warning messages in OS X builds:
>
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib:
> file: libpgport.a(dirmod.o) has no symbols
> /Applications/Xcode.app/C
I'm getting rather tired of reading these warning messages in OS X builds:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib:
file: libpgport.a(dirmod.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/b
