Hi all: I'm sorry I have not been able to look at PDL more closely leading up to the release--I've been swamped!

When I built PDL recently on my Linux FC3 i386 machines, I did not see any problems.

I did see some troubles on my FC3 x86_64 machines.

The check to add -fPIC involved $ENV{hosttype}:

$ENV{HOSTTYPE}=~m/x86_64/

Under some shells, under certain conditions, $ENV{hosttype} can be set wrongly. I would recommend checking $Config{archname} instead:

$Config{archname}=~m/x86_64/

This should be changed in:

PDL/Makefile.PL
and
PDL/Lib/Slatec/Makefile.PL

If no one objects, I'll check this change into CVS.

Thanks for all the good work!

Regards,

  Doug

[EMAIL PROTECTED]
Software Engineer III
UCAR - COSMIC, Tel. (303) 497-2611

On Thu, 27 Jul 2006, Chris Marshall wrote:

----- Original Message -----
From: "Christian Soeller" <[EMAIL PROTECTED]>
Sent: Friday, July 28, 2006 8:32 AM
Subject: Re: [Perldl] next version

I suggest pushing a release out now to be followed
by a quick minor release if/when the remaining niggles
are fixed.

We have been talking about release being imminent
for some time now - there is a danger we will become
the debian of perl modules ;)

What do you think?

Yes!

I just checked INSTALL and README notes for cygwin
into CVS and am ready for a general release with this
stuff.

I suggest we freeze code changes immediately.

Everyone runs the build/install tests on their setups
looking for any "oops" problems (i.e. show stoppers)
this weekend.

We update the Known_Problems files and release
by next Tuesday (01-Aug-2006).  BTW, how hard
is it to actually generate a new release?  Is it an
automated process or is there hand cranking involved?

--Chris

_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl

Reply via email to