Re: dbi connection problem with @INC

2002-06-03 Thread tom poe
On Monday 03 June 2002 12:54, Michael Fowler wrote: > Copying the files over manually is usually a bad idea. Even if you do > manage to get all of the files (which you probably didn't, I will explain > later), the binary portions are probably not going to be compatible from > one version of perl

Re: dbi connection problem with @INC

2002-06-03 Thread Michael Fowler
On Sat, Jun 01, 2002 at 05:58:58PM -0700, tom poe wrote: > I copied the dirs/files to the upgrade 5.6.1, but no change, so I go, OK, > I'll make sure Pg.pm is copied over, then I'll get rid of the old one, and > this is just weird. Anyone have a thought about This? Copying the files over manua

Re: dbi connection problem with @INC

2002-06-01 Thread tom poe
Hi: Well, this is fun! I copied the dirs/files to the upgrade 5.6.1, but no change, so I go, OK, I'll make sure Pg.pm is copied over, then I'll get rid of the old one, and this is just weird. Anyone have a thought about This? tompoe@aether:~/perlStuff/dbi > cd /usr/lib/perl5/site_perl/5

Re: dbi connection problem with @INC

2002-06-01 Thread Janek Schleicher
Tom Poe wrote at Sun, 02 Jun 2002 00:26:24 +0200: > Hello: The script worked at one point, with use DBI; then, I upgraded perl from >5.6.0 to 5.6.1 > and got into trouble. I have both running now. What I want to do, is to figure out >how to get > use DBI to go find DBD/Pg.pm. Any pointers

dbi connection problem with @INC

2002-06-01 Thread tom poe
Hello: The script worked at one point, with use DBI; then, I upgraded perl from 5.6.0 to 5.6.1 and got into trouble. I have both running now. What I want to do, is to figure out how to get use DBI to go find DBD/Pg.pm. Any pointers appreciated. The error message follows: #! /usr/bin/perl