Re: Darwin bootstrap failure

[Jason Bacon <jtocino%gmx.com@localhost>]

On 5/26/23 09:38, Jonathan Perkin wrote:
> * On 2023-05-26 at 15:12 BST, Jason Bacon wrote:
>
> > Looks like we need to add the following to mk/platform/Darwin.mk for
> > macOS 13.4:
> >
> > OSX_SDK_MAP.13.4=       13.3
>
> cvs up, this was added on Monday.

I see.  The tarballs appear to be lagging a little...

> > Does anyone recall why we have these hard-coded mappings in Darwin.mk,
> > as opposed to just using the "MacOSX.sdk" link, or using the latest?
>
> You can use the default MacOSX.sdk link by setting 
> OSX_TOLERATE_SDK_SKEW=yes, as long as you are ok with the SDK changing 
> from beneath you on upgrades and potentially running into 
> incompatibilities.

I'm not seeing a difference here.  Since Darwin,mk appears to determine 
the SDK path on the fly, when I update macOS from 13.2 to 13.4, then the 
hard-coded mapping would change from 13.1 to 13.3 along with the 
symlink, correct?

OSX_SDK_MAP.13.2=       13.1
OSX_SDK_MAP.13.4=       13.3

> Personally I use MACOSX_DEPLOYMENT_TARGET to set the correct SDK at 
> bootstrap time, and then I don't have to think about it again.

I saw that option, thanks.  I may code this into auto-pkgsrc-setup.