Re: Trouble with Test::Smoke 1.12

[email protected] ("H.Merijn Brand")
Newsgroups perl.daily-build
Message-ID <[email protected]>
On Thu 11 Apr 2002 14:43, Kay Roepke <[email protected]> wrote:
> Hi!
> 
> I tried to setup a smoke site, but I always run into this kind of 
> failure (the mktest.rpt has all '-' as test results - Not sure whether 
> those have been sent to the list or not... :-( ):
> 
> Regards,
> 
> Kay
> 
> snippet from mktest.log:
> [...]
> 1281 bytes (28.6%) saved spotting duplicates
> 1 bytes (99.8%) saved using substrings
> Processing hints file hints/linux.pl
> Note (probably harmless): No library found for -lposix
> Note (probably harmless): No library found for -lcposix

All harmless, and will be filtered in the next version of smoke

> make: [extras.make] Error 1 (ignored)
> 
>   Tests start here:
> PERLIO = stdio  /bin/sh: TEST: command not found

not harmless, but easy to solve. '.' is not in your $PATH

Either
1. Put '.' in $PATH in smoke.sh

	export PATH=.:$PATH

2. Put '.' in $ENV{PATH} in mktest.pl

	$ENV{PATH} .= ":.";

Security issues are being discussed. Might also be `solved' in the bleadperl
distribution itself.

Thanks for participating

> make[1]: *** [_test_tty] Error 127
> make: *** [_test] Error 2
> 
> PERLIO = perlio /bin/sh: TEST: command not found
> make[1]: *** [_test_tty] Error 127
> make: *** [_test] Error 2
> 
> 
> Configuration: -Dusedevel -Duseperlio -DDEBUGGING
> ------------------------------------------------------------------------------
> Make distclean ...
> Copy Policy.sh ...
> Configure ...
> [...]

-- 
H.Merijn Brand        Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using perl-5.6.1, 5.7.3 & 631 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3,
  WinNT 4, Win2K pro & WinCE 2.11.  Smoking perl CORE: [email protected]
http://archives.develooper.com/[email protected]/   [email protected]
send smoke reports to: [email protected], QA: http://qa.perl.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.