Front page | perl.perl5.porters |
Postings from October 2015
On Sat, Oct 17, 2015 at 8:42 PM, Ricardo Signes <perl.p5p@rjbs.manxome.org> wrote: > * Jarkko Hietaniemi via RT <perlbug-followup@perl.org> [2015-10-16T16:48:43] >> I now went ahead and pushed the change as 53d1d41c. > > Thanks for forging ahead on this. I was a bit worried because I didn't see the > problems in https://rt.perl.org/Public/Bug/Display.html?id=123985#txn-1363511 > discussed, and it seemed like they'd be sure to come up... but building blead > does not show the changes in behavior warned about from what I could see. As far as I can tell, the things about POSIX conformance and so on that David G. mentioned had to do with specifying a target for the compiler, not the linker. Until now we've never specified an explicit target for the compiler, which means it chose its own defaults, which would typically be whatever version you are running on (or whatever latest SDK you have installed). Then we turned around and told the linker to target 10.3 no matter what. This was probably the best thing to do for some range of 10.early, but has been somewhere between a little and a lot wrong for several more recent versions. Latest greatest (XCode 7.0.1) actually warns about the discrepancy between compiler target and linker target and also silently promotes a link target of 10.3 to 10.4 because that is the minimum even possible for any Intel-only version of OS X. So the new implementation applies a consistent target version to both compiler and linker flags. There should no longer be a discrepancy between compiler and linker, nor between the perl binary and extensions built against it when those extensions are built on a later OS and/or with later build tools than was the perl binary.Thread Previous | Thread Next