On Wed, Feb 27, 2008 at 01:51:32PM -0600, Norm Jacobs wrote: > Nicolas Williams wrote: > >On Wed, Feb 27, 2008 at 01:37:26PM -0600, Norm Jacobs wrote: > > > >>Nicolas Williams wrote: > >> > >>>On Wed, Feb 27, 2008 at 11:16:26AM -0800, Danek Duvall wrote: > >>> > >>> > >>>>On Wed, Feb 27, 2008 at 12:58:15PM -0600, Nicolas Williams wrote: > >>>> > >>>> - if there's no .la file for libtool to read, then it will stick > >>>> various > >>>> crud paths in the RUNPATH of the executables it creates, including > >>>> the > >>>> directories where its dependencies lie in the source > >>>> > >>>> > >>>It's the reverse. The libtool link command line that creates > >>>libtclsqlite3.so is referencing the libsqlite3.la in the current > >>>directory, which causes the current directory (+ /.libs) to be added to > >>>the RUNPATH by libtool, because it's trying to be helpful. > >>> > >>> > >>I have run into this before with other components that use libtool. If > >>you use the component's install target, libtool should relink without > >>the references to your workspace before installing the file. > >> > > > >Could you elaborate? What do you mean by "[i]f you use the component's > >install target"? > > > (cd $(VER) ; make DESTDIR=/tmp/foo install)
That's what I do now. It leaves turds in libtclsqlite3.so. I won't continue this sub-thread.
