Your message dated Tue, 31 May 2011 01:15:25 +0200
with message-id <[email protected]>
and subject line Closing bug #620625: ogre v1.6.4 is not in the archive anymore
has caused the Debian Bug report #558941,
regarding Resolve unresolved symbols in shared libraries
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 [email protected]
immediately.)
--
558941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558941
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ogre
Version: 1.6.4.dfsg1-1
Severity: wishlist
User: [email protected]
Usertags: unresolved-symbols-so
I build all packages some time ago with binutils-gold and your package build
without an hard failure, but I noticed that you seems to provide a library in
a specific library package so other packages can link against it without
problems.... but your shared object has still some unresolved symbols which
the program which links agaomst it must resolve. This isnt a good idea because
when you introduce new dependencies the package previously linked against the
old version will break because it doesnt know about the new dependency.
Maybe you could link against all needed libraries so programs must not link
against libraries which it doesnt need to use.
Maybe it is related to following bugs which hard failed due to unresolved
symbols in programs
http://bugs.debian.org/cgi-bin/[email protected];tag=no-add-needed
More informations can be found at
http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking
dpkg-shlibdeps already showed you the related warnings:
dpkg-shlibdeps: warning: symbol _ZN4Ogre10VertexDataD1Ev used by
debian/libceguiogrerenderer-1.6.4/usr/lib/libCEGUIOgreRenderer-1.6.4.so found
in none of the libraries.
dpkg-shlibdeps: warning: symbol _ZN4Ogre12NedAllocImpl12deallocBytesEPv used by
debian/libceguiogrerenderer-1.6.4/usr/lib/libCEGUIOgreRenderer-1.6.4.so found
in none of the libraries.
dpkg-shlibdeps: warning: symbol _ZN5CEGUI8Renderer14EventNamespaceE used by
debian/libceguiogrerenderer-1.6.4/usr/lib/libCEGUIOgreRenderer-1.6.4.so found
in none of the libraries.
dpkg-shlibdeps: warning: symbol _ZNK5CEGUI6String15build_utf8_buffEv used by
debian/libceguiogrerenderer-1.6.4/usr/lib/libCEGUIOgreRenderer-1.6.4.so found
in none of the libraries.
dpkg-shlibdeps: warning: symbol _ZN5CEGUI6String4nposE used by
debian/libceguiogrerenderer-1.6.4/usr/lib/libCEGUIOgreRenderer-1.6.4.so found
in none of the libraries.
dpkg-shlibdeps: warning: symbol
_ZN5CEGUI8EventSet22subscribeScriptedEventERKNS_6StringEjS3_ used by
debian/libceguiogrerenderer-1.6.4/usr/lib/libCEGUIOgreRenderer-1.6.4.so found
in none of the libraries.
dpkg-shlibdeps: warning: symbol _ZN5CEGUI6String4growEm used by
debian/libceguiogrerenderer-1.6.4/usr/lib/libCEGUIOgreRenderer-1.6.4.so found
in none of the libraries.
dpkg-shlibdeps: warning: symbol _ZN5CEGUI9ExceptionC2ERKNS_6StringES3_S3_i used
by debian/libceguiogrerenderer-1.6.4/usr/lib/libCEGUIOgreRenderer-1.6.4.so
found in none of the libraries.
dpkg-shlibdeps: warning: symbol _ZN4Ogre21HardwareBufferManager12getSingletonEv
used by debian/libceguiogrerenderer-1.6.4/usr/lib/libCEGUIOgreRenderer-1.6.4.so
found in none of the libraries.
dpkg-shlibdeps: warning: symbol _ZN4Ogre16MemoryDataStreamC1EPvmb used by
debian/libceguiogrerenderer-1.6.4/usr/lib/libCEGUIOgreRenderer-1.6.4.so found
in none of the libraries.
dpkg-shlibdeps: warning: 37 other similar warnings have been skipped (use -v to
see them all).
--- End Message ---
--- Begin Message ---
Hello,
I am closing this bug since v1.6.4 is not going to be in the archive
anymore. It was removed from testing today, and I am preparing new versions
of upstream 1.7.*.
Nobody reported problems with 1.7.0 and binutils-gold, although it might be
simply because nobody tested it. I tried to build with binutils-gold in the
pbuilder environment, and unless I did something wrong, no problems were
reported.
Anyway, it would be nice if you could try to build the package v1.7.* again
and confirm that now everything's fine, or otherwise reopen the bug with new
info.
Cheers and thanks for your bug report.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
