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 wrote:
>
> I believe MM will hav
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 kn
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
wrote:
> Hello Karl,
>
> Judging by the discussion under this bug report (
> https://rt.perl.org/Public/Bug/Display.html
AFAICT, we have never had more than one SciPDL per PDL release
and the two "styles" of SciPDL have never overlapped. Is the
change from the past implementation to the current implementation
information needed to use SciPDL? If not, we could keep it
the same, SciPDL, and also have the benefit of b
Yes, I think I am persuaded. Just giving the history
Karl
> On 6 Jun 2016, at 1:52 AM, Chris Marshall wrote:
>
> AFAICT, we have never had more than one SciPDL per PDL release
> and the two "styles" of SciPDL have never overlapped. Is the
> change from the past implementation to the current i
no I mean it does not set that env var.
Will follow up on David Mertens reply…
> On 5 Jun 2016, at 11:23 PM, Ed 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
