[Pkg-libburnia-devel] adding symbol files to the burn library packages

Simon Huggins huggie at earth.li
Mon Mar 2 11:08:27 UTC 2009

On Mon, Mar 02, 2009 at 07:11:49AM +0200, George Danchev wrote:
> On Monday 02 March 2009 00:18:03 Simon Huggins wrote:
> > On Sun, Mar 01, 2009 at 07:32:24PM +0200, George Danchev wrote:
> > > I've just commited common symbols file for libburn4 package.
> > So now I'm confused because it's claiming that every symbol is new in
> > 0.6.2.
> >
> > That can't be true can it?
> Good bug report. I incorrectly assumed that the new verison of the
> library also produces common symbols file as claimed by mole for the
> previous version at:
> http://qa.debian.org/cgi-bin/mole/seedsymbols?pkgname=libburn4

> So, we should switch to arch specific symbols files: 
> debian/package.symbols.arch

> my libburn4.symbols became libburn4.symbols.i386 since I generated it out of 
> x86 object files. I suspect that you are building it on amd64, hence 
> arch-specific symbols differ. So I also added:

> Now if you build on amd64 you will still see dpkg-gensymbols show diff with 
> new symbols because symbols.amd64 is empty now. You can either patch it or I 
> can grab the arch-specific symbols diffs from autobuilders logs.

> Let me know if that answers your concerns.

But don't we have to do this for *older* versions of the library in
order for this to be useful?  I think I need to sit down with the docs
and get a handle on all of this really.

Simon Huggins  \ <pessoa> par definitions, les alcoviens sont les gens
                \ qui transforment du café en logiciel libre :))))))))
http://www.earth.li/~huggie/                                htag.pl 0.0.24

More information about the Pkg-libburnia-devel mailing list