From:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: perl testing
Date:	Thu, 10 Apr 2003 10:02:17 +0100
Lines:	29
Message-ID:	<3E953319.397195E4@phekda.freeserve.co.uk>
References:	<mx3la.4937$oJ2 DOT 742778 AT news20 DOT bellglobal DOT com>
NNTP-Posting-Host:	62.136.91.152
Mime-Version:	1.0
X-Trace:	newsg4.svr.pol.co.uk 1049965647 29076 62.136.91.152 (10 Apr 2003 09:07:27 GMT)
NNTP-Posting-Date:	10 Apr 2003 09:07:27 GMT
X-Complaints-To:	abuse AT theplanet DOT net
X-Mailer:	Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language:	de,fr
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hello.

Ian wrote:
>     I've installed the binary port of perl5.6.1 and I'm having no end of
> frustration with cpan.  I skipped cpan and downloaded the tarball of DBI and
> unpacked it with winzip 8 okay. perl Makefile.PL gave me errors and I'd like
> to know how to test perl itself (not DBI)?  There somewhere is a script that
> I can run which tests the perl installation.  Any pointers would be a great
> help in figuring out where I've messed up.

If you posted some error messages, that might help diagnose what's up.

I don't know of any tests to check the Perl installation. Perhaps using
autoconf or automake would be a good test. Or you could try something like
this from bash:

    echo foo > t.t
    perl -e 'use FileHandle; $fh = new FileHandle("<t.t"); while (<$fh>) {
print; } $fh->close();'

The perl command should all be on one line. It should display "foo". Maybe if
there was a problem with extracting the Perl distribution, you will get an
error. (FileHandle.pm does not fit exactly into 8+3, so this may highlight any
problems with extraction of the Perl binary archive.)

Regards,

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

- Raw text -