----- Original Message -----
From: "Sisyphus"
If non-one else beats me to it (and I really don't mind at all if someone
*does* beat me to it :-), I should be able to come up with a solution
tomorrow by comparing the 0.02 and 0.05 build sources and build outputs.
Only trouble with that theory is that 0.02 also no longer builds for me -
so, something that I've installed into my perl builds since I last
successfully built 0.02 (on 23rd May 2012) is breaking PDL::Drawing::Prima.
After spending a good part of today puzzling over this, I finally discovered
that I'd found a solution earlier. (See my 2 posts of March 5 in this
thread.)
Seems it's just a matter of renaming perl/site/lib/auto/Prima/Prima.a to
perl/site/lib/auto/Prima/libPrima.a, and then re-building
PDL::Drawing::Prima from scratch.
That works for me.
I recall recently rebuilding Prima and wondering why the 32-bit builds
created a libPrima.a, but the 64-bit builds created Prima.a.
Having forgottent the importance of the 32-bit import lib being named
"libPrima.a", I let it revert to "Prima.a" .... which doesn't matter at all
until one comes to building PDL::Drawing::Prima.
I must keep a note of why it has to be that way so I don't do the same thing
again.
I suspect it has something to do with there being 2 files named Prima.dll,
but I still don't understand why the 64-bit builds are not similarly
affected. And I don't know precisely what it is that *ought* to be fixed
(Prima ? ExtUtils::Depends ? Perl itself ?)
Cheers,
Rob
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
