[MacPorts] #60798: legacy-support needs to use -Wl, when adding library name to LDFLAGS

[MacPorts]

#60798: legacy-support needs to use -Wl, when adding library name to LDFLAGS
------------------------------------------+----------------------
  Reporter:  ryandesign                   |      Owner:  (none)
      Type:  defect                       |     Status:  new
  Priority:  Normal                       |  Milestone:
 Component:  ports                        |    Version:  2.6.2
Resolution:                               |   Keywords:  haspatch
      Port:  gwenhywfar5, legacy-support  |
------------------------------------------+----------------------

Comment (by kencu):

 In [changeset:"7bded6b45234445ad5cc49a5f56b404ef3d8a38d/macports-ports"
 7bded6b45234445ad5cc49a5f56b404ef3d8a38d/macports-ports] (master):
 {{{
 #!ConfigurableCommitTicketReference repository="macports-ports"
 revision="7bded6b45234445ad5cc49a5f56b404ef3d8a38d"
 legacysupport 1.1 PG: use tranditional libname

 it turns out that libtool does not pass along
 dylibs for linking when the name is a full-specified
 pathname.

 However, libtool does pass along static libs for linking
 when the name is a fully-specified pathname.

 the changes the dylib name back to the traditional one
 that works, and has been used for some years in legacysupport 1.0.

 Hopefully this is the simplest, least-invasive, and most tested
 method of restoring the proper link behaviour when using
 legacysupport and libtool.

 see: https://trac.macports.org/ticket/60798
 }}}

-- 
Ticket URL: <https://trac.macports.org/ticket/60798#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS