[MacPorts] #70626: gh: Upgrading to version 2.55.0 Fails -- Invalid value for flag -extldflags

[MacPorts]

#70626: gh:  Upgrading to version 2.55.0 Fails -- Invalid value for flag
-extldflags
---------------------+--------------------
  Reporter:  RobK88  |      Owner:  (none)
      Type:  defect  |     Status:  new
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:  2.10.1
Resolution:          |   Keywords:
      Port:  gh      |
---------------------+--------------------

Comment (by RobK88):

 I am baffled with this bug.

 Below is the only place in the `golang PortGroup` where the `-extldflags`
 is set:


 {{{
 post-extract {
         build.env-append \
             "CC=[compwrap::wrap_compiler cc]" \
             "CXX=[compwrap::wrap_compiler cxx]" \
             "OBJC=[compwrap::wrap_compiler objc]" \
             "OBJCXX=[compwrap::wrap_compiler objcxx]" \
             "FC=[compwrap::wrap_compiler fc]" \
             "F90=[compwrap::wrap_compiler f90]" \
             "F77=[compwrap::wrap_compiler f77]"
         if { ${os.major} <= [option
 legacysupport.newest_darwin_requires_legacy] } {
             build.env-append \
                 "GO_EXTLINK_ENABLED=1" \
                 "BOOT_GO_LDFLAGS=-extldflags='${configure.ldflags}'" \
                 "CGO_CFLAGS=${configure.cflags} [get_canonical_archflags
 cc]" \
                 "CGO_CXXFLAGS=${configure.cxxflags}
 [get_canonical_archflags cxx]" \
                 "CGO_LDFLAGS=${configure.cflags} ${configure.ldflags}
 [get_canonical_archflags ld]" \
                 "GO_LDFLAGS=-extldflags='${configure.ldflags}
 [get_canonical_archflags ld]'"
         }
 }}}

 It looks okay.  I do not see `golang` setting `-extldflag` to an
 unterminated string...

 Rob

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