Ryan Schmidt <[email protected]> writes: > On Sep 12, 2017, at 19:36, Glenn Ramsey wrote: >> >> On OSX 10.12.6 with the latest Xcode I have set macosx_deployment_target to >> 10.8 >> in macports.conf and when installing mercurial I get this error: >> >> error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.8" but "10.12" during >> configure >> >> Is this a bug or can I only install mercurial if macosx_deployment_target >> matches the SDK version? If it is a bug, what is the workaround? > > I would guess there are a fair number of ports that fail to build when > macosx_deployment_target is changed, or that build successfully but ignore > the requested macosx_deployment_target, because this is an esoteric feature > that few people test. Looks like mercurial is one of those ports. > > Sure, it can be considered a bug in that port; you could file a bug report in > our issue tracker. Each port's build system is different so I can't give you > a one-size-fits-all solution. In some cases, the reason may be that the > port's build system specifies its own value for that environment variable (or > the equivalent compiler flag). If so, the solution might be to remove that > code from the build system.
I can't see anything obvious in the portfile. Maybe something in the python port group? Or perhaps the canonical_archflags?
signature.asc
Description: PGP signature
