trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: June 2012

Re: [trinity-devel] Suspect debugging symbols

From: /dev/ammo42 <mickeytintincolle@...>
Date: Mon, 18 Jun 2012 22:04:32 +0200
On Mon, 18 Jun 2012 12:34:24 -0700 (PDT)
Darrell Anderson <humanreadable@...> wrote:

> > > > 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.
> > 
> > Thanks. Does that mean I should build all packages with
> > rpath explicitly disabled?
> > 
> > cmake:
> > -DCMAKE_SKIP_RPATH=OFF
> > 
> > automake:
> > --disable-rpath
> > 
> 
> By the way, in all of my Trinity builds I set
> LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/trinity. Does that
> make a difference?

These paths are the ones for the final packages. They should be added
to /etc/ld.so.conf, and I think the install script of the package
every other one needs (so I suppose it's qt3/tqt3) is a good place to
do that.
If you choose that way, don't forget to take account of the lib->lib64
transformation when 64-bit packages are built; you can take the Qt3
build script of KDE 3.5.10 for Slackware 13.0 as an example.
(for $trinityprefix/lib{,64} your (T)Qt3 build script perhaps already
does that)
> 
> Darrell
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> trinity-devel-unsubscribe@... For additional
> commands, e-mail: trinity-devel-help@... 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
>