[Xcb] print backtraces in case an assert fails inside xlib/xcb

Julien Cristau jcristau at debian.org
Thu Jun 7 19:13:51 PDT 2007


On Thu, Jun  7, 2007 at 18:10:00 -0700, Barton C Massey wrote:

> I don't understand the ".la contamination" issue.  Could
> someone who understands it please enlighten me?
> 
Basically, the problem is that libtool sucks.  When a library is built
with libtool, it installs a libfoo.la alongside libfoo.{so,a}.  This .la
file has, among other things, dependency information, which means that
it references every single library in the dependency tree of libfoo.  So
if you rebuild libX11 without xcb, and uninstall libxcb, you still have
tons of files referencing libxcb-xlib.la which make later builds of
unrelated stuff fail.
As far as I can tell, the fix is to not install .la files (which is what
we do for the X libraries in Debian), or rm /usr/lib/*.la.

Cheers,
Julien


More information about the Xcb mailing list