I'm not sure how that will fix your libtool/tcl problems, but perhaps it
does. I took a quick look at the sqlite3 build and it looks like the
libtool/tcl problems could possibly be solved with a couple line fix to
their Makefile.in or tclinstaller.tcl. When sqlite3 installs using
their install target, it looks like they end up cherry picking
tlibtclsqlite3 from the .libs dir. They should be making libtool relink
it before they try to take a copy. Presumably fixing this and sending a
patch upstream that removes turds from the tcl support would be viewed
as a good thing.
-Norm
Nicolas Williams wrote:
> There may be a better way. SQLite3's build system actually provides a
> way to build what the SQLite community calls an "amalgamation" of all
> the sources that make up libsqlite3.so.
>
> So perhaps I can "gmake sqlite3.c" and I can build all three (+ 2 for
> 64-bit) ELF files the Solaris way, and I can use INS.file to install
> them. No more DESTDIR, no more libtool nonsense, no more ./install-sfw
> script. The only thing is I may need to patch the SQLite3 Makefile.in
> to define a target that allows me to extract all the CPP defines
> produced by ./configure.
>
> Nico
>
