On 03.12.2016 11:58, Santiago Vila wrote:
> Sorry, did not see the part about internal compiler error in the buld log
> itself. Still amazed that you can be so sure that it's hardware related when
> he is using virtual machines.
The message reads:
The bug is not reproducible, so it is likely
Sorry, did not see the part about internal compiler error in the buld log
itself. Still amazed that you can be so sure that it's hardware related when he
is using virtual machines.
Thanks.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
On 03.12.2016 10:41, Santiago Vila wrote:
> On Sat, Dec 03, 2016 at 10:08:33AM +0100, Lucas Nussbaum wrote:
>
>> Just for the record: I can still reproduce this failure.
>
> Then, IMHO, you should reopen the bug.
>
>
> I bet it's a Makefile bug related to parallel building, because my
> autobui
On Sat, Dec 03, 2016 at 10:08:33AM +0100, Lucas Nussbaum wrote:
> Just for the record: I can still reproduce this failure.
Then, IMHO, you should reopen the bug.
I bet it's a Makefile bug related to parallel building, because my
autobuilders are single-CPU and I also have this in my .sbuilrc fi
Hi,
Just for the record: I can still reproduce this failure.
Lucas
On Wed, Nov 23, 2016 at 12:26:18AM +0100, Matthias Klose wrote:
> > What would be the right package for a bug in one of GCC Makefiles, then?
> >
> > What if Lucas was able to reproduce this in two different machines and
> > the failure and the error message was the same? Would you discard
> > "fi
On 21.11.2016 13:09, Santiago Vila wrote:
> On Sat, 19 Nov 2016, Matthias Klose wrote:
>
>>> It's unlikely a hardware problem because the build was made in a
>>> virtual machine and the build was tried twice. This is written
>>> in the bug report itself.
>>>
>>> This is a lot more likely to be a b
On Sat, 19 Nov 2016, Matthias Klose wrote:
> > It's unlikely a hardware problem because the build was made in a
> > virtual machine and the build was tried twice. This is written
> > in the bug report itself.
> >
> > This is a lot more likely to be a bug which happens randomly,
> > for example, a
On 19.11.2016 22:54, Santiago Vila wrote:
> On Sat, 19 Nov 2016, Matthias Klose wrote:
>
>> On 19.11.2016 07:40, Lucas Nussbaum wrote:
>>> Source: gcc-5
>>> Version: 5.4.1-3
>>> Severity: serious
>>> Tags: stretch sid
>>> User: debian...@lists.debian.org
>>> Usertags: qa-ftbfs-20161118 qa-ftbfs
>>
On Sat, 19 Nov 2016, Matthias Klose wrote:
> On 19.11.2016 07:40, Lucas Nussbaum wrote:
> > Source: gcc-5
> > Version: 5.4.1-3
> > Severity: serious
> > Tags: stretch sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20161118 qa-ftbfs
> > Justification: FTBFS on amd64
> >
> > Hi,
>
Source: gcc-5
Version: 5.4.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> /tmp/ccAZve4U.o:
11 matches
Mail list logo
