develooper Front page | perl.perl5.porters | Postings from October 2015

[perl #126360] MACOSX_DEPLOYMENT_TARGET

Thread Previous | Thread Next
From:
Jarkko Hietaniemi via RT
Date:
October 14, 2015 22:39
Subject:
[perl #126360] MACOSX_DEPLOYMENT_TARGET
Message ID:
rt-4.0.18-5463-1444862339-249.126360-15-0@perl.org
On Wed Oct 14 15:24:24 2015, jhi wrote:
> > Jarkko:
> >
> > How would this patch:
> >
> > https://rt.perl.org/Ticket/Attachment/1332434/711615/0002-very-first-
> > step-to-tidy-up-mess-around-sdk-to-use.patch
> >
> > ... which is from https://rt.perl.org/Ticket/Display.html?id=123831
> 
> Missed that one...
> 
> > and which Tony Cook and I were discussing last night in #p5p affect
> > this issue?
> 
> The above-suggested patch is implicit, I suggested explicit (the
> configurer deciding).  But I don't mind either way.  Binding together
> the installed SDK and the deployment target is definitely a
> possibility.  At least it would be better than the current "link like
> it's 2003" state of things.
> 
> With that patch one could also build a backward compatible version, by
> hinting -Dld="env MACOSX_DEPLOYMENT_TARGET=whatever $cc'", though
> that's quite ugly...
> 
> > Thank you very much.

I think as reasonable first step we could just apply Jens' patch.

Second minor tweak would be to have the minimum to be 10.4, instead of 10.3 (as suggested by the macports guys).

Then we can look into additional cc/ld options like what Craig described.

And maybe also add the env $MACOSX_DEPLOYMENT_TARGET trick to make it easier to hint the minimum, if one wants.  Though as Craig noted, compiling for ancient releases might not actually even work that well.

The thing is, we need older OS X boxes to be able to test this.  Anyone still run PPC?







---
via perlbug:  queue: perl5 status: open
https://rt.perl.org/Ticket/Display.html?id=126360

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About