Processed: Re: Bug#1061370: gcc-14 ftbfs on armel
Processing control commands: > affects -1 systemd Bug #1061370 [src:gcc-14] gcc-14 ftbfs on armel Added indication that 1061370 affects systemd -- 1061370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061370: gcc-14 ftbfs on armel
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 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 bug numbers, commits, and so > > forth. > > > > More in general though there have been several important issues with > > armel lately, not least the fact that there is very little hardware > > still supported by the kernel (essentially just the Raspberry Pi Zero > > and 1 AIUI [0]). It seems to me that the time has come to seriously > > consider whether supporting armel as an official port still makes sense. > > > > [0] https://salsa.debian.org/kernel-team/linux/-/commit/b53e2d881063b060934bee3da9378da3b5b5387b > > > > disabled ada, now ftbs with go. > > if you care about the Pi Zero, then please get involved upstream. > Listening to ARM guys, armv5t doesn't seem to raise any interest these days. > > Also having LLVM build failures, still targeting armv4t didn't raise any > attention to the Debian armel porters. > > So let's just say there is no man power to address issues, and probably > also lack of interest. 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 systemd-cryptsetup.p/src_cryptsetup_cryptsetup.c.o systemd-cryptsetup.p/src_cryptsetup_cryptsetup-pkcs11.c.o systemd-cryptsetup.p/src_cryptsetup_cryptsetup-tpm2.c.o -Wl,--as-needed -Wl,--no-undefined -fstack-protector '-Wl,-rpath,$ORIGIN/src/shared:' -Wl,-rpath-link,/home/bluca/systemd/foo/src/shared -Wl,--start-group src/shared/libsystemd-shared-255.so /lib/arm-linux-gnueabi/libcryptsetup.so /usr/lib/arm-linux-gnueabi/libssl.so /usr/lib/arm-linux-gnueabi/libcrypto.so -Wl,--end-group -Wl,--fatal-warnings -Wl,-z,now -Wl,-z,relro -Wl,--warn-common /usr/bin/ld: /lib/arm-linux-gnueabi/libatomic.so.1: undefined reference to `libat_test_and_set_1_i2' collect2: error: ld returned 1 exit status 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 -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#1061370: gcc-14 ftbfs on armel
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 > systemd-cryptsetup.p/src_cryptsetup_cryptsetup.c.o > systemd-cryptsetup.p/src_cryptsetup_cryptsetup-pkcs11.c.o > systemd-cryptsetup.p/src_cryptsetup_cryptsetup-tpm2.c.o -Wl,--as-needed > -Wl,--no-undefined -fstack-protector > '-Wl,-rpath,$ORIGIN/src/shared:' > -Wl,-rpath-link,/home/bluca/systemd/foo/src/shared -Wl,--start-group > src/shared/libsystemd-shared-255.so /lib/arm-linux-gnueabi/libcryptsetup.so > /usr/lib/arm-linux-gnueabi/libssl.so /usr/lib/arm-linux-gnueabi/libcrypto.so > -Wl,--end-group -Wl,--fatal-warnings -Wl,-z,now -Wl,-z,relro -Wl,--warn-common > /usr/bin/ld: /lib/arm-linux-gnueabi/libatomic.so.1: undefined reference to > `libat_test_and_set_1_i2' > collect2: error: ld returned 1 exit status >From the build logs at [1] it seems that a mix of GCC 13 and 14 packages was used, is this expected? Toolchain package versions: binutils_2.41.90.20240122-1 dpkg-dev_1.22.4 g++-13_13.2.0-10 gcc-13_13.2.0-10 libc6-dev_2.37-14 libstdc++-13-dev_13.2.0-10 libstdc++6_14-20240127-1 linux-libc-dev_6.6.13-1 [1] https://buildd.debian.org/status/fetch.php?pkg=systemd&arch=armel&ver=255.3-2&stamp=1706528229&raw=0
Bug#1061370: gcc-14 ftbfs on armel
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 > > systemd-cryptsetup.p/src_cryptsetup_cryptsetup-keyfile.c.o > > systemd-cryptsetup.p/src_cryptsetup_cryptsetup.c.o > > systemd-cryptsetup.p/src_cryptsetup_cryptsetup-pkcs11.c.o > > systemd-cryptsetup.p/src_cryptsetup_cryptsetup-tpm2.c.o -Wl,--as-needed > > -Wl,--no-undefined -fstack-protector > > '-Wl,-rpath,$ORIGIN/src/shared:' > > -Wl,-rpath-link,/home/bluca/systemd/foo/src/shared -Wl,--start-group > > src/shared/libsystemd-shared-255.so /lib/arm-linux-gnueabi/libcryptsetup.so > > /usr/lib/arm-linux-gnueabi/libssl.so > > /usr/lib/arm-linux-gnueabi/libcrypto.so -Wl,--end-group > > -Wl,--fatal-warnings -Wl,-z,now -Wl,-z,relro -Wl,--warn-common > > /usr/bin/ld: /lib/arm-linux-gnueabi/libatomic.so.1: undefined reference to > > `libat_test_and_set_1_i2' > > collect2: error: ld returned 1 exit status > > From the build logs at [1] it seems that a mix of GCC 13 and 14 packages > was used, is this expected? > > Toolchain package versions: binutils_2.41.90.20240122-1 dpkg-dev_1.22.4 > g++-13_13.2.0-10 gcc-13_13.2.0-10 libc6-dev_2.37-14 > libstdc++-13-dev_13.2.0-10 libstdc++6_14-20240127-1 linux-libc-dev_6.6.13-1 > > [1] > https://buildd.debian.org/status/fetch.php?pkg=systemd&arch=armel&ver=255.3-2&stamp=1706528229&raw=0 The package name is 'libatomic1' and it's not versioned after the GCC major version like the rest, so it seems to be all working as intended.
Bug#1061370: gcc-14 ftbfs on armel
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 passing the newly built debs as --extra-package - which resulted in libatomic1 and a few others being upgraded. Unfortunately systemd still failed building, see full logs at: https://people.debian.org/~ema/systemd_255.3-1_armel.build diff -Nru gcc-14-14-20240127/debian/changelog gcc-14-14-20240127/debian/changelog --- gcc-14-14-20240127/debian/changelog 2024-01-27 09:51:04.0 +0100 +++ gcc-14-14-20240127/debian/changelog 2024-01-29 19:55:54.0 +0100 @@ -1,3 +1,9 @@ +gcc-14 (14-20240127-1.1) unstable; urgency=medium + + * Add upstream patch libatomic-armel.diff. + + -- Emanuele Rocca Mon, 29 Jan 2024 19:55:54 +0100 + gcc-14 (14-20240127-1) unstable; urgency=medium * Snapshot, taken from the trunk 20240127. diff -Nru gcc-14-14-20240127/debian/patches/libatomic-armel.diff gcc-14-14-20240127/debian/patches/libatomic-armel.diff --- gcc-14-14-20240127/debian/patches/libatomic-armel.diff 1970-01-01 01:00:00.0 +0100 +++ gcc-14-14-20240127/debian/patches/libatomic-armel.diff 2024-01-29 19:55:54.0 +0100 @@ -0,0 +1,12 @@ +Index: gcc-14-14-20240127/src/libatomic/Makefile.am +=== +--- gcc-14-14-20240127.orig/src/libatomic/Makefile.am gcc-14-14-20240127/src/libatomic/Makefile.am +@@ -139,6 +139,7 @@ if ARCH_ARM_LINUX + IFUNC_OPTIONS = -march=armv7-a+fp -DHAVE_KERNEL64 + libatomic_la_LIBADD += $(foreach s,$(SIZES),$(addsuffix _$(s)_1_.lo,$(SIZEOBJS))) + libatomic_la_LIBADD += $(addsuffix _8_2_.lo,$(SIZEOBJS)) ++libatomic_la_LIBADD += tas_1_2_.lo + endif + if ARCH_I386 + IFUNC_OPTIONS = -march=i586 diff -Nru gcc-14-14-20240127/debian/rules.patch gcc-14-14-20240127/debian/rules.patch --- gcc-14-14-20240127/debian/rules.patch 2024-01-26 12:31:20.0 +0100 +++ gcc-14-14-20240127/debian/rules.patch 2024-01-29 19:55:54.0 +0100 @@ -232,6 +232,7 @@ endif debian_patches += go-testsuite +debian_patches += libatomic-armel # don't remove, this is regularly overwritten, see PR sanitizer/63958. #debian_patches += libasan-sparc
Bug#1061370: gcc-14 ftbfs on armel
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 gcc-14 with the attached debdiff, and then tried building > systemd passing the newly built debs as --extra-package - which resulted > in libatomic1 and a few others being upgraded. Unfortunately systemd > still failed building, see full logs at: > https://people.debian.org/~ema/systemd_255.3-1_armel.build 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': Run-time dependency libcryptsetup found: YES 2.6.1 Checking for function "crypt_set_metadata_size" with dependency libcryptsetup: NO Checking for function "crypt_activate_by_signed_key" with dependency libcryptsetup: NO Checking for function "crypt_token_max" with dependency libcryptsetup: NO Checking for function "crypt_reencrypt_init_by_passphrase" with dependency libcryptsetup: NO Checking for function "crypt_reencrypt" with dependency libcryptsetup: NO Checking for function "crypt_set_data_offset" with dependency libcryptsetup: NO Checking for function "crypt_activate_by_token_pin" with dependency libcryptsetup: NO
Bug#1061370: gcc-14 ftbfs on armel
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)) +libatomic_la_LIBADD += tas_1_2_.lo An earlier patch looked like this instead: libatomic_la_LIBADD += $(addsuffix _8_2_.lo,$(SIZEOBJS)) +libatomic_la_LIBADD += $(addsuffix _1_2_.lo,$(SIZEOBJS)) Trying the latter now. Note that this issue is making loads of packages fail, not just systemd.
Processed: Re: Bug#1061370: gcc-14 ftbfs on armel
Processing control commands: > tags -1 patch Bug #1061370 [src:gcc-14] gcc-14 ftbfs on armel Added tag(s) patch. -- 1061370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061370: gcc-14 ftbfs on armel
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 an updated Makefile.in. I updated it with the following command from within src/libatomic: AUTOM4TE=/usr/bin/autom4te2.69 autoreconf And added both Makefile.am and Makefile.in to the patch, see attached debdiff. With these changes, libat_test_and_set_1_i2 is not anymore listed among the undefined symbols in the output of objdump -T, and systemd builds fine. I haven't tried to re-enable ada and gccgo, but they should hopefully build again now too. diff -Nru gcc-14-14-20240127/debian/changelog gcc-14-14-20240127/debian/changelog --- gcc-14-14-20240127/debian/changelog 2024-01-27 09:51:04.0 +0100 +++ gcc-14-14-20240127/debian/changelog 2024-01-29 19:55:54.0 +0100 @@ -1,3 +1,9 @@ +gcc-14 (14-20240127-1.1) unstable; urgency=medium + + * Add upstream patch libatomic-armel.diff. Closes: #1061370. + + -- Emanuele Rocca Mon, 29 Jan 2024 19:55:54 +0100 + gcc-14 (14-20240127-1) unstable; urgency=medium * Snapshot, taken from the trunk 20240127. diff -Nru gcc-14-14-20240127/debian/patches/libatomic-armel.diff gcc-14-14-20240127/debian/patches/libatomic-armel.diff --- gcc-14-14-20240127/debian/patches/libatomic-armel.diff 1970-01-01 01:00:00.0 +0100 +++ gcc-14-14-20240127/debian/patches/libatomic-armel.diff 2024-01-29 19:55:54.0 +0100 @@ -0,0 +1,209 @@ +Index: gcc-14-14-20240127/src/libatomic/Makefile.am +=== +--- gcc-14-14-20240127.orig/src/libatomic/Makefile.am gcc-14-14-20240127/src/libatomic/Makefile.am +@@ -139,6 +139,7 @@ if ARCH_ARM_LINUX + IFUNC_OPTIONS = -march=armv7-a+fp -DHAVE_KERNEL64 + libatomic_la_LIBADD += $(foreach s,$(SIZES),$(addsuffix _$(s)_1_.lo,$(SIZEOBJS))) + libatomic_la_LIBADD += $(addsuffix _8_2_.lo,$(SIZEOBJS)) ++libatomic_la_LIBADD += tas_1_2_.lo + endif + if ARCH_I386 + IFUNC_OPTIONS = -march=i586 +Index: gcc-14-14-20240127/src/libatomic/Makefile.in +=== +--- gcc-14-14-20240127.orig/src/libatomic/Makefile.in gcc-14-14-20240127/src/libatomic/Makefile.in +@@ -1,7 +1,7 @@ +-# Makefile.in generated by automake 1.15.1 from Makefile.am. ++# Makefile.in generated by automake 1.16.5 from Makefile.am. + # @configure_input@ + +-# Copyright (C) 1994-2017 Free Software Foundation, Inc. ++# Copyright (C) 1994-2021 Free Software Foundation, Inc. + + # This Makefile.in is free software; the Free Software Foundation + # gives unlimited permission to copy and/or distribute it, +@@ -95,7 +95,8 @@ target_triplet = @target@ + @ARCH_ARM_LINUX_TRUE@@HAVE_IFUNC_TRUE@ s,$(SIZES),$(addsuffix \ + @ARCH_ARM_LINUX_TRUE@@HAVE_IFUNC_TRUE@ _$(s)_1_.lo,$(SIZEOBJS))) \ + @ARCH_ARM_LINUX_TRUE@@HAVE_IFUNC_TRUE@ $(addsuffix \ +-@ARCH_ARM_LINUX_TRUE@@HAVE_IFUNC_TRUE@ _8_2_.lo,$(SIZEOBJS)) ++@ARCH_ARM_LINUX_TRUE@@HAVE_IFUNC_TRUE@ _8_2_.lo,$(SIZEOBJS)) \ ++@ARCH_ARM_LINUX_TRUE@@HAVE_IFUNC_TRUE@ tas_1_2_.lo + @ARCH_I386_TRUE@@HAVE_IFUNC_TRUE@am__append_4 = $(addsuffix _8_1_.lo,$(SIZEOBJS)) + @ARCH_X86_64_TRUE@@HAVE_IFUNC_TRUE@am__append_5 = $(addsuffix _16_1_.lo,$(SIZEOBJS)) \ + @ARCH_X86_64_TRUE@@HAVE_IFUNC_TRUE@ $(addsuffix _16_2_.lo,$(SIZEOBJS)) +@@ -187,11 +188,16 @@ am__v_at_ = $(am__v_at_@AM_DEFAULT_V@) + am__v_at_0 = @ + am__v_at_1 = + depcomp = $(SHELL) $(top_srcdir)/../depcomp +-am__depfiles_maybe = depfiles ++am__maybe_remake_depfiles = depfiles ++am__depfiles_remade = ./$(DEPDIR)/atomic_16.Plo ./$(DEPDIR)/fence.Plo \ ++ ./$(DEPDIR)/fenv.Plo ./$(DEPDIR)/flag.Plo ./$(DEPDIR)/gcas.Plo \ ++ ./$(DEPDIR)/gexch.Plo ./$(DEPDIR)/glfree.Plo \ ++ ./$(DEPDIR)/gload.Plo ./$(DEPDIR)/gstore.Plo \ ++ ./$(DEPDIR)/init.Plo ./$(DEPDIR)/lock.Plo + am__mv = mv -f + CPPASCOMPILE = $(CCAS) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) \ + $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CCASFLAGS) $(CCASFLAGS) +-LTCPPASCOMPILE = $(LIBTOOL) $(AM_V_lt) $(AM_LIBTOOLFLAGS) \ ++LTCPPASCOMPILE = $(LIBTOOL) $(AM_V_lt) --tag=CC $(AM_LIBTOOLFLAGS) \ + $(LIBTOOLFLAGS) --mode=compile $(CCAS) $(DEFS) \ + $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) \ + $(AM_CCASFLAGS) $(CCASFLAGS) +@@ -240,8 +246,8 @@ am__recursive_targets = \ + $(am__extra_recursive_targets) + AM_RECURSIVE_TARGETS = $(am__recursive_targets:-recursive=) TAGS CTAGS \ + cscope +-am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) \ +- $(LISP)auto-config.h.in ++am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) $(LISP) \ ++ auto-config.h.in + # Read a list of newline-separated strings from the standard input, + # and print each of them once, without duplicates. Input order is + # *not* preserved. +@@ -258,9 +264,6 @@ am__define_uniq_tagged_files = \ + unique=`for i in $$list; do \ + if t
Processing of gcc-14_14-20240130-1_source.changes
gcc-14_14-20240130-1_source.changes uploaded successfully to localhost along with the files: gcc-14_14-20240130-1.dsc gcc-14_14-20240130.orig.tar.gz gcc-14_14-20240130-1.debian.tar.xz gcc-14_14-20240130-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1061647: marked as done (libgccjit-14-doc: missing Breaks+Replaces: libgccjit-13-doc (and maybe more old versions))
Your message dated Tue, 30 Jan 2024 07:49:12 +
with message-id
and subject line Bug#1061647: fixed in gcc-14 14-20240130-1
has caused the Debian Bug report #1061647,
regarding libgccjit-14-doc: missing Breaks+Replaces: libgccjit-13-doc (and
maybe more old versions)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1061647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgccjit-14-doc
Version: 14-20240127-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../libgccjit-14-doc_14-20240127-1_all.deb ...
Unpacking libgccjit-14-doc (14-20240127-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libgccjit-14-doc_14-20240127-1_all.deb (--unpack):
trying to overwrite '/usr/share/info/libgccjit-figures/factorial.png', which
is also in package libgccjit-13-doc 13.2.0-10
Errors were encountered while processing:
/var/cache/apt/archives/libgccjit-14-doc_14-20240127-1_all.deb
The files in conflict are
usr/share/info/libgccjit-figures/factorial.png
usr/share/info/libgccjit-figures/factorial1.png
usr/share/info/libgccjit-figures/sum-of-squares.png
usr/share/info/libgccjit-figures/sum-of-squares1.png
usr/share/info/libgccjit.info.gz
cheers,
Andreas
libgccjit-13-doc=13.2.0-10_libgccjit-14-doc=14-20240127-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gcc-14
Source-Version: 14-20240130-1
Done: Matthias Klose
We believe that the bug you reported is fixed in the latest version of
gcc-14, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose (supplier of updated gcc-14 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 30 Jan 2024 08:09:50 +0100
Source: gcc-14
Architecture: source
Version: 14-20240130-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GCC Maintainers
Changed-By: Matthias Klose
Closes: 1061647 1061670
Changes:
gcc-14 (14-20240130-1) experimental; urgency=medium
.
* Snapshot, taken from the trunk 20240130.
.
[ Matthias Klose ]
* Fix and add dependencies for -for-build and -for-host packages.
* Add conflict to libgccjit-13-doc. Closes: #1061647.
* Fix some -for-{build,host} package descriptions. Closes: #1061670.
* Correct conflicts with old gnat-N versions. Addresses: #1061648.
* Apply proposed patch for PR target/113336.
* Build again gnat and gcc on armel.
.
[ Aurelien Jarno ]
* Update libasan8 symbols for riscv64.
* Update liblsan0 symbols for riscv64.
Checksums-Sha1:
9dfe7ab575a90196420a8b470057ee2487340064 46482 gcc-14_14-20240130-1.dsc
fa10cdd3c65a99b7cbee5b6d2d142f387b563067 89512649
gcc-14_14-20240130.orig.tar.gz
ccc2423907a458302a631781fac8ae92e2350a1c 535592
gcc-14_14-20240130-1.debian.tar.xz
4581325df2d888b84f87134cd4df9265a7a4e67e 9752
gcc-14_14-20240130-1_source.buildinfo
Checksums-Sha256:
b990070ac67da4878739846dc50891fb6d858801fe628abbf0c563b38c0f51c5 46482
gcc-14_14-20240130-1.dsc
e85640452418555673055db6c3b17c87f8fe3d01e92b7dbbba7adf8dfbc3cd3d 89512649
gcc-14_14-20240130.orig.tar.gz
0e8a1ab7522be458b2bd391fd47689f5a84ca08366f1ef820c1c41c8de2aaa05 535592
gcc-14_14-20240130-1.debian.tar.xz
41e6d474e3712cc821b4b493738b96ec7e597cd22a2eeded88f9c332d634b756 9752
gcc-14_14-20240130-1_source.buildinfo
Files:
69d3ac0bfd487a4aa1d41ef30b229489 46482 devel optional gcc-14_14-20240130-1.dsc
20246ef2ec6238be80e3f0f76a9b2916 89512649 devel optional
gcc-14_14-20240130.orig.tar.gz
4ab8838f16d4705f2768d842c218e7e8 535592 devel optional
Bug#1061670: marked as done (gcc-14: long package description of {cpp,g++}-14-for-{build,host} has literal arch_gnu)
Your message dated Tue, 30 Jan 2024 07:49:12 +
with message-id
and subject line Bug#1061670: fixed in gcc-14 14-20240130-1
has caused the Debian Bug report #1061670,
regarding gcc-14: long package description of {cpp,g++}-14-for-{build,host} has
literal arch_gnu
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1061670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-14
Severity: minor
X-Debbugs-Cc: dfo...@gmail.com
Dear maintainers,
the long package description of
cpp-14-for-build cpp-14-for-host g++-14-for-build g++-14-for-host
contains the string "arch_gnu" instead of "the build" or "the host".
Eg:
...the preprocessor configured for arch_gnu architecture...
...This package contains C++ cross-compiler for arch_gnu architecture...
The short package descriptions contain the correct text.
greetings,
Daniele
--- End Message ---
--- Begin Message ---
Source: gcc-14
Source-Version: 14-20240130-1
Done: Matthias Klose
We believe that the bug you reported is fixed in the latest version of
gcc-14, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose (supplier of updated gcc-14 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 30 Jan 2024 08:09:50 +0100
Source: gcc-14
Architecture: source
Version: 14-20240130-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GCC Maintainers
Changed-By: Matthias Klose
Closes: 1061647 1061670
Changes:
gcc-14 (14-20240130-1) experimental; urgency=medium
.
* Snapshot, taken from the trunk 20240130.
.
[ Matthias Klose ]
* Fix and add dependencies for -for-build and -for-host packages.
* Add conflict to libgccjit-13-doc. Closes: #1061647.
* Fix some -for-{build,host} package descriptions. Closes: #1061670.
* Correct conflicts with old gnat-N versions. Addresses: #1061648.
* Apply proposed patch for PR target/113336.
* Build again gnat and gcc on armel.
.
[ Aurelien Jarno ]
* Update libasan8 symbols for riscv64.
* Update liblsan0 symbols for riscv64.
Checksums-Sha1:
9dfe7ab575a90196420a8b470057ee2487340064 46482 gcc-14_14-20240130-1.dsc
fa10cdd3c65a99b7cbee5b6d2d142f387b563067 89512649
gcc-14_14-20240130.orig.tar.gz
ccc2423907a458302a631781fac8ae92e2350a1c 535592
gcc-14_14-20240130-1.debian.tar.xz
4581325df2d888b84f87134cd4df9265a7a4e67e 9752
gcc-14_14-20240130-1_source.buildinfo
Checksums-Sha256:
b990070ac67da4878739846dc50891fb6d858801fe628abbf0c563b38c0f51c5 46482
gcc-14_14-20240130-1.dsc
e85640452418555673055db6c3b17c87f8fe3d01e92b7dbbba7adf8dfbc3cd3d 89512649
gcc-14_14-20240130.orig.tar.gz
0e8a1ab7522be458b2bd391fd47689f5a84ca08366f1ef820c1c41c8de2aaa05 535592
gcc-14_14-20240130-1.debian.tar.xz
41e6d474e3712cc821b4b493738b96ec7e597cd22a2eeded88f9c332d634b756 9752
gcc-14_14-20240130-1_source.buildinfo
Files:
69d3ac0bfd487a4aa1d41ef30b229489 46482 devel optional gcc-14_14-20240130-1.dsc
20246ef2ec6238be80e3f0f76a9b2916 89512649 devel optional
gcc-14_14-20240130.orig.tar.gz
4ab8838f16d4705f2768d842c218e7e8 535592 devel optional
gcc-14_14-20240130-1.debian.tar.xz
2ce43b8a528a9eb4639c1f790de53443 9752 devel optional
gcc-14_14-20240130-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmW4o14QHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9Y4OD/4yvfnvE16qfXJSq3buHbPOhKUYjkmq093Z
uBeHAHIKsrDCJ+9vNSGxTFs3Q8Jk3a1S483NW0v6wPPG15zdYL+5A4PNLYpYUjKv
2ES7tWL2O2fY7IMioEXPg3rjF/8WxLww0QmFBmAvogRraJ7cxdBg+3qMWWHjVeqW
jDugNhYPcGO605h4ZxN4JWC4wkRfjJFmwREnuFRdbZYjFruOqlJsrj3ennKb3FEs
3tBBKEVA63CylI4EMgiNJBLvwRh/w5fPa5sqZKznqqd5b9iBS0uEME2ZGf1bd9PX
6m/BjLdB38PTqOueBkR5HqVENBpvrfon3GT3K7BXMqWAy/SwVmpt0niV/C9Swq89
stqHdTphFhF49MIwIsOKwUstzoLRCBocec0DcPkURZnRW1n6VrXYquEF2jBgvGZq
DTPsn115aBypmvpOWniUfZ56jBC0yn+0VuZ/2DHNMTy1caAokABrfWVCDkBkDwGy
hAGZAJZGxXYvOKuSjjj3LSlWyPL7qQQh6yYerXnZ9LsX8YwaXMeWJkLgn+emKfPe
1IkaL1kRbqbcurRKUGqwyiqXskdXT/6N/BYli6QUvfrcJeTFJaoloJLA10AZ3ze/
0X0mye3DgssMQ1KVOlnbAozBwQEQ0KCf/z7IY1kyzIlKfuXQV0vZz8iuPyMyUC0C
