Thanks David. I took a look and it seems that adding LD=‘cc’ to the perl Makefile.PL line is enough to make this go away. This is fine for SciPDL - since it is a perl OS X config issue I won’t propose a PDL patch.
Karl > On 6 Jun 2016, at 12:17 AM, David Mertens <dcmertens.p...@gmail.com> wrote: > > Here is more relevant discussion: > http://stackoverflow.com/questions/32280732/whats-the-best-way-to-set-macosx-deployment-target > > On Sun, Jun 5, 2016 at 10:16 AM, David Mertens <dcmertens.p...@gmail.com> > wrote: > Hello Karl, > > Judging by the discussion under this bug report > (https://rt.perl.org/Public/Bug/Display.html?id=117433), specifically Jim > Keenan's build summary, it looks like MACOSX_DEPLOYMENT_TARGET is being set > in the linker command explicitly: ld='env MACOSX_DEPLOYMENT_TARGET=10.3 cc' > > I don't know exactly how to resolve the specific issue for GSL linking > (though, as you noted, it's not really a problem, just a warning, and > everything seems to work), but at this point it might require leaning on p5p > to move Perl's Mac build away from this. > > David > > On Sun, Jun 5, 2016 at 9:23 AM, Ed <ej...@hotmail.com> wrote: > You're saying that the Perl you're running has an empty Config.pm? > > -----Original Message----- > From: Karl Glazebrook > Sent: Sunday, June 05, 2016 5:45 AM > To: Ed > Cc: pdl-devel > Subject: Re: [Pdl-devel] OS X issue > > nope it is a blank! > > > On 4 Jun 2016, at 11:54 PM, Ed <ej...@hotmail.com> wrote: > > > > I believe MM will have got that from the configuration of Perl itself. You > > could confirm/deny that by doing "perldoc -m Config" and searching for it > > there? > > > > Best regards, > > Ed > > > > -----Original Message----- From: Karl Glazebrook > > Sent: Saturday, June 04, 2016 5:01 AM > > To: Karl Glazebrook > > Cc: pdl-devel > > Subject: Re: [Pdl-devel] OS X issue > > > > correction: it was there in 2.015 etc we just ignored it. Tests all pass. > > > > env MACOSX_DEPLOYMENT_TARGET=10.3 seems to come from Makemaker, does > > anyone know the story on this? > > > > Karl > > > > > > > >> On 4 Jun 2016, at 12:54 PM, Karl Glazebrook <kglazebr...@swin.edu.au> > >> wrote: > >> > >> Seems to be an issue in the latest build > >> > >> env MACOSX_DEPLOYMENT_TARGET=10.3 cc -bundle -undefined > >> dynamic_lookup -L/usr/local/lib -L/opt/local/lib -fstack-protector-strong > >> EXPINT.o -o ../../../../blib/arch/auto/PDL/GSLSF/EXPINT/EXPINT.bundle \ > >> -L/Applications/PDL/lib -lgsl -lgslcblas \ > >> > >> ld: warning: object file (EXPINT.o) was built for newer OSX version > >> (10.11) than being linked (10.4) > >> ld: warning: object file (/Applications/PDL/lib/libgsl.a(shint.o)) was > >> built for newer OSX version (10.10) than being linked (10.4) > >> ld: warning: object file (/Applications/PDL/lib/libgsl.a(sinint.o)) was > >> built for newer OSX version (10.10) than being linked (10.4) > >> ld: warning: object file (/Applications/PDL/lib/libgsl.a(atanint.o)) was > >> built for newer OSX version (10.10) than being linked (10.4) > >> ld: warning: object file (/Applications/PDL/lib/libgsl.a(expint3.o)) was > >> built for newer OSX version (10.10) than being linked (10.4) > >> ld: warning: object file (/Applications/PDL/lib/libgsl.a(expint.o)) was > >> built for newer OSX version (10.10) than being linked (10.4) > >> ld: warning: object file (/Applications/PDL/lib/libgsl.a(strerror.o)) was > >> built for newer OSX version (10.10) than being linked (10.4) > >> > >> > >> > >> where does the setting of MACOSX_DEPLOYMENT_TARGET come from? > >> > >> > >> Karl > >> > >> > >> ------------------------------------------------------------------------------ > >> What NetFlow Analyzer can do for you? Monitors network bandwidth and > >> traffic > >> patterns at an interface-level. Reveals which users, apps, and protocols > >> are > >> consuming the most bandwidth. Provides multi-vendor support for NetFlow, > >> J-Flow, sFlow and other flows. Make informed decisions using capacity > >> planning reports. > >> https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > >> _______________________________________________ > >> pdl-devel mailing list > >> pdl-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/pdl-devel > > > > > > ------------------------------------------------------------------------------ > > What NetFlow Analyzer can do for you? Monitors network bandwidth and > > traffic > > patterns at an interface-level. Reveals which users, apps, and protocols > > are > > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > > J-Flow, sFlow and other flows. Make informed decisions using capacity > > planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > > _______________________________________________ > > pdl-devel mailing list > > pdl-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/pdl-devel > > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > _______________________________________________ > pdl-devel mailing list > pdl-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/pdl-devel > > > > -- > "Debugging is twice as hard as writing the code in the first place. > Therefore, if you write the code as cleverly as possible, you are, > by definition, not smart enough to debug it." -- Brian Kernighan > > > > -- > "Debugging is twice as hard as writing the code in the first place. > Therefore, if you write the code as cleverly as possible, you are, > by definition, not smart enough to debug it." -- Brian Kernighan ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ pdl-devel mailing list pdl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pdl-devel
