Re: libpq.so.2.0 problem
От | Lamar Owen |
---|---|
Тема | Re: libpq.so.2.0 problem |
Дата | |
Msg-id | 3A082EF0.ECB082AA@wgcr.org обсуждение исходный текст |
Ответ на | libpq.so.2.0 problem (James Hall <James.Hall@RadioShack.com>) |
Список | pgsql-general |
Trond Eivind Glomsrød wrote: > James Hall <James.Hall@RadioShack.com> writes: > > I recently installed Redhat 7.0 and Postgres 7.0.2 on a new server... the > > install (of both) went better than expected, and I was able to get DBD and > > DBI up and running. When I copied my scripts (perl) over to the new server > > none ran. The error I received was "error in loading shared libraries > > libpq.so.2.0: cannot open shared object file: No such file or > > directory". > What refers to that file? The perl-DBD-Pg package. The version of this package installed is not given -- and that would be critical, here, as there are a number of versions to choose from, according to rpmfind. The version likely to be used would be perl-DBD-pg-0.91-2, which was built by RedHat for the CPAN archives -- and the dependency list for this package is: Provides: perl-DBD-Pg Pg.so Requires: perl ld-linux.so.2 libc.so.6 libpq.so.2.0 Only a Connectiva Linux perl-DBD-Pg RPM is being built (according to rpmfind.net, at least) against PostgreSQL 7 as of yet -- this would be perl-DBD-Pg-0.93-7cl. But I would think there would be more of a problem with Perl 5.6 versus 5.005 than any other issue. Symlink libpq.so.2.0 to libpq.so.2.1. This is the problem I have referred to in the past that causes problems with PHP RPM's as well. Or, if DBD::Pg was built from source on the previous machine, and binaries simply moved over, that would also cause this. And I'm working on my end of the fix -- copying libpq.so.2.x to libpq.so.2 instead of symlinking. But this will only help future packages that are built against PostgreSQL RPM's after I do that. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11
В списке pgsql-general по дате отправления: