Bug#675846: marked as done (ovito: FTBFS[any-amd64]: relocation R_X86_64_32 against `solid_background_texture' can not be used when making a shared object; recompile with -fPIC)
Your message dated Wed, 27 Jun 2012 17:42:50 +0300
with message-id <685941340808170@web23g.yandex.ru>
and subject line Re: Bug#675846: ovito: FTBFS[any-amd64]: ...
has caused the Debian Bug report #675846,
regarding ovito: FTBFS[any-amd64]: relocation R_X86_64_32 against `solid_background_texture' can not be used when making a shared object; recompile with -fPIC
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 owner@bugs.debian.org
immediately.)
--
675846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675846
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:ovito
Version: 0.9.5-2
Severity: serious
Tags: sid wheezy
Justification: fails to build from source (but built successfully in the past)
Hi!
Your package failed to build on the buildds:
Linking CXX shared library ../../lib/ovito/plugins/libTachyon.so
cd /build/buildd-ovito_0.9.5-2-kfreebsd-amd64-koPxNo/ovito-0.9.5/obj-x86_64-kfreebsd-gnu/src/tachyon && /usr/bin/cmake -E cmake_link_script CMakeFiles/Tachyon.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fmessage-length=0 -DBOOST_PYTHON_DYNAMIC_LIB -DBOOST_PYTHON_DYNAMIC_MODULE -ftemplate-depth-100 -DMAKING_MODULE_TACHYON -O3 -DNDEBUG -DQT_NO_DEBUG=1 -DQT_NO_DEBUG_OUTPUT=1 -Wl,-z,relro -shared -Wl,-soname,libTachyon.so -o ../../lib/ovito/plugins/libTachyon.so CMakeFiles/Tachyon.dir/PrecompiledHeader.cpp.o CMakeFiles/Tachyon.dir/renderer/TachyonRenderer.cpp.o CMakeFiles/Tachyon.dir/renderer/TachyonRendererEditor.cpp.o CMakeFiles/Tachyon.dir/renderer/moc_TachyonRenderer.cxx.o CMakeFiles/Tachyon.dir/renderer/moc_TachyonRendererEditor.cxx.o CMakeFiles/Tachyon.dir/renderer/moc_TachyonExportInterface.cxx.o -L/build/buildd-ovito_0.9.5-2-kfreebsd-amd64-koPxNo/ovito-0.9.5/obj-x86_64-kfreebsd-gnu/lib/ovito/plugins ../../lib/ovito/libBase.so ../../lib/ovito/libCore.so ../../lib/ovito/libMesh.so -lQtOpenGL -lQtGui -lQtXml -lQtNetwork -lQtCore -lGLU -lboost_iostreams-mt -lboost_python -ltachyon ../../lib/ovito/libBase.so -lQtOpenGL -lQtGui -lQtXml -lQtNetwork -lQtCore -lGL -lutil -ldl -lpthread -lpython2.7 -lboost_python -Wl,-rpath,"\$ORIGIN/../lib/ovito"
/usr/bin/ld: /usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/../../../../lib/libtachyon.a(api.o): relocation R_X86_64_32 against `solid_background_texture' can not be used when making a shared object; recompile with -fPIC
/usr/lib/gcc/x86_64-kfreebsd-gnu/4.7/../../../../lib/libtachyon.a: could not read symbols: Bad value
collect2: error: ld returned 1 exit status
make[4]: *** [lib/ovito/plugins/libTachyon.so] Error 1
make[4]: Leaving directory `/build/buildd-ovito_0.9.5-2-kfreebsd-amd64-koPxNo/ovito-0.9.5/obj-x86_64-kfreebsd-gnu'
make[3]: *** [src/tachyon/CMakeFiles/Tachyon.dir/all] Error 2
/usr/bin/cmake -E cmake_progress_report /build/buildd-ovito_0.9.5-2-kfreebsd-amd64-koPxNo/ovito-0.9.5/obj-x86_64-kfreebsd-gnu/CMakeFiles
make[3]: *** Waiting for unfinished jobs....
[ 65%] Building CXX object
src/scripting/CMakeFiles/Scripting.dir/interface/PythonInterface.cpp.o
Full build log at
https://buildd.debian.org/status/fetch.php?pkg=ovito&arch=kfreebsd-amd64&ver=0.9.5-2&stamp=1338315215
Regards
Christoph
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
--- End Message ---
--- Begin Message ---
Hi,
Bug report #675714 was fixed:
http://bugs.debian.org/675714
And ovito package was rebuild successfully:
https://buildd.debian.org/status/package.php?p=ovito
Regards,
Boris
--- End Message ---
Reply to: