Message: previous - next
Month: June 2012

Re: [trinity-devel] Suspect debugging symbols

From: Darrell Anderson <humanreadable@...>
Date: Mon, 18 Jun 2012 13:13:31 -0700 (PDT)
> IIRC I had this problem only for Qt3. Because of the unusual
> build system you could have to manually remove rpath:
> Removing the rpath after build has the advantage that the
> RPATH-enabled uic and moc ease the compilation of moc/uic-dependent parts
> of Qt.

How do I remove rpath after the build?

Second, I am build separate debugging symbol packages. Could that be related?

> If you want to build without rpath, you will have to either
> specify LD_LIBRARY_PATH in your build script or build the package
> where it is intended to be installed (and it is what Slackware does for
> Qt3 and Qt4).

In my Trinity builds I have been explicitly setting LD_LIBRARY_PATH=/opt/trinity/lib;/opt/trinity/lib/trinity. Should I stop doing that?

I'm trying to get my mind right about this. :-)

In my build logs sometimes I see something similar to this:

-rpath /opt/trinity/lib

Sometimes I see similar to this:

--rpath -Wl,/dev/shm/gwenview/src/gvcore/.libs -Wl,--rpath -Wl,/opt/trinity/lib -L/opt/trinity/lib