Opened 11 years ago

Closed 11 years ago

#2458 closed defect (invalid)

liblwgeom-2.1.0.so not found by loader utilities

Reported by: kentr Owned by: strk
Priority: critical Milestone: PostGIS 2.1.1
Component: postgis Version: 2.1.x
Keywords: Cc:

Description

Unsure if this is a bug or just my own error in installation.

After performing documented installation procedure, I received this error when executing loader utilities:

/usr/lib/postgresql/9.2/bin/shp2pgsql: error while loading shared libraries: liblwgeom-2.1.0.so: cannot open shared object file: No such file or directory

Discovered that running the command within the build directory, it worked as expected (meaning, I got the version / help text output):

loader/shp2pgsql

Found that if I copied these two liblwgeom files to /usr/lib, then the installed binary also worked as expected:

liblwgeom/.libs/liblwgeom-2.1.0.so
liblwgeom/.libs/liblwgeom.so

Change History (7)

comment:1 by pramsey, 11 years ago

Just dropping in here to point out that shared libraries don't make installation more reliable.

comment:2 by pramsey, 11 years ago

Owner: changed from pramsey to strk

comment:3 by robe, 11 years ago

Milestone: PostGIS 2.1.1

comment:4 by strk, 11 years ago

kentr: do you have liblwgeom-2.1.0.so under /usr/local/lib ? Is that dir scanned by the dynamic loader ? grep local /etc/ld.so.conf /etc/ld.so.conf.d/* Did you run ldconfig after installation ? (this is something we might want to do automatically in the future).

I'd note that builders should be familiar with these topics.

comment:5 by kentr, 11 years ago

Sorry, haven't had a chance to re-do this and confirm that running ldconfig works.

I'm happy to take your word for it.

Understood that builders would normally be familiar with these topics.

I (a noob) was building PostGIS 2.1.x b/c I'm running Lucid (the Lucid package is 2.0.2), so others may find themselves in this boat (and out of their element). Though I searched around for the meaning of the error message (and solutions), I didn't come across ldconfig.

Your suggestion of running ldconfig automatically is a good one.

comment:6 by strk, 11 years ago

I've found out that libtool version 2.4.2 already runs ldconfig on —mode=install

comment:7 by strk, 11 years ago

Resolution: invalid
Status: newclosed

closing as I don't think it's to be considered a bug

Note: See TracTickets for help on using tickets.