[MacPorts] #59135: legacy-support: functions properly only if os.version = deployment target

[MacPorts]

#59135: legacy-support: functions properly only if os.version = deployment target
---------------------------------------------------+----------------------
  Reporter:  kencu                                 |      Owner:  kencu
      Type:  defect                                |     Status:  assigned
  Priority:  Normal                                |  Milestone:
 Component:  ports                                 |    Version:
Resolution:                                        |   Keywords:
      Port:  legacy-support, legacy-support-devel  |
---------------------------------------------------+----------------------
Description changed by kencu:

Old description:

> while debugging some enexpected behavior recently, I realized the build
> system was setting the mmacosx-version-min to a value of 10.7 on a host
> os of 10.11. What this did was enable a bunch of replacement definitions
> in the legacy support headers that collided with definitions in the SDK.
>
> This can be fixed by making the legacy support definitions exactly match
> the newer SDK's definitions (eg getattrlistat)' or by removing the
> deployment target change...
>
> But it brought forth the idea that the exact way the legacysupport
> library is built depends on both the host os version but also the setting
> of the deployment target.
>
> It may or may not be possible to build legacy support for an older system
> - that idea would have to be explored and tested -- but for now, at
> least, making sure the host os version matches to deployment target (and
> the sdk version?) is the only reliable way of using the legacy support
> library an PG...

New description:

 while debugging some unexpected behavior recently, I realized the build
 system was setting the mmacosx-version-min to a value of 10.7 on a host os
 of 10.11. What this did was enable a bunch of replacement definitions in
 the legacy support headers that collided with definitions in the SDK.

 This can be fixed by making the legacy support definitions exactly match
 the newer SDK's definitions (eg getattrlistat)' or by removing the
 deployment target change...

 But it brought forth the idea that the exact way the legacysupport library
 is built depends on both the host os version but also the setting of the
 deployment target.

 It may or may not be possible to build legacy support for an older system
 - that idea would have to be explored and tested -- but for now, at least,
 making sure the host os version matches to deployment target (and the sdk
 version?) is the only reliable way of using the legacy support library an
 PG...

--

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