Hi Sandro, Yes, installed from source. Yes, the "make check" step is where I'm seeing the problem.
An interesting thing occurred though. Once (exactly once out of perhaps 20 builds now) it all worked correctly, but failed the one of the topology tests. At that time I was unaware that the single failed topology test might be a red herring because of the version change. There's a ticket on that. Anyway, I went back and rebuilt with a modified switch and everything was lost again. I also see a difference in how the various json-c packages build. They just rolled a revision two days ago. >From the json-c package, should we be disabling "static" builds? DD On Oct 21, 2012, at 11:33 PM, Sandro Santilli <s...@keybit.net> wrote: > On Sat, Oct 20, 2012 at 05:39:51PM -0700, Daniel Devine wrote: >> Hi, >> >> I'm having the same trouble building PostGIS on AWS that some other posters >> here have encountered. >> >> ERROR: could not load library …..postgis-2.0.so: undefined symbol: >> json_tokener_errors > > Did you install postgis from sources ? > Did you run "make check" before installing ? Did it succeed ? > > Find your postgis-2.0.so file, run `ldd <postgis20_so>` on it and see if you > get any not-found message and if you get a libjson link line. > Then run `nm <libjson_file>` and see if you get any > ``json_tokener_errors`` line > > --strk; > > http://www.cartodb.com - Map, analyze and build applications with your data > > ~~ http://strk.keybit.net > > _______________________________________________ > postgis-users mailing list > postgis-users@postgis.refractions.net > http://postgis.refractions.net/mailman/listinfo/postgis-users _______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
