[MacPorts] #56200: What happened to SHLIB_LDFLAGS?

MacPorts noreply at macports.org
Sun Apr 1 07:20:00 UTC 2018


#56200: What happened to SHLIB_LDFLAGS?
------------------------+----------------------
 Reporter:  ryandesign  |      Owner:  (none)
     Type:  defect      |     Status:  new
 Priority:  Normal      |  Milestone:
Component:  ports       |    Version:
 Keywords:              |       Port:  MacPorts
------------------------+----------------------
 The [changeset:22966945555c1b562875f92a5dc9b75dc1427d26/macports-base
 ChangeLog entry for MacPorts 1.2.1] says that `-arch` flags should be
 specified to the MacPorts configure script in `CFLAGS` and
 `SHLIB_LDFLAGS`, and that's what the [browser:macports-
 ports/sysutils/MacPorts/Portfile MacPorts Portfile] does, in addition to
 specifying the SDK path there when needed, but ever since
 [changeset:8b2c47f349b18c125098764b68e409929d55af3b/macports-base bundling
 Tcl 8.5], setting `SHLIB_LDFLAGS` at configure time does nothing. Is this
 intentional? If so, we should update the MacPorts port. Is it acceptable
 for the user to set `LDFLAGS` instead of `SHLIB_LDFLAGS`? It seems to
 work.

-- 
Ticket URL: <https://trac.macports.org/ticket/56200>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list