Re: grokking debian symbols files

2014-04-04 Thread Jakub Wilk
* Sune Vuorela , 2014-04-04, 08:01: It's a pkgkde-symbolshelper(1)'s (from the pkg-kde-tools package) thing. But AFIACS pkgkde-symbolshelper doesn't have any documentation, so the “is not explained” still holds. :/ http://pkg-kde.alioth.debian.org/symbolfiles.html If it's not in the manpage

Re: grokking debian symbols files

2014-04-04 Thread Sune Vuorela
On 2014-04-04, Jakub Wilk wrote: > It's a pkgkde-symbolshelper(1)'s (from the pkg-kde-tools package) thing. > But AFIACS pkgkde-symbolshelper doesn't have any documentation, so the > “is not explained” still holds. :/ http://pkg-kde.alioth.debian.org/symbolfiles.html > Hopefully it's a matter

Re: grokking debian symbols files

2014-04-04 Thread Jakub Wilk
* Wookey , 2014-04-04, 02:38: The package has already been ported and bug filed with patch: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726402 which updates the symbols file to have 'arm64' and '!arm64' in the various arch-qualified symbols entries (which I think I do understand). However

grokking debian symbols files

2014-04-03 Thread Wookey
I have always been a bit vague about the workings of symbols files in packaging. I understand what it's supposed to do, but not how the mechanics work. I have a problem getting mozjs to build on arm64 which means someone needs to explain to me exactly what the contents of those files mean. The pa