Hi,
On 13.10.23 18:55, Simon Richter wrote:
There are a few dependency rules in the file that seem to do the same
thing, but use the wrong target name, so they are ignored, and this
doesn't seem to be a complete set anyway. I'm trying with the same
addition of an order-only dependency that th
Hi,
On 10/13/23 03:03, Simon Richter wrote:
makes the problem reproducible even when building with -j2, and
regardless of whether building _all packages in the same build or not.
I'll check tomorrow about gcc 13 and if that also happens upstream.
gcc 13 is okay, because of 0bfc503c [1]. This
Hi,
On 10/12/23 19:14, Simon Richter wrote:
I cannot reproduce this, and I would rather not investigate time into
that. Please check if you see this with gcc-13 as well.
I suspect it's a missing dependency, so the failure is more dependent on
"number of threads", and that it succeeds for -b
Hi,
On 10/12/23 15:17, Matthias Klose wrote:
I cannot reproduce this, and I would rather not investigate time into
that. Please check if you see this with gcc-13 as well.
I suspect it's a missing dependency, so the failure is more dependent on
"number of threads", and that it succeeds for -b
I cannot reproduce this, and I would rather not investigate time into that.
Please check if you see this with gcc-13 as well.
On 06.10.23 09:49, Simon Richter wrote:
Package: gcc-12
Version: 12.3.0-9
Severity: normal
Tags: ftbfs
X-Debbugs-Cc: s...@debian.org
Hi,
I just built arch:all and arc
Package: gcc-12
Version: 12.3.0-9
Severity: normal
Tags: ftbfs
X-Debbugs-Cc: s...@debian.org
Hi,
I just built arch:all and arch:amd64 packages separately in pbuilder,
and got a reproducible build failure while building amd64 with
--binary-arch. Normal severity because building both arch-dependent
6 matches
Mail list logo
