On 01/31/2011 11:21 AM, Ed Hartnett wrote:
Peter O'Gorman writes:
/usr/bin/libtool: unknown option character `f' in: -force_load
Usage: /usr/bin/libtool -static [-] file [...] [-filelist
listfile[,dirname]] [-arch_only arch] [-sacLT]
Usage: /usr/bin/libtool -dynamic [-] file [...] [-fil
Peter O'Gorman writes:
> On 01/07/2011 06:30 AM, Ed Hartnett wrote:
>
>> libtool: link: g95 -dynamiclib -Wl,-undefined -Wl,dynamic_lookup -o
>> .libs/libnetcdff.0.dylib .libs/fort-attio.o .libs/fort-control.o
>> .libs/fort-dim.o .libs/fort-genatt.o .libs/fort-geninq.o
>> .libs/for
On 01/07/2011 06:30 AM, Ed Hartnett wrote:
libtool: link: g95 -dynamiclib -Wl,-undefined -Wl,dynamic_lookup -o
.libs/libnetcdff.0.dylib .libs/fort-attio.o .libs/fort-control.o
.libs/fort-dim.o .libs/fort-genatt.o .libs/fort-geninq.o
.libs/fort-genvar.o .libs/fort-lib.o .libs/fort
On Fri, Jan 7, 2011 at 13:30, Ed Hartnett wrote:
> For some reason, the libtool script that ships with the dist is ignored,
> and the build tries to use /usr/bin/libtool instead, and that's where it
> comes unglued. This may have nothing to do with macos, but may mearly be
> happening on this mach
