It should look something like this:
scubadev[build/ExtUtils-F77-1.17-G9BE4z]>perl Makefile.PL
Checking if your kit is complete...
Looks good
Writing Makefile for ExtUtils::F77
Writing MYMETA.yml and MYMETA.json
scubadev[build/ExtUtils-F77-1.17-G9BE4z]>make test
cp F77.pm blib/lib/ExtUtils/F77.pm
PERL_DL_NONLAZY=1
/home/timj/perl5/perlbrew/perls/perl64-5.16.0/bin/perl
"-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib',
'blib/arch')" t/*.t
t/require.t ..
ExtUtils::F77: Version 1.17
t/require.t .. ok
All tests successful.
Files=1, Tests=2, 1 wallclock secs ( 0.02 usr 0.01 sys + 0.01 cusr
0.01 csys = 0.05 CPU)
Result: PASS
scubadev[build/ExtUtils-F77-1.17-G9BE4z]>perl -Mblib t/require.t
1..2
ExtUtils::F77: Version 1.17
Loaded ExtUtils::F77 version 1.17
Found compiler gfortran
ExtUtils::F77: Using system=Linux compiler=GNU
Runtime: -L/usr/lib/gcc/x86_64-redhat-linux/4.1.2 -L/usr/lib -lgfortran -lm
ExtUtils::F77: Validating -L/usr/lib/gcc/x86_64-redhat-linux/4.1.2
-L/usr/lib -lgfortran -lm [ok]
ExtUtils::F77: Compiler: gfortran
ExtUtils::F77: Cflags:
ok 1
ok 2
f77 is what it chooses if it doesn't understand your system.
On Tue, Sep 18, 2012 at 10:53 AM, Coskun Oba <[log in to unmask]> wrote:
> gfortran is installed and in path. Variables FC and F77 are also set to
> gfortran. Nothing is changed compared to my earlier version. I recently got
> a fresh copy from github and built Starlink without any problems.
>
> Coskun Oba
>
>
>
> -----Original Message-----
> From: Starlink development [mailto:[log in to unmask]] On Behalf Of Tim
> Jenness
> Sent: September-17-12 4:10 PM
> To: [log in to unmask]
> Subject: Re: Starlink Installation
>
> Install a fortran compiler. Is gfortran in your path? It's falling back to
> f77 as a last desperate attempt to find a fortran compiler.
>
> On Mon, Sep 17, 2012 at 3:06 PM, Oba, Josh <[log in to unmask]> wrote:
>> 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
|