On Tue, Jun 21, 2011 at 08:43:17AM +0200, Picca Frédéric-Emmanuel wrote: > Hello Steve
> > The build failures have been almost entirely due to symbols that are not > > part of the library ABI, but are g++ implementation details instead. These > > symbols should be correctly marked 'optional', because /for each > > architecture/, they will come and go with changes to the toolchain. I think > > the reason you were having so many problems nailing down the symbol files is > > because you were racing various toolchain changes on the different > > architectures. :) > do we have a list somewhere explaining which symbols are optional > depending on the build tool chain ? Well, the dpkg-gensymbols(1) manpage mentions exactly the "C++ template instantiations" that I focused on in my first NMU. The other class I know of that affected things here were destructors, but I haven't seen any discussion of that problem before now. > I would like to add thoses symbols files to my package, but fill not > confortable enought to add them expecially for C++ libraries. debian-(devel,dpkg) may be a better place to discuss this, rather than in this bug report. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
