-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 4/26/11 11:30 AM, Fritz Hudnut wrote:
> Dr H:
> 
> Went further up in FC log of the sawfish install process and found that
> one test failed out of 963 and then under that test list some comments
> on perl were found:  I'm just showing a few of the tests above and below
> the failed test, not all 993:
> 

fair enough.  We probably only need the failed one.

> <paste>
> lib/Locale/Maketext/t/60_super............ok
> lib/Locale/Maketext/t/90_utf8.............ok
> lib/locale................................FAILED at test 99
> lib/Math/BigInt/t/bare_mbf................ok
> lib/Math/BigInt/t/bare_mbi................ok
> lib/Math/BigInt/t/bare_mif................ok
> <snip>
> <paste>
> t/x2p/s2p.................................ok
> Failed 1 test script out of 963, 99.90% 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,
> ### DYLD_LIBRARY_PATH, to point to the build directory:
> ###   setenv DYLD_LIBRARY_PATH `pwd`; cd t; ./perl harness
> ###   DYLD_LIBRARY_PATH=`pwd`; export DYLD_LIBRARY_PATH; cd t; ./perl
> harness
> ###   export DYLD_LIBRARY_PATH=`pwd`; cd t; ./perl harness
> ### for csh-style shells, like tcsh; or for traditional/modern
> ### Bourne-style shells, like bash, ksh, and zsh, respectively.
> u=10.38  s=7.66  cu=552.84  cs=181.57  scripts=963  tests=118092
> make[2]: *** [_test_notty] Error 1
> make[1]: *** [_test] Error 2
> make: *** [test] Error 2
> ### execution of /var/tmp/tmp.3.ukDfmC failed, exit code 2
> Removing runtime build-lock...
> Removing build-lock package...
> /sw/bin/dpkg-lockwait -r fink-buildlock-perl588-5.8.8-9
> (Reading database ... 62905 files and directories currently installed.)
> Removing fink-buildlock-perl588-5.8.8-9 ...
> Updating the list of locally available binary packages.
> Scanning dists/stable/main/binary-darwin-powerpc
> <snip>
> Reading Package Lists...
> Building Dependency Tree...
> Failed: phase compiling: perl588-5.8.8-9 failed
> 
> Before reporting any errors, please run "fink selfupdate" and
> try again.  If you continue to have issues, please check to see if the
> FAQ on fink's website solves the problem.  If not, ask on the fink-users
> or fink-beginners mailing lists, with a carbon copy to the maintainer:
> 
>     Fink Core Group <[email protected]
> <mailto:[email protected]>>
> <un-paste>
> 
> ------------------------------------------------------------------------------------
> -------------------------------------------------
> 
> So I'm seeing that after the ### signs are some suggested options but it
> seems like the suggestions are for different commands and now I know
> that these suggestions exist in the log but what do I do with them? 
> E.g., what is a 't' directory?

It's a subdirectory that is somewhere within the the directory that Fink
temporarily creates to build perl-5.8.8, which is

/sw/src/fink.build/perl588-5.8.8-9

or something similar.  I don't know the exact location right now, but it
may be

/sw/src/fink.build/perl588-5.8.8-9/perl-5.8.8/t

> 
> And, as I scroll thru the list I see that FC asks itself questions,
> e.g., "do we have the package?"  and then it answers itself, e.g., "yes"
> or "no" . . . and then it does stuff, so why is it that FC isn't running
> the tests it suggests in the log after the ### itself?  Considering it
> looks like only one test failed why shut down the install? 

There are two different varieties of tests going on.

1)  The tests at the beginning are performed so that perl588 knows
exactly what options to use in building.

2)  The tests at the end are to make sure that everything is set up
correctly.  These are tests _using_ stuff from the perl588 package, and
therefore require the package to have been built already, so they can't
be run at step #1.

Often packages either don't use #2 or they make it optional.  In this
case, the perl588 package appears to have had tests turned on explicitly
for powerpc machines.   Presumably it's set up to be fatal (by the Perl
developers in this case, rather than by Fink) for failed tests because
when it misbuilds it will behave improperly.
> 
> F
> http://surfingthetimelesswave.net
> 
> 
> 


- -- 
Alexander Hansen, Ph.D.
Fink User Liaison
http://finkakh.wordpress.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk23EtkACgkQB8UpO3rKjQ9SjACfd9A9sqFEITAxpZKv5rhSYF0F
2Z4An2c2Q+TxT8jRo65d0LLnkz0xpzsy
=jegh
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Fink-beginners mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.apple.fink.beginners
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-beginners

Reply via email to