Re: DBD::Pg compilation errors

Andrew Dunstan <[email protected]>
Newsgroups gmane.comp.db.postgresql.dbdpg
Message-ID <[email protected]>
Kyle Herrmann wrote:

>I am posting this question to the DBDpg general discussion list, but please
>point me towards a more appropriate group if there is one.
>
>I am using CPAN to install DBI 1.51 and DBD::Pg 1.49 modules.  We are
>currently running the latest version of bizgres, which translates into
>postgres 8.1.3.
>
>On other machines I have been able to install DBD::Pg fairly easily, but
>I'm
>having trouble on a few that I am trying to setup for development.  The
>only
>thing I can see being different between these new systems and the currently
>working environments is that on the working systems they have
>DBI 1.50 installed.
>
>Here is the error I am seeing, and I would be curious if anyone has any
>pointers as to what it means:
>
>#     Error:  Can't load
>'~/.cpan/build/DBD-Pg-1.49/blib/arch/auto/DBD/Pg/Pg.so' for module DBD::Pg:
>libpq.so.4: cannot open shared object file: No such file or directory at
>/usr/lib/perl5/5.8.5/i386-linux-thread-multi/DynaLoader.pm line 230.
>#  at (eval 4) line 2
># Compilation failed in require at (eval 4) line 2.
>
>The README seems to have reference to shared library issues, but this error
>looks different than their examples and I'm not sure what to look for.  I
>did ldconfig -v and couldn't find any reference to libpq.so at all,
>although
>I ran the same command on our working environments and didn't see any
>references there either.
>
>Thanks for any thoughts on this issue.
>
>  
>


Well, you haven't told us what OS this is on, except indirectly :-) What 
distro is it? Some have binaries already built for you. FC5 for example 
has DBD::Pg 1.49 in updates, for example.

You must surely have libpq.so somewhere on your system - psql won't run 
without it. Maybe a find or locate command will show you where.

cheers

andrew
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.