[MacPorts] #50894: perl: hardcodes compiler and compiler options (packages from CPAN may not compile under a different Xcode version) (was: Perl packages needing compilation do not install)

[MacPorts]

#50894: perl: hardcodes compiler and compiler options (packages from CPAN may not
compile under a different Xcode version)
---------------------------------+---------------------
  Reporter:  matthew-macports@…  |      Owner:  mojca@…
      Type:  defect              |     Status:  new
  Priority:  Normal              |  Milestone:
 Component:  ports               |    Version:
Resolution:                      |   Keywords:
      Port:  perl5.22            |
---------------------------------+---------------------
Changes (by mojca@…):

 * version:  2.3.4 =>


Comment:

 See also
 * [https://lists.macosforge.org/pipermail/macports-
 dev/2012-October/020636.html Compiler name baked into our packages]
 (Mailing list, October 2012)
 * [https://lists.macosforge.org/pipermail/macports-
 dev/2012-October/020736.html apr binary package misconfigured?] (Mailing
 list, October 2012)
 * [[TicketQuery(id=36474)]]

 Here's what Joshua replied on the [https://lists.macosforge.org/pipermail
 /macports-dev/2016-March/032648.html mailing list]:
 > So it's also an upstream bug. You could patch perl to remove use of
 `-fstack-protector-strong` or replace it with `-fstack-protector`; that
 won't prevent anything from running since it's a hardening measure.
 Whether it "breaks" anything is a harder question. (Used on a bug-free
 program, it would do nothing but make it slightly slower.) Whether perl
 should even be choosing its own `CFLAGS` like this is left as an exercise
 for the reader. ;)

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