18 Jun
2012
18 Jun
'12
7:52 p.m.
On Mon, 18 Jun 2012 12:05:03 -0700 (PDT)
Darrell Anderson <humanreadable(a)yahoo.com> wrote:
Thanks. Does that mean I should build all packages with rpath
explicitly disabled?
cmake:
-DCMAKE_SKIP_RPATH=OFF
automake:
--disable-rpath
IIRC I had this problem only for Qt3. Because of the unusual build
system you could have to manually remove rpath:
http://wiki.debian.org/RpathIssue
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.
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).
I notice in my kcrash backtrace captures that
sometimes I see
references to files in "dev/shm." That is the location for
tmpfs/$TMP on my system, where I build packages.
Are those "dev/shm" references normal or am I doing something
wrong with creating my debugging symbol packages?
It could be rpath references. Last time I built Trinity Qt3
(for 3.5.13) my Qt3 package was f*cked up with /tmp/* rpaths.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting