On Wed, Nov 26, 2008 at 07:45:40PM +0100, "C. Bergstr?m" wrote: > When it comes to building against a multilib based system there's other > more elegant ways to depend on specific versions than > > LIBSQLITE = $(ROOT)/usr/lib/libsqlite.o > > To really explain why this should be avoided is an entirely different > thread I won't bore anyone here with..
I don't agree. SQLite is great, stable and all that. But SMF is so critical to system boot that it simply must not be allowed to break under any circumstance, so SQLite (version 2 in this case) really must be statically linked into svc.configd. You want as few dependencies as possible here. (Incidentally, the preferred way to build SQLite_3_ is as one big source file that the SQLite community calls the "amalgamation," thence into one big object file, thence into a shared object or library archive.) > -------------- > I'm done some basic optimizations on smf parts and during the build > > [...] > > I've changed dev env in the middle of all this and hoping to dodge > debugging this until after I get network is up on the target.. (which as > I'm finding out may not be svc related, but some other issue entirely) Just what are you trying to accomplish? Nico --
