[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #YVQ-214480]: Patch for Intel fortran on Mac OS


> Well okay, that's better.  Now the argument "-Wl,-force_load" was in
> fact the central target of my original investigation.  If you are
> still having trouble with that, you could let me see your setup, and
> configure and make outputs, *including* capture of full console
> output.  I might be able to spot something for you.

OK, thanks, I'll send you something as soon as I have tried a few more
tests.  But I do have a few questions below about your patch.

 - Which libtool are you using, the Apple one in /usr/bin/libtool, or
   something you've installed from Macports or another package
   management system, e.g. libtool version 2.4 in /usr/local/bin?  The
   Apple libtool doesn't understand the
   syntax, which is why it issues the error message
    /usr/bin/libtool: unknown option character `f' in: -force_load

  - Have you tried the libtool environment variable
    lt_cv_ld_force_load=no when running the configure script?  We've
    had some success with that for building on our local Mac OS X
    platform, but I don't know exactly when it works or doesn't.
    Here's a relevant comment about it from one of the libtool
    and this contribution to macports edited the configure script to
    replace occurrentces of "lt_cv_ld_force_load=yes" with
    "lt_cv_ld_force_load=no" for g95 variants:

  - Have you corresponded with the libtool maintainers on your
    proposed fix, for example on the libtool-gnu mailing list?  Are
    they aware of the problem with Mac OS X?

For now, I think I'll just try to get a 4.1.3 build working on my Mac
laptop and worry about the fixes to the libtool.m4 or configure in
netcdf-fortran-4.2.1 after that ...


Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu

Ticket Details
Ticket ID: YVQ-214480
Department: Support netCDF
Priority: Normal
Status: Closed

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.