On Tue, Apr 16, 2013 at 03:40:51PM -0400, Lennart Sorensen wrote: > Installing libvtk5.8 and tcl-vtk version 5.8.0-12 makes the symbol > problem go away and volview starts fine. Install 5.8.0-13 or 5.8.0-13+b1, > and the problem occours again. > > Not sure which of this caused a problem: > > vtk (5.8.0-13) unstable; urgency=low > > * Make sure to include VTK/QT cmake file. Closes: #656115 > * Revert back to libtiff4-dev and use libtiff-dev in d/control. Closes: > #674998 > * Fix tkInt.h installation, using proper cmake magic. Closes: #674169 > * Make sure to discover init.tcl properly. Closes: #673245 > > -- Mathieu Malaterre <ma...@debian.org> Wed, 30 May 2012 13:48:14 +0200 > > My current suspicion is: > > --- vtk-5.8.0-12/debian/rules 2012-05-16 05:06:53.000000000 -0400 > +++ vtk-5.8.0-13/debian/rules 2012-05-30 07:47:25.000000000 -0400 > @@ -3,6 +3,10 @@ > # Uncomment this to turn on verbose mode. > #export DH_VERBOSE=1 > > +export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed > +DPKG_EXPORT_BUILDFLAGS = 1 > +-include /usr/share/dpkg/buildflags.mk > + > DEB_HOST_ARCH ?=$(shell dpkg-architecture -qDEB_HOST_ARCH) > DEB_HOST_ARCH_CPU ?=$(shell dpkg-architecture -qDEB_HOST_ARCH_CPU) > > I am trying to recompile with that removed to see if that is the cause.
Confirmed. Building with that change removed, makes volview work again. Putting it back in causes the missing symbol error. Of course rebuilding volview instead also fixes it. I have no idea why that argument to ld would break things, but it seems it does. So is this change sensible? Should it be breaking users of the library? Should volview be rebuilt to solve this, or should vtk have this change removed? Is this a volview or a vtk bug? -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
