F
Fred Ma
Guest
Hi,
I'm building SystemPerl (trying to) and running into
problems. Technically, the question has to do with Make,
but I have a feeling it will be most answerable by someone
who has successfully built SystemPerl-1.148 as
nonadministrator (meaning that the installation takes place
in a directory that part of my user account, not in
directories that can only be modified by root e.g.
/usr/local/...).
Since I'm not root, I started the installation with "perl
Makefile.PL PREFIX=/home/fma/INSTROOT", where INSTROOT is my
version of /usr/local, in my file space. This has worked
for many utilities, including Wilson Snyder's
Verilog-Perl-2.231 (same author as SystemPerl, and similar
kind of install procedure). The "make" step went ahead
uneventfully, but the "make test" fails many tests e.g.:
t/05_template......Can't locate Verilog/Netlist/Subclass.pm
in @INC (@INC contains: ../Verilog/blib/arch
../Verilog/blib/lib .. blib/arch blib/lib .
/tmp/fma/SystemPerl-1.148/blib/lib
/tmp/fma/SystemPerl-1.148/blib/arch
/usr/local/lib/perl5/5.8.0/sun4-solaris
/usr/local/lib/perl5/5.8.0
/usr/local/lib/perl5/site_perl/5.8.0/sun4-solaris
/usr/local/lib/perl5/site_perl/5.8.0
/usr/local/lib/perl5/site_perl/sun4-solaris
/usr/local/lib/perl5/site_perl) at
blib/lib/SystemC/Template.pm line 23.
The other failures also can't find *.pm files. These files
do exist! They are under the file tree ~fma/INSTROOT, but
"make test" just isn't looking there. I looked at the
Makefile to see why. Makefiles are not my strong point, and
I'm picking it up from web tutorials, but it can get
extremely complicated. From the above message, it seems INC
isn't being set to include ~/INSTROOT. However, the
Makefile never even sets INC, it just uses it. Furthermore,
it sets $(INC), not @INC. According to the gnu make manual,
"@" merely forces Make execute commands silently. There are
also a few automatic variables prefixed with "@", but
nothing like "INC".
This failed tests *might* be related to warnings during the
initial step "perl Makefile.PL":
Warning: prerequisite Verilog::Getopt 2.211 not found.
Warning: prerequisite Verilog::Netlist 2.21 not found.
But I doubt it, considering that the test failure is due to
not finding a file because ~/INSTROOT is not being looked
in. Just in case, I emailed Wilson Snyder about these
warnings -- in particular, why I would be getting them if I
already installed Verilog-Perl (CPAN shows them to be part
of Verilog-Perl). I am not 100% confident about the
Verilog-Perl installation, since "make test" on that gives
a failed test:
t/10_keywords.....ok
t/12_splitbus.....ok
t/20_getopt.......ok
t/30_preproc......ok
t/40_netlist......ok
t/42_dumpcheck....ok
t/50_vrename......ok
t/60_vpm..........*** You do not have VCS installed, not running rest of test!
ok
1/4 skipped:
All tests successful, 1 subtest skipped.
Files=8, Tests=57, 10 wallclock secs ( 5.58 cusr + 1.56 csys = 7.14 CPU)
The error about not having VCS is true, and we don't have
licenses for it. Hopefully, that hasn't messed up
Verilog-Perl, and that the failed tests for SystemPerl are
not caused by badly installed Verilog-Perl.
If anyone can suggest a course of action to get "make test"
for SystemPerl to look in the ~/INSTROOT tree, I would be
very grateful. Though it is (I think) an auxiliary problem,
any comments about the warnings re. the missing Verilog-Perl
modules, and the [non]necessity of VCS, would also be
appreciated. And if you think there is a more appropriate
group to which to post this issue, please let me know.
Fred
--
Fred Ma
Dept. of Electronics, Carleton University
1125 Colonel By Drive, Ottawa, Ontario
Canada, K1S 5B6
I'm building SystemPerl (trying to) and running into
problems. Technically, the question has to do with Make,
but I have a feeling it will be most answerable by someone
who has successfully built SystemPerl-1.148 as
nonadministrator (meaning that the installation takes place
in a directory that part of my user account, not in
directories that can only be modified by root e.g.
/usr/local/...).
Since I'm not root, I started the installation with "perl
Makefile.PL PREFIX=/home/fma/INSTROOT", where INSTROOT is my
version of /usr/local, in my file space. This has worked
for many utilities, including Wilson Snyder's
Verilog-Perl-2.231 (same author as SystemPerl, and similar
kind of install procedure). The "make" step went ahead
uneventfully, but the "make test" fails many tests e.g.:
t/05_template......Can't locate Verilog/Netlist/Subclass.pm
in @INC (@INC contains: ../Verilog/blib/arch
../Verilog/blib/lib .. blib/arch blib/lib .
/tmp/fma/SystemPerl-1.148/blib/lib
/tmp/fma/SystemPerl-1.148/blib/arch
/usr/local/lib/perl5/5.8.0/sun4-solaris
/usr/local/lib/perl5/5.8.0
/usr/local/lib/perl5/site_perl/5.8.0/sun4-solaris
/usr/local/lib/perl5/site_perl/5.8.0
/usr/local/lib/perl5/site_perl/sun4-solaris
/usr/local/lib/perl5/site_perl) at
blib/lib/SystemC/Template.pm line 23.
The other failures also can't find *.pm files. These files
do exist! They are under the file tree ~fma/INSTROOT, but
"make test" just isn't looking there. I looked at the
Makefile to see why. Makefiles are not my strong point, and
I'm picking it up from web tutorials, but it can get
extremely complicated. From the above message, it seems INC
isn't being set to include ~/INSTROOT. However, the
Makefile never even sets INC, it just uses it. Furthermore,
it sets $(INC), not @INC. According to the gnu make manual,
"@" merely forces Make execute commands silently. There are
also a few automatic variables prefixed with "@", but
nothing like "INC".
This failed tests *might* be related to warnings during the
initial step "perl Makefile.PL":
Warning: prerequisite Verilog::Getopt 2.211 not found.
Warning: prerequisite Verilog::Netlist 2.21 not found.
But I doubt it, considering that the test failure is due to
not finding a file because ~/INSTROOT is not being looked
in. Just in case, I emailed Wilson Snyder about these
warnings -- in particular, why I would be getting them if I
already installed Verilog-Perl (CPAN shows them to be part
of Verilog-Perl). I am not 100% confident about the
Verilog-Perl installation, since "make test" on that gives
a failed test:
t/10_keywords.....ok
t/12_splitbus.....ok
t/20_getopt.......ok
t/30_preproc......ok
t/40_netlist......ok
t/42_dumpcheck....ok
t/50_vrename......ok
t/60_vpm..........*** You do not have VCS installed, not running rest of test!
ok
1/4 skipped:
All tests successful, 1 subtest skipped.
Files=8, Tests=57, 10 wallclock secs ( 5.58 cusr + 1.56 csys = 7.14 CPU)
The error about not having VCS is true, and we don't have
licenses for it. Hopefully, that hasn't messed up
Verilog-Perl, and that the failed tests for SystemPerl are
not caused by badly installed Verilog-Perl.
If anyone can suggest a course of action to get "make test"
for SystemPerl to look in the ~/INSTROOT tree, I would be
very grateful. Though it is (I think) an auxiliary problem,
any comments about the warnings re. the missing Verilog-Perl
modules, and the [non]necessity of VCS, would also be
appreciated. And if you think there is a more appropriate
group to which to post this issue, please let me know.
Fred
--
Fred Ma
Dept. of Electronics, Carleton University
1125 Colonel By Drive, Ottawa, Ontario
Canada, K1S 5B6