This seems better. But it failed for me. The problem seems to be with ExtUtils::F77. How can I resolve this? Details are below (from the log file):
Checking dependencies from MYMETA.json ...
Checking if you have ExtUtils::MakeMaker 0 ... Yes (6.63_02)
Building and testing ExtUtils-F77-1.17
cp F77.pm blib/lib/ExtUtils/F77.pm
Manifying blib/man3/ExtUtils::F77.3
PERL_DL_NONLAZY=1 /usr/local/star/Perl/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
ExtUtils::F77: Version 1.17
Use of uninitialized value $ExtUtils::F77::Runtime in concatenation (.) or string at t/require.t line 17.
Can't exec "f77": No such file or directory at t/require.t line 28.
t/require.t ..
Failed 1/2 subtests
Test Summary Report
-------------------
t/require.t (Wstat: 0 Tests: 1 Failed: 0)
Parse errors: Bad plan. You planned 2 tests but ran 1.
Files=1, Tests=1, 0 wallclock secs ( 0.02 usr + 0.00 sys = 0.02 CPU)
Result: FAIL
Failed 1/1 test programs. 0/1 subtests failed.
make: *** [test_dynamic] Error 255
-> FAIL Installing ExtUtils::F77 failed. See /home/oba/.cpanm/build.log for details.
________________________________________
From: Starlink development [[log in to unmask]] on behalf of Tim Jenness [[log in to unmask]]
Sent: Monday, September 17, 2012 3:28 PM
To: [log in to unmask]
Subject: Re: Starlink Installation
On Mon, Sep 17, 2012 at 9:56 AM, Coskun Oba <[log in to unmask]> wrote:
> I used to rsync starjava and site_perl from JAC. Is this still possible or
> do I need to go back to building the individual components?
>
Should be fine. /stardev is kept up to date.
Note that we have a much more robust system for installing all the
perl modules now. After a build you can just
cd thirdparty/perlsys/perlmods
sh build-modules.sh
and all the perl modules will be updated.
--
Tim Jenness
|