On Fri, Jun 27, 2014 at 10:06 AM, Lisandro Damián Nicanor Pérez Meyer
wrote:
> On Friday 27 June 2014 09:32:59 Yunqiang Su wrote:
> [snip] > Ah, that's a good workaround, thanks!
>>
>> I noticed that your new upload ftbfs on mips64el again.
>> I think that we should make sure that the packages bui
On Friday 27 June 2014 09:32:59 Yunqiang Su wrote:
[snip] > Ah, that's a good workaround, thanks!
>
> I noticed that your new upload ftbfs on mips64el again.
> I think that we should make sure that the packages build successfully on
> any archs, so we can get the full symbols list on all of these
On Thu, Jun 26, 2014 at 8:50 PM, Lisandro Damián Nicanor Pérez Meyer
wrote:
> On Thursday 26 June 2014 12:45:51 Yunqiang Su wrote:
>> On Thu, Jun 26, 2014 at 12:35 PM, Lisandro Damián Nicanor Pérez
>>
>> wrote:
>> > Note: I'm sending yuou a copy because I mistakenly sent it to the original
>> > b
On Thursday 26 June 2014 12:45:51 Yunqiang Su wrote:
> On Thu, Jun 26, 2014 at 12:35 PM, Lisandro Damián Nicanor Pérez
>
> wrote:
> > Note: I'm sending yuou a copy because I mistakenly sent it to the original
> > bug reporter.
> >
> > On Thursday 26 June 2014 12:16:22 Yunqiang Su wrote:
> >> I r
On Thu, Jun 26, 2014 at 12:35 PM, Lisandro Damián Nicanor Pérez
wrote:
> Note: I'm sending yuou a copy because I mistakenly sent it to the original bug
> reporter.
>
> On Thursday 26 June 2014 12:16:22 Yunqiang Su wrote:
>> I refreshed this patch for mips64el
>
> Yunqiang: again, when we are talki
On Thursday 26 June 2014 12:16:22 Yunqiang Su wrote:
> I refreshed this patch for mips64el
Yunqiang: again, when we are talking about symbols files, a simple patch for
just one arch is not enough. The best way to solve this is to let mips64[el]
build logs be available trough debian-ports.
Kinds
With the attached patch, it can be built on mips64el, amd64, i386
without symbols warning.
On Tue, May 13, 2014 at 2:15 PM, Yunqiang Su wrote:
> The attachment is build log of mips64el.
>
> On mips64el, beside the same gcc-4.9 problem,
> there are some more problems.
>
> With this patch, I can bu
The attachment is build log of mips64el.
On mips64el, beside the same gcc-4.9 problem,
there are some more problems.
With this patch, I can build it on both amd64, mips64el, and i386.
While it still has some warnings.
I think that we should try to build it on experimental to determine the symbols
On Monday 05 May 2014 01:02:45 Matthias Klose wrote:
> Am 04.05.2014 19:36, schrieb Lisandro Damián Nicanor Pérez Meyer:
> > These bugs seems to be just symbols issues. If so, trying to fix them
> > while
>
> "just symbols" resulting in a build failure.
We might have a different understanding of
Am 04.05.2014 19:36, schrieb Lisandro Damián Nicanor Pérez Meyer:
> These bugs seems to be just symbols issues. If so, trying to fix them while
>
"just symbols" resulting in a build failure.
> gcc-4.9 is not the default compiler might be a call for problems and
> rebuilds.
>
> The best approach
These bugs seems to be just symbols issues. If so, trying to fix them while
gcc-4.9 is not the default compiler might be a call for problems and rebuilds.
The best approach here will be to check the packages once gcc-4.9 is the
default compiler letting the buildds FTBFS to get the symbols change
Package: src:qtdeclarative-opensource-src
Version: 5.2.1-5
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.9
The package fails to build in a test rebuild on at least amd64 with
gcc-4.9/g++-4.9, but succeeds to build with gcc-4.8/g++-4.8. The
severity of
12 matches
Mail list logo
