Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!sdd.hp.com!elroy.jpl.nasa.gov!jpl-devvax!lwall
From: lwall@jpl-devvax.jpl.nasa.gov (Larry Wall)
Newsgroups: comp.lang.perl
Subject: Re: possible problem with perl's TEST
Message-ID: <1991Apr18.233207.520@jpl-devvax.jpl.nasa.gov>
Date: 18 Apr 91 23:32:07 GMT
References: <1991Apr5.172457.10599@infonode.ingr.com> <guy.670894399@guy> <1991Apr14.235128.9435@kpc.com>
Reply-To: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall)
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 17

In article <1991Apr14.235128.9435@kpc.com> mac@kpc.com (Mike McNamara) writes:
: 	So how I naively ran the tests was to cd to t and type ./TEST.
: If I had stayed in the perl directory, and typed t/TEST, then 
: #! ./perl 
: would have worked.

Only on t/TEST itself.  TEST immediately chdirs to t, so base/whatever.t looks
for perl in the t directory.

: Or, a symbolic link could have been made from
: t/perl to ../perl

Which is precisely what "make test" does.  The reason that the tests
look for perl in t/ is that it gives you the option of pointing the
symlink at some other perl to test, such as the currently installed one.

Larry