Control: tags -1 patch
On 2024-01-29 10:23, Emanuele Rocca wrote:
> Upstream proposed two patches though, the one I tried is:
>
> libatomic_la_LIBADD += $(addsuffix _8_2_.lo,$(SIZEOBJS))
> +libatomic_la_LIBADD += tas_1_2_.lo
The problem was not the patch, but the fact that it did not include
On 2024-01-29 09:04, Luca Boccassi wrote:
> Guess that doesn't solve it them, as it's the same problem, the meson
> build tests are failing, all of these should be 'YES':
Upstream proposed two patches though, the one I tried is:
libatomic_la_LIBADD += $(addsuffix _8_2_.lo,$(SIZEOBJS))
On Mon, 29 Jan 2024 at 20:36, Emanuele Rocca wrote:
>
> On 2024-01-29 01:33, Luca Boccassi wrote:
> > On the Bugzilla report a patch has been linked, would it be possible to
> > backport it, please?
> >
> > https://gcc.gnu.org/pipermail/gcc-patches/2024-January/644147.html
>
> I have rebuilt
On 2024-01-29 01:33, Luca Boccassi wrote:
> On the Bugzilla report a patch has been linked, would it be possible to
> backport it, please?
>
> https://gcc.gnu.org/pipermail/gcc-patches/2024-January/644147.html
I have rebuilt gcc-14 with the attached debdiff, and then tried building
systemd
On Mon, 29 Jan 2024 at 16:38, Emanuele Rocca wrote:
>
> Hi Luca,
>
> On 2024-01-29 01:33, Luca Boccassi wrote:
> > This causes systemd to FTBFS on armel since the new upload of
> > libatomic-14. No other architecture is affected.
> >
> > cc -o systemd-cryptsetup
> >
Hi Luca,
On 2024-01-29 01:33, Luca Boccassi wrote:
> This causes systemd to FTBFS on armel since the new upload of
> libatomic-14. No other architecture is affected.
>
> cc -o systemd-cryptsetup
> systemd-cryptsetup.p/src_cryptsetup_cryptsetup-keyfile.c.o
>
Control: affects -1 systemd
On Fri, 26 Jan 2024 20:10:40 +0100 Matthias Klose
wrote:
> On 24.01.24 09:58, Emanuele Rocca wrote:
> > Hi Matthias,
> >
> > On 2024-01-23 09:01, Matthias Klose wrote:
> >> This is a long standing, re-occurring issue which never has been
> >> forwarded and committed
On 24.01.24 09:58, Emanuele Rocca wrote:
Hi Matthias,
On 2024-01-23 09:01, Matthias Klose wrote:
This is a long standing, re-occurring issue which never has been
forwarded and committed by the armel ports to GCC upstream.
You seem to be aware of previous occurrences of this issue. Please
Hi Matthias,
On 2024-01-23 09:01, Matthias Klose wrote:
> This is a long standing, re-occurring issue which never has been
> forwarded and committed by the armel ports to GCC upstream.
You seem to be aware of previous occurrences of this issue. Please share
the details you have available such as
On 23.01.24 15:56, Wookey wrote:
On 2024-01-23 09:01 +0100, Matthias Klose wrote:
Package: src:gcc-14
Version: 14-20240121-1
Severity: important
Tags: sid trixie ftbfs
X-Debbugs-CC: debian-...@lists.debian.org
gcc-14 ftbfs on armel. This is a long standing, re-occurring issue which
never has
On 2024-01-23 09:01 +0100, Matthias Klose wrote:
> Package: src:gcc-14
> Version: 14-20240121-1
> Severity: important
> Tags: sid trixie ftbfs
> X-Debbugs-CC: debian-...@lists.debian.org
>
> gcc-14 ftbfs on armel. This is a long standing, re-occurring issue which
> never has been forwarded and
Package: src:gcc-14
Version: 14-20240121-1
Severity: important
Tags: sid trixie ftbfs
X-Debbugs-CC: debian-...@lists.debian.org
gcc-14 ftbfs on armel. This is a long standing, re-occurring issue
which never has been forwarded and committed by the armel ports to GCC
upstream. Please do it.
12 matches
Mail list logo
