From:	Martin Stromberg <Martin DOT Stromberg AT lu DOT erisoft DOT se>
Message-Id:	<200007041042.MAA11685@lws256.lu.erisoft.se>
Subject:	Re: DJGPP problem executing a script
To:	djgpp-workers AT delorie DOT com
Date:	Tue, 4 Jul 2000 12:42:12 +0200 (MET DST)
In-Reply-To:	<Pine.SUN.3.91.1000704130715.2527A-100000@is> from "Eli Zaretskii" at Jul 04, 2000 01:10:43 PM
X-Mailer:	ELM [version 2.5 PL3]
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> 
> 
> On Tue, 4 Jul 2000, Teun Burgers wrote:
> 
> > The problem is not that c:\djgpp\bin/perl.exe does not get invocated.
> > Somehow internally in perl c:\djgpp\bin propagates to @INC,
> > messing up @INC.
> 
> I'm quite Perl-illiterate, so I don't really know what @INC is, and how 
> does it relate to the variables defined by djgpp.env.  If it is derived 
> from DJDIR, it should have forward slashes.

It's saying where perl should look for its modules. Like the include
and lib directories for C. What's strange is that bin isn't usually in
the @INC variable. 

On our Solaris system, e. g.:
> perl5 -e 'print join(":", @INC ) . "\n" '
/local/share/fw/perl/5.005/lib/5.00502/sun4-solaris:/local/share/fw/perl/5.005/lib/5.00502:/local/share/fw/perl/5.005/lib/site_perl/5.005/sun4-solaris:/local/share/fw/perl/5.005/lib/site_perl/5.005:.


Right,

							MartinS

- Raw text -