[MacPorts] #69867: legacy-support headers should work with later SDK versions

[MacPorts]

#69867: legacy-support headers should work with later SDK versions
-----------------------------+-----------------------
  Reporter:  fhgwright       |      Owner:  fhgwright
      Type:  defect          |     Status:  assigned
  Priority:  Low             |  Milestone:
 Component:  ports           |    Version:  2.9.3
Resolution:                  |   Keywords:
      Port:  legacy-support  |
-----------------------------+-----------------------

Comment (by fhgwright):

 In [changeset:"e0a0fafdf81f12959a29cdd834a449c1827f96c9/macports-legacy-
 support" e0a0fafdf81f12959a29cdd834a449c1827f96c9/macports-legacy-support]
 (master):
 {{{
 #!ConfigurableCommitTicketReference repository="macports-legacy-support"
 revision="e0a0fafdf81f12959a29cdd834a449c1827f96c9"
 Add secure/_common.h to avoid security wrappers on 10.4.

 Security wrappers are unsupported on 10.4.  They're never enabled when
 using the 10.4 SDK, but builds with later SDKs and the enable on
 (default in 10.6+, allowable in 10.5) result in build failures.  This
 is not limited to legacy-support's stpncpy(), but affects native
 functions (e.g. strncpy()) as well.  We avoid this by #undefing
 _FORTIFY_SOURCE in any 10.4 build.

 Re: https://trac.macports.org/ticket/69867

 TESTED:
 Tested on 10.4-10.5 ppc, 10.5-10.6 ppc (i386 Rosetta), 10.4-10.6 i386,
 10.5-12.x x86_64, and 11.x-14.x arm64.  Tested against all 10.4-14.x
 SDKs, using the headerinfo manual test (from a subsequent commit).
 All target/SDK combinations where the SDK supports the CPU
 architecture work correctly, including all SDKs on Intel
 architectures.  Only 10.4-10.6 SDKs support ppc, and only 11.x+ SDKs
 support arm64.
 }}}

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