Tiger 2009 import on Mac OS X ... the pain never ends
28 views
Skip to first unread message
Greg Combs
Oct 14, 2010, 2:16:33 AM10/14/10
to GeoCommons Geocoder
So Mac OS X (and in my case, Mac OS X Server) includes sqlite3 ...
however it doesn't support loading extensions. This installation is
in /usr/bin, /usr/include, and /usr/lib
So, in my vanity, for the past 48 hours (near solid!) I've gone
through every conceivable scenario that I could find ...
... downloaded sqlite3 (many different minor versions and
configurations), built it to have loadable extensions, installed it
in /usr/local (in one case I accidentally installed it over the
existing binaries at /usr which blew up any application that uses Core
Data, i.e. everything we love about Apple) ... I even tried obscuring
the existing libraries and headers, also I loaded up a handful of
environment variables (DYLD_LIBRARY_PATH, LD_OPTIONS,
SQLITE3_LIB_PATH) to point to the new build
... I downloaded the preferred/modified sqlite3-ruby and got it
building ... but then I noticed it was building against the bad/
original sqlite3, hence a lot of the mucking about in the previous
paragraph. After a bit of fooling about, it wouldn't build anymore
because it couldn't find ruby.h ... which is only in half a dozen
places around the volume, none of which looked appealing to it. More
heavy handed bludgeoning of a few Makefiles and I'm none the better.
In all cases, because there's already a sqlite and because the
developer SDK and ruby and every other damned thing on the machine
knows where and what version the expected sqlite3 is ... I'm screwed.
Several things come to mind:
1. Am I missing something obvious?
2. Is there a better/easier way that doesn't involve me
reformatting the server for Linux?
3. Can someone pretty pretty please do me a real solid and just
hand me a preloaded tiger '09 db?
4. (yes, I know it's huge, that's why I have fiber to the house!)
5. Sometimes you just have to depend on the kindness of
strangers ...
g
however it doesn't support loading extensions. This installation is
in /usr/bin, /usr/include, and /usr/lib
So, in my vanity, for the past 48 hours (near solid!) I've gone
through every conceivable scenario that I could find ...
... downloaded sqlite3 (many different minor versions and
configurations), built it to have loadable extensions, installed it
in /usr/local (in one case I accidentally installed it over the
existing binaries at /usr which blew up any application that uses Core
Data, i.e. everything we love about Apple) ... I even tried obscuring
the existing libraries and headers, also I loaded up a handful of
environment variables (DYLD_LIBRARY_PATH, LD_OPTIONS,
SQLITE3_LIB_PATH) to point to the new build
... I downloaded the preferred/modified sqlite3-ruby and got it
building ... but then I noticed it was building against the bad/
original sqlite3, hence a lot of the mucking about in the previous
paragraph. After a bit of fooling about, it wouldn't build anymore
because it couldn't find ruby.h ... which is only in half a dozen
places around the volume, none of which looked appealing to it. More
heavy handed bludgeoning of a few Makefiles and I'm none the better.
In all cases, because there's already a sqlite and because the
developer SDK and ruby and every other damned thing on the machine
knows where and what version the expected sqlite3 is ... I'm screwed.
Several things come to mind:
1. Am I missing something obvious?
2. Is there a better/easier way that doesn't involve me
reformatting the server for Linux?
3. Can someone pretty pretty please do me a real solid and just
hand me a preloaded tiger '09 db?
4. (yes, I know it's huge, that's why I have fiber to the house!)
5. Sometimes you just have to depend on the kindness of
strangers ...
g
Kate Chapman
Oct 14, 2010, 7:10:28 AM10/14/10
to GeoCommons Geocoder
Hi Greg,
I haven't done anything with OSX Server so I can't be of much help
with your troubleshooting. I've run the geocoder multiple times on
OSX Leopard though without having the issues you are running into.
Here is the database: http://maploser.com/geocoder.db.gz
-Kate
I haven't done anything with OSX Server so I can't be of much help
with your troubleshooting. I've run the geocoder multiple times on
OSX Leopard though without having the issues you are running into.
Here is the database: http://maploser.com/geocoder.db.gz
-Kate
Greg Combs
Oct 14, 2010, 10:39:58 AM10/14/10
to GeoCommons Geocoder
Spectacular, thank you Kate. I'm grabbing it now.
Reply all
Reply to author
Forward
0 new messages