On 17/03/15 08:09, Tomasz Buchert wrote:
Hi,
[...]
It turns out that the version 0.1.41-2 had *no* symbols file and for
all I know, it wouldn't build on some archs just as 0.1.41-3. I
decided to drop symbols file altogether since making it work with all
architecture/g++/STL details is madness.
Hi,
Guillem in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780489
noticed that some symbols indeed changed from unsigned long to
unsigned int. It is because size_t resolves to unsigned int instead
of unsigned long as before. So it is rather a toolchain change that
makes size_t defined in a
On 16/03/15 15:49, John Paul Adrian Glaubitz wrote:
Source: verbiste
Version: 0.1.41-3
Severity: serious
Justification: FTBFS on release architecture leaves package out-of-date
Hello!
Your package currently fails to build on various (release) architectures since
the symbols file is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/16/2015 04:42 PM, Tomasz Buchert wrote:
Indeed, you could be right. I just checked the build log for
verbiste_0.1.41-2 on sh4, for example, and the buildd was,
indeed, using dpkg_1.17.23 that time while it was using 1.17.24
for the last
Source: verbiste
Version: 0.1.41-3
Severity: serious
Justification: FTBFS on release architecture leaves package out-of-date
Hello!
Your package currently fails to build on various (release) architectures since
the symbols file is outdated and needs to be updated using the diff output
generated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Tomasz!
On 03/16/2015 04:14 PM, Tomasz Buchert wrote:
I don't think it is the case. It seems to me (although I may be
wrong) that dpkg-gensymbols does not demangle C++ symbols properly.
I reported a bug yesterday:
Control: block -1 by 780489
On 16/03/15 16:24, John Paul Adrian Glaubitz wrote:
Hi Tomasz!
On 03/16/2015 04:14 PM, Tomasz Buchert wrote:
I don't think it is the case. It seems to me (although I may be
wrong) that dpkg-gensymbols does not demangle C++ symbols properly.
I reported a bug
7 matches
Mail list logo
