Your message dated Mon, 14 Sep 2015 09:34:23 +0200
with message-id <20150914073423.ga28...@hephaistos.amsuess.com>
and subject line FTBFS solved in 2015.03-1+dfsg-1
has caused the Debian Bug report #790776,
regarding FTBFS: error adding symbols: DSO missing from command line
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
790776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openscad
Version: 2014.03+dfsg-1
Severity: serious
openscad fails to build in unstable:
> sbuild (Debian sbuild) 0.64.1 (13 Oct 2013) on m400-c4n1.hlinux.usa.hp.com
...
> make[4]: Leaving directory '/«BUILDDIR»/openscad-2014.03+dfsg/tests'
> make[4]: Entering directory '/«BUILDDIR»/openscad-2014.03+dfsg/tests'
> [ 98%] Building CXX object
> CMakeFiles/openscad_nogui.dir/«BUILDDIR»/openscad-2014.03+dfsg/src/openscad.cc.o
> Linking CXX executable openscad_nogui
> /usr/bin/ld: libtests-offscreen.a(OffscreenContextGLX.cc.o): undefined
> reference to symbol 'XGetErrorText'
> //usr/lib/aarch64-linux-gnu/libX11.so.6: error adding symbols: DSO missing
> from command line
> collect2: error: ld returned 1 exit status
> CMakeFiles/openscad_nogui.dir/build.make:123: recipe for target
> 'openscad_nogui' failed
> make[4]: *** [openscad_nogui] Error 1
> make[4]: Leaving directory '/«BUILDDIR»/openscad-2014.03+dfsg/tests'
> CMakeFiles/Makefile2:175: recipe for target
> 'CMakeFiles/openscad_nogui.dir/all' failed
--
Martin Michlmayr
Linux for HP Helion OpenStack, Hewlett-Packard
--- End Message ---
--- Begin Message ---
notfound 790776 2015.03-1+dfsg-1
thank you
the missing -lX11 that caused this bug was probably fixed by
> * New patches:
> * Build system: Work around missing -lX11
in the 2015.03-1+dfsg-1 version; closing the bug.
--- End Message ---
