Your message dated Sat, 11 May 2024 21:35:43 +0000 with message-id <e1s5unb-003gk5...@fasolo.debian.org> and subject line Bug#1070872: fixed in glibc 2.38-11 has caused the Debian Bug report #1070872, regarding libm.a lost fmod + fmodf on i386 + m68k 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.) -- 1070872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libc6-dev Version: 2.38-7 Severity: serious Tags: ftbfs Control: affects -1 src:zsh https://buildd.debian.org/status/logs.php?pkg=zsh&ver=5.9-6%2Bb1 ... gcc -static -o zsh main.o `cat stamp-modobjs` -lpcre2-8 -lgdbm -lcap -lncursesw -ltinfo -ltinfo -lrt -lm -lc ... ./obj-static/Src/../../Src/math.c:1260:(.text+0x1d8e): undefined reference to `fmod' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:228: zsh] Error 1 $ objdump -t /usr/lib/i386-linux-gnu/libm.a | grep fmod w_fmodl_compat.o: file format elf32-i386 w_fmod_compat.o: file format elf32-i386 w_fmodf_compat.o: file format elf32-i386 e_fmodl.o: file format elf32-i386 00000000 g F .text 00000013 __ieee754_fmodl w_fmodl.o: file format elf32-i386 00000000 g F .text 00000085 __fmodl 00000000 *UND* 00000000 __ieee754_fmodl 00000000 w F .text 00000085 fmodf64x 00000000 w F .text 00000085 fmodl e_fmod.o: file format elf32-i386 00000000 g F .text 00000013 __ieee754_fmod w_fmod.o: file format elf32-i386 e_fmodf.o: file format elf32-i386 00000000 g F .text 00000013 __ieee754_fmodf w_fmodf.o: file format elf32-i386 e_fmodf128.o: file format elf32-i386 00000000 g F .text 00000c9b __ieee754_fmodf128 00000000 *UND* 00000000 __ieee754_fmodf128 00000000 *UND* 00000000 __ieee754_fmodf128 w_fmodf128.o: file format elf32-i386 00000000 g F .text 00000237 __fmodf128 00000000 *UND* 00000000 __ieee754_fmodf128 00000000 w F .text 00000237 fmodf128 $ With 2.37-13 this is instead: $ objdump -t /usr/lib/i386-linux-gnu/libm.a | grep fmod w_fmodl_compat.o: file format elf32-i386 w_fmod_compat.o: file format elf32-i386 w_fmodf_compat.o: file format elf32-i386 e_fmodl.o: file format elf32-i386 00000000 g F .text 00000013 __ieee754_fmodl w_fmodl.o: file format elf32-i386 00000000 g F .text 00000085 __fmodl 00000000 *UND* 00000000 __ieee754_fmodl 00000000 w F .text 00000085 fmodf64x 00000000 w F .text 00000085 fmodl e_fmod.o: file format elf32-i386 00000000 g F .text 00000013 __ieee754_fmod w_fmod.o: file format elf32-i386 00000000 g F .text 0000006b __fmod 00000000 *UND* 00000000 __ieee754_fmod 00000000 w F .text 0000006b fmodf32x 00000000 w F .text 0000006b fmodf64 00000000 w F .text 0000006b fmod e_fmodf.o: file format elf32-i386 00000000 g F .text 00000013 __ieee754_fmodf w_fmodf.o: file format elf32-i386 00000000 g F .text 00000063 __fmodf 00000000 *UND* 00000000 __ieee754_fmodf 00000000 w F .text 00000063 fmodf32 00000000 w F .text 00000063 fmodf e_fmodf128.o: file format elf32-i386 00000000 g F .text 00000cc5 __ieee754_fmodf128 00000000 *UND* 00000000 __ieee754_fmodf128 00000000 *UND* 00000000 __ieee754_fmodf128 w_fmodf128.o: file format elf32-i386 00000000 g F .text 00000237 __fmodf128 00000000 *UND* 00000000 __ieee754_fmodf128 00000000 w F .text 00000237 fmodf128 $
--- End Message ---
--- Begin Message ---Source: glibc Source-Version: 2.38-11 Done: Aurelien Jarno <aure...@debian.org> We believe that the bug you reported is fixed in the latest version of glibc, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurelien Jarno <aure...@debian.org> (supplier of updated glibc 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: Sat, 11 May 2024 23:17:18 +0200 Source: glibc Architecture: source Version: 2.38-11 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers <debian-gl...@lists.debian.org> Changed-By: Aurelien Jarno <aure...@debian.org> Closes: 1070872 1070875 Changes: glibc (2.38-11) unstable; urgency=medium . [ Aurelien Jarno ] * debian/testsuite-xfail-debian.mk: ignore a few math failures due to GCC 13 on hppa. Closes: #1070875. * debian/patches/any/submitted-static-*.diff: add proposed patches to fix various missing math function in libm.a. Closes: #1070872. * debian/testsuite-xfail-debian.mk: mark tst-support_descriptors as XFAIL, due to sbuild bug #1070003. Checksums-Sha1: cb16f1fe7d3a90116921dfec258d9b1686b894d0 7535 glibc_2.38-11.dsc cc793377025830f66fb937ad2b6316f630c11bfc 429076 glibc_2.38-11.debian.tar.xz 2c283e082e8a33880c389204e658e0d97a5c5e6a 9945 glibc_2.38-11_source.buildinfo Checksums-Sha256: e3673f0f0f7371335ed6d9ac1221d33c62604af8171686282a481da8e7a4aa80 7535 glibc_2.38-11.dsc 336d41903e4c2b12a71bb646b68c9c295c980a4a7f22a43da70aadbcfa80a825 429076 glibc_2.38-11.debian.tar.xz c8f760e85c32c0d5ec7d97431213e67682fc285dbc0d58aaf2812482746624e6 9945 glibc_2.38-11_source.buildinfo Files: a811ef2a956ad933930fc7eebfeff191 7535 libs required glibc_2.38-11.dsc f28787622972a7abf9aaaa410e185856 429076 libs required glibc_2.38-11.debian.tar.xz 8107fceff977128d94b922275a6a3f3a 9945 libs required glibc_2.38-11_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmY/4XoACgkQE4jA+Jno M2uXFg//Yje3QGX/t1bfLHjnkWHCdUm+YttbET18bsbObuT4jdGgv4aDUgEmhXB3 ncB+BAJI6mJiaRjLu6E9eaHlVyMhzpMSVlJ40O12XVo45W3gxtjZ5RxrO8HEso4b 8HFWwtpt6wa2VnQqmneaoNdHA/ZYpPI9dDvELlanvvIc7u6pzQ7606A3oTd+O/Aw RnXaRWrREPKi305+1bEzShymgcM+uDxlQ1w6PhXiEPlbROg6Qg+Oz8CbJHM9UAMJ T984QNwTfJRSLtkSmxl1bv8dOoaNJop8qiXdlEGgavs87cEACB7e5RObzZNzNTXl f09sHzdc1NIpjuNXGUYr5V7RcKl0A59rvk1mWHcR3PHPtbvKUHpRJumhxmzWioDc h6pNxj0NnUomWNNgvBnhzykpxzSGkWAtrqi6lEdh8HQMt5FsFwNKOZaj7ytRYjNO a3h0FdD4lGKupJKe2nwgpurT91Oc/C0TwobYvxuyrPMEgp7pkzhQrc5UXvH4kWMA tih7Da6qhHZk/xjxi6GjUL65X5lQM7gxSOxeuWzC2K1y4evxNH9Qi1vp6HUZGn75 9hrCjeYKgUawGVZZIX/10PDzZEcCY5xfhU+kylunjp7QtgOPxmmmYLqWQxndV7MN 4M85cYWE1F/5j44i8L8Jgpk4CQnD1epL7roHi5zBuBJO3Ai5Bo0= =o9yh -----END PGP SIGNATURE-----pgpMqjLX0WvKI.pgp
Description: PGP signature
--- End Message ---