Postgres Pro
Downloads
Home   >   mailing lists

Re: Trouble installing PostGIS on Amazon Linux server - Mailing list pgsql-general

From Augori
Subject Re: Trouble installing PostGIS on Amazon Linux server
Date
Msg-id CAFE+72NseLszmXJ6Y8fs_NM_Xhqv2aMH=3sSVioH5nQARizVUg@mail.gmail.com
Whole thread Raw
In response to Re: Trouble installing PostGIS on Amazon Linux server  (Chris Mair <chris@1006.org>)
Responses Re: Trouble installing PostGIS on Amazon Linux server
List pgsql-general
Tree view
It installed poppler successfully but still gives the same error.  I did notice that it installed libpoppler 37 and the postgis2_93 install error seems to be looking for version 5
[root@ip-user]# ls /usr/lib64/libpo*
/usr/lib64/libpoppler-cpp.so        /usr/lib64/libpoppler.so
/usr/lib64/libpoppler-cpp.so.0      /usr/lib64/libpoppler.so.37
/usr/lib64/libpoppler-cpp.so.0.2.0  /usr/lib64/libpoppler.so.37.0.0

[root@ip-ec2-user]# yum install postgis2_93 --enablerepo=epel   (same results both with and without the enable repo flag)
.
. (lots of stuff not included here)
.
Error: Package: gdal-libs-1.9.2-6.rhel6.x86_64 (pgdg93)
           Requires: libpoppler.so.5()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Perhaps I should uninstall the 37 version and install the 5.0 version?  Any idea how to get it to install the 5.0 version?

Thanks


On Sun, Feb 14, 2016 at 11:14 PM, Chris Mair <chris@1006.org> wrote:

Error: Package: gdal-libs-1.9.2-6.rhel6.x86_64 (pgdg93)
            Requires: libpoppler.so.5()(64bit)
  You could try using --skip-broken to work around the problem
  You could try running: rpm -Va --nofiles --nodigest

 Hi,

what happens if you try to install libpoppler (it is in the standard Amazon repo)?

yum install poppler poppler-devel poppler-cpp poppler-cpp-devel

Bye,
Chris.



pgsql-general by date:

Previous
From: "FarjadFarid\(ChkNet\)"
Date:
Subject: Re: PosgreSQL Security Architecture
Next
From: Alvaro Herrera
Date:
Subject: Re: Transaction ID not logged if no explicit transaction used