Seems like the 'op/cproto' and 'op/pat' tests need to be more careful with what they try to load. This is bleadperl@21657. Regards, Gisle $ make minitest You may see some irrelevant test failures if you have been unable to build lib/Config.pm or lib/lib.pm. cd t && (rm -f perl; /bin/ln -s ../miniperl perl) \ && LD_LIBRARY_PATH=/local/perl/src/perl-hack ./perl TEST base/*.t comp/*.t cmd/*.t run/*.t io/*.t op/*.t uni/*.t </dev/tty t/base/cond..........ok t/base/if............ok t/base/lex...........ok [...] t/op/cond............ok t/op/context.........ok t/op/cproto..........Can't load module threads, dynamic loading not available in this perl. (You may need to build a new perl executable which either supports dynamic loading or has the threads module statically linked into it.) at ../lib/Test/Builder.pm line 20 Compilation failed in require at ../lib/Test/Builder.pm line 20. BEGIN failed--compilation aborted at ../lib/Test/Builder.pm line 28. Compilation failed in require at ../lib/Test/More.pm line 6. BEGIN failed--compilation aborted at ../lib/Test/More.pm line 6. Compilation failed in require at op/cproto.t line 9. BEGIN failed--compilation aborted at op/cproto.t line 9. FAILED at test 0 t/op/crypt...........ok t/op/defins..........ok [...] t/op/override........ok t/op/pack............ok t/op/pat.............Can't load module Storable, dynamic loading not available in this perl. (You may need to build a new perl executable which either supports dynamic loading or has the Storable module statically linked into it.) at ../lib/Unicode/UCD.pm line 8 Compilation failed in require at ../lib/Unicode/UCD.pm line 8. BEGIN failed--compilation aborted at ../lib/Unicode/UCD.pm line 8. Compilation failed in require at ../lib/charnames.pm line 241. Compilation failed in require at op/pat.t line 1371. BEGIN failed--compilation aborted at op/pat.t line 1371. FAILED at test 0 t/op/pos.............ok t/op/pow.............ok t/op/push............ok [...] t/uni/upper..........ok t/uni/write..........ok Failed 2 test scripts out of 191, 98.95% okay. ### Since not all tests were successful, you may want to run some of ### them individually and examine any diagnostic messages they produce. ### See the INSTALL document's section on "make test". ### You have a good chance to get more information by running ### ./perl harness ### in the 't' directory since most (>=80%) of the tests succeeded. ### You may have to set your dynamic library search path, ### LD_LIBRARY_PATH, to point to the build directory: ### setenv LD_LIBRARY_PATH `pwd`:$LD_LIBRARY_PATH; cd t; ./perl harness ### LD_LIBRARY_PATH=`pwd`:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd t; ./perl harness ### export LD_LIBRARY_PATH=`pwd`:$LD_LIBRARY_PATH; cd t; ./perl harness ### for csh-style shells, like tcsh; or for traditional/modern ### Bourne-style shells, like bash, ksh, and zsh, respectively. u=0.52 s=0.09 cu=13.57 cs=3.31 scripts=191 tests=26654Thread Next