On Mon, 14 Apr 2014 11:23:29 Michael Tokarev wrote: > 14.04.2014 10:47, Dmitry Smirnov wrote: > > By the way do you think that just using "dh_makeshlibs -V" would be > > sufficient? Although I committed .symbols files I've never had good > > experience with symbols in C++ libraries and I have concerns for > > potential build problems on multiple architectures... > > Yes, this has happened in the past - a naive attempt to use dh_makeshlibs -V > resulted in package FTBFS on all arches except of the one where makeshlibs > were run, due to differences in complier and architectures wrt C++ symbols.
Actually I thought that "dh_makeshlibs -V" would be safe to use, safer than adding .symbols file(s) but perhas not that flexible... I'm considering to make upload of 0.72.2-3 with "dh_makeshlibs -V" -- would you recommend not to do that? How "dh_makeshlibs -V" can cause FTBFS? > I don't know ceph internals. If those C++ symbols are internal, and only > regular symbols should be exposed, maybe just hiding them all should be a > good idea. If, on the other hand, those are parts of public ABI, I'm afraid > there's no good solution except of the way you did it -- making all C++ > symbols to be part of the latest release. I wish I knew the answer to those questions. :) By the way thank you for useful comments in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679686#53 > Note that makeshlibs supports symbols.arch file in addition to symbols file, > maybe that one can be used to export (limited) set of C++ ABI. Thank you, I'll remember that. > I too have no expirience with C++ exporting and .symbols files. I found it so difficult to maintain symbols in C++ libraries so I just used "dh_makeshlibs -V" and it never failed me. > Besides, you added the two .symbols files into 0.79 package, -- maybe you > may run makeshlibs on 0.72 instead (or even on 0.44/0.48), to generate > initial .symbols files, and run mkshlibs again on new version(s) to make > additions. This way, even older lib may be used for symbols which were > present long time ago. Dunno how important it is. Will do, that's exactly what I was thinking about. Just need a bit more time to build... :) Thank you. -- All the best, Dmitry Smirnov. --- However beautiful the strategy, you should occasionally look at the results. -- Winston Churchill
signature.asc
Description: This is a digitally signed message part.
