Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #409476 > unrolled thread

Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation

Back to article view | Back to linux.debian.bugs.rc

Contents

  Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation Christian Marillat <marillat@debian.org> - 2026-01-19 12:00 +0100
    Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation Matthias Klose <doko@debian.org> - 2026-01-19 12:10 +0100
      Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation Christian Marillat <marillat@debian.org> - 2026-01-19 12:50 +0100
        Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation Matthias Klose <doko@debian.org> - 2026-01-19 13:20 +0100
    Processed (with 1 error): Re: Bug#1125944: binutils-x86-64-linux-gnu:  input SFrame sections with different format versions prevent .sframe  generation "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-01-19 13:20 +0100
    Bug#1125944: marked as done (binutils-x86-64-linux-gnu: input  SFrame sections with different format versions prevent .sframe generation) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-01-19 20:40 +0100
    Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation Aurelien Jarno <aurel32@debian.org> - 2026-01-19 20:50 +0100
    Processed: reopen, should not migrate before glibc 2.42-10 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-01-20 06:50 +0100
    Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation Santiago Vila <sanvila@debian.org> - 2026-01-23 02:20 +0100
      Processed: binutils-x86-64-linux-gnu: input SFrame sections with  different format versions prevent .sframe generation "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-01-23 02:30 +0100
      Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation Aurelien Jarno <aurel32@debian.org> - 2026-01-23 23:00 +0100
    Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation Aurelien Jarno <aurel32@debian.org> - 2026-01-24 14:30 +0100
      Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation Aurelien Jarno <aurel32@debian.org> - 2026-01-25 14:50 +0100
    Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation Adrian Bunk <bunk@debian.org> - 2026-01-24 17:10 +0100
      Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation Santiago Vila <sanvila@debian.org> - 2026-01-25 16:10 +0100
    Bug#1125944: marked as done (binutils-x86-64-linux-gnu: input  SFrame sections with different format versions prevent .sframe generation) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-02-01 11:30 +0100

#409476 — Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation

Package: binutils-x86-64-linux-gnu
Version: 2.45.50.20260119-1
Severity: serious

Dear Maintainer,

I see this issue on amd64, i386 arm64 and with various sources.

,----
|     [2/2] : && /usr/bin/cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/svt-av1-dmo-3.1.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro CMakeFiles/cmTC_a80d2.dir/testCCompiler.c.o -o cmTC_a80d2   && :
|     FAILED: [code=1] cmTC_a80d2 
|     : && /usr/bin/cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/svt-av1-dmo-3.1.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro CMakeFiles/cmTC_a80d2.dir/testCCompiler.c.o -o cmTC_a80d2   && :
|     /usr/bin/x86_64-linux-gnu-ld.bfd: input SFrame sections with different format versions prevent .sframe generation
|     /usr/bin/x86_64-linux-gnu-ld.bfd: final link failed
|     collect2: error: ld returned 1 exit status
|     ninja: build stopped: subcommand failed.
`----


Christian


-- System Information:
Debian Release: forky/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.18.5-1-custom (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages binutils-x86-64-linux-gnu depends on:
ii  binutils-common  2.45.50.20260119-1
ii  libbinutils      2.45.50.20260119-1
ii  libc6            2.42-9
ii  libctf-nobfd0    2.45.50.20260119-1
ii  libctf0          2.45.50.20260119-1
ii  libjansson4      2.14-2+b4
ii  libsframe3       2.45.50.20260119-1
ii  libzstd1         1.5.7+dfsg-3+b1
ii  zlib1g           1:1.3.dfsg+really1.3.1-1+b2

binutils-x86-64-linux-gnu recommends no packages.

Versions of packages binutils-x86-64-linux-gnu suggests:
pn  binutils-doc  <none>

-- no debconf information

[toc] | [next] | [standalone]

#409478

On 1/19/26 11:54, Christian Marillat wrote:
> Package: binutils-x86-64-linux-gnu
> Version: 2.45.50.20260119-1
> Severity: serious
> 
> Dear Maintainer,
> 
> I see this issue on amd64, i386 arm64 and with various sources.

please submit complete bug reports. "various" ...

[toc] | [prev] | [next] | [standalone]

#409483

On 19 janv. 2026 12:06, Matthias Klose <doko@debian.org> wrote:

> On 1/19/26 11:54, Christian Marillat wrote:
>> Package: binutils-x86-64-linux-gnu
>> Version: 2.45.50.20260119-1
>> Severity: serious
>> Dear Maintainer,
>> I see this issue on amd64, i386 arm64 and with various sources.
>
> please submit complete bug reports. "various" ...

Various can be replaced by all.

This output come-from svt-av1 dmo source

https://www.deb-multimedia.org/pool/main/s/svt-av1-dmo/svt-av1-dmo_3.1.2-dmo1.debian.tar.xz
https://www.deb-multimedia.org/pool/main/s/svt-av1-dmo/svt-av1-dmo_3.1.2-dmo1.dsc
https://www.deb-multimedia.org/pool/main/s/svt-av1-dmo/svt-av1-dmo_3.1.2.orig.tar.xz

Christian

[toc] | [prev] | [next] | [standalone]

#409493

Control: tags -1 + important

On 1/19/26 12:42, Christian Marillat wrote:
> On 19 janv. 2026 12:06, Matthias Klose <doko@debian.org> wrote:
> 
>> On 1/19/26 11:54, Christian Marillat wrote:
>>> Package: binutils-x86-64-linux-gnu
>>> Version: 2.45.50.20260119-1
>>> Severity: serious
>>> Dear Maintainer,
>>> I see this issue on amd64, i386 arm64 and with various sources.
>>
>> please submit complete bug reports. "various" ...
> 
> Various can be replaced by all.
> 
> This output come-from svt-av1 dmo source
> 
> https://www.deb-multimedia.org/pool/main/s/svt-av1-dmo/svt-av1-dmo_3.1.2-dmo1.debian.tar.xz
> https://www.deb-multimedia.org/pool/main/s/svt-av1-dmo/svt-av1-dmo_3.1.2-dmo1.dsc
> https://www.deb-multimedia.org/pool/main/s/svt-av1-dmo/svt-av1-dmo_3.1.2.orig.tar.xz

that's outside of Debian. Is this seen in the Debian archive as well? 
Note, that you should just rebuild your binaries that have sframe v2 
sections.

[toc] | [prev] | [next] | [standalone]

#409492 — Processed (with 1 error): Re: Bug#1125944: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation

Processing control commands:

> tags -1 + important
Unknown tag/s: important.
Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore forky forky-ignore.

Bug #1125944 [binutils-x86-64-linux-gnu] binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation
Requested to add no tags; doing nothing.

-- 
1125944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125944
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#409505 — Bug#1125944: marked as done (binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 19 Jan 2026 19:35:08 +0000
with message-id <E1vhv1o-0000000DwVf-3c7z@fasolo.debian.org>
and subject line Bug#1125944: fixed in glibc 2.42-10
has caused the Debian Bug report #1125944,
regarding binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation
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 owner@bugs.debian.org
immediately.)


-- 
1125944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125944
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#409507

Hi,

On 2026-01-19 14:43, Matthias Klose wrote:
> I didn't realize that glibc was still built with --enable-sframe. sframe v2
> and v3 are incompatible. Only future vX versions will see upgradability.
> 
> To move forward,
> 
>   - glibc needs to be built without --enable-sframe on i386,
>     amd64, x32 and arm64, binaries uploaded to unstable,
>     built in testing.

Source upload is done. Binary uploads are following. Then this will need 
binNMUs so that this version can migrate.

>   - then glibc can be built again with --enable-sframe
>     enabled, maybe adjusting glibc build-deps on binutils.
>     sframe also should be enabled on s390x.

Let's first try to get it migrate in testing first before trying to 
reenable it. Also please note there is no sframe support in glibc for 
s390x.

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

[toc] | [prev] | [next] | [standalone]

#409523 — Processed: reopen, should not migrate before glibc 2.42-10

Processing control commands:

> reopen -1
Bug #1125944 {Done: Aurelien Jarno <aurel32@debian.org>} [binutils-x86-64-linux-gnu] binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions glibc/2.42-10.
> severity -1 serious
Bug #1125944 [binutils-x86-64-linux-gnu] binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation
Severity set to 'serious' from 'critical'

-- 
1125944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125944
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#409691

severity 1125944 grave
affects 1125944 src:ableton-link src:density-fitness src:dump src:dynarmic src:fenics-dolfinx src:fizmo-console src:fizmo-ncursesw src:fuzzylite src:gcc-11-cross-ports src:gcc-12-cross-ports src:gcc-13-cross-ports src:gnome-system-monitor src:libbgcode src:libmcfp src:libodsstream src:libpdb-redo src:libsfml src:lomiri-thumbnailer src:metview src:metview src:metview src:mrc src:netgen src:nuspell src:oaknut src:openblas src:posixsignalmanager src:rdkit src:snapcast src:sqlite-modern-cpp src:swiftlang src:termpaint src:therion src:threeb src:tl-expected src:tl-optional src:tuiwidgets src:yuzu src:appstream-generator src:augustus src:cli11 src:corectrl src:dssp src:endless-sky src:fizmo-sdl2 src:gcc-14-cross-ports src:gcc-15-cross-ports src:genomicsdb src:highs src:j4-dmenu-desktop src:libcifpp src:libcsfml src:libpappsomspp src:nmodl src:papilo src:purify src:rapidfuzz-cpp src:sdpa src:sol2 src:sopt src:spdlog src:tortoize src:tuning-library
thanks

I'm adding all the packages I found which currently FTBFS with this error:

input SFrame sections with different format versions prevent .sframe generation

Thanks.

[toc] | [prev] | [next] | [standalone]

#409692 — Processed: binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation

Processing commands for control@bugs.debian.org:

> severity 1125944 grave
Bug #1125944 [binutils-x86-64-linux-gnu] binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation
Severity set to 'grave' from 'serious'
> affects 1125944 src:ableton-link src:density-fitness src:dump src:dynarmic src:fenics-dolfinx src:fizmo-console src:fizmo-ncursesw src:fuzzylite src:gcc-11-cross-ports src:gcc-12-cross-ports src:gcc-13-cross-ports src:gnome-system-monitor src:libbgcode src:libmcfp src:libodsstream src:libpdb-redo src:libsfml src:lomiri-thumbnailer src:metview src:metview src:metview src:mrc src:netgen src:nuspell src:oaknut src:openblas src:posixsignalmanager src:rdkit src:snapcast src:sqlite-modern-cpp src:swiftlang src:termpaint src:therion src:threeb src:tl-expected src:tl-optional src:tuiwidgets src:yuzu src:appstream-generator src:augustus src:cli11 src:corectrl src:dssp src:endless-sky src:fizmo-sdl2 src:gcc-14-cross-ports src:gcc-15-cross-ports src:genomicsdb src:highs src:j4-dmenu-desktop src:libcifpp src:libcsfml src:libpappsomspp src:nmodl src:papilo src:purify src:rapidfuzz-cpp src:sdpa src:sol2 src:sopt src:spdlog src:tortoize src:tuning-library
Bug #1125944 [binutils-x86-64-linux-gnu] binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation
Added indication that 1125944 affects src:ableton-link, src:density-fitness, src:dump, src:dynarmic, src:fenics-dolfinx, src:fizmo-console, src:fizmo-ncursesw, src:fuzzylite, src:gcc-11-cross-ports, src:gcc-12-cross-ports, src:gcc-13-cross-ports, src:gnome-system-monitor, src:libbgcode, src:libmcfp, src:libodsstream, src:libpdb-redo, src:libsfml, src:lomiri-thumbnailer, src:metview, src:mrc, src:netgen, src:nuspell, src:oaknut, src:openblas, src:posixsignalmanager, src:rdkit, src:snapcast, src:sqlite-modern-cpp, src:swiftlang, src:termpaint, src:therion, src:threeb, src:tl-expected, src:tl-optional, src:tuiwidgets, src:yuzu, src:appstream-generator, src:augustus, src:cli11, src:corectrl, src:dssp, src:endless-sky, src:fizmo-sdl2, src:gcc-14-cross-ports, src:gcc-15-cross-ports, src:genomicsdb, src:highs, src:j4-dmenu-desktop, src:libcifpp, src:libcsfml, src:libpappsomspp, src:nmodl, src:papilo, src:purify, src:rapidfuzz-cpp, src:sdpa, src:sol2, src:sopt, src:spdlog, src:tortoize, and src:tuning-library
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1125944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125944
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#409776

Hi,

On 2026-01-23 02:16, Santiago Vila wrote:
> severity 1125944 grave
> affects 1125944 src:ableton-link src:density-fitness src:dump src:dynarmic src:fenics-dolfinx src:fizmo-console src:fizmo-ncursesw src:fuzzylite src:gcc-11-cross-ports src:gcc-12-cross-ports src:gcc-13-cross-ports src:gnome-system-monitor src:libbgcode src:libmcfp src:libodsstream src:libpdb-redo src:libsfml src:lomiri-thumbnailer src:metview src:metview src:metview src:mrc src:netgen src:nuspell src:oaknut src:openblas src:posixsignalmanager src:rdkit src:snapcast src:sqlite-modern-cpp src:swiftlang src:termpaint src:therion src:threeb src:tl-expected src:tl-optional src:tuiwidgets src:yuzu src:appstream-generator src:augustus src:cli11 src:corectrl src:dssp src:endless-sky src:fizmo-sdl2 src:gcc-14-cross-ports src:gcc-15-cross-ports src:genomicsdb src:highs src:j4-dmenu-desktop src:libcifpp src:libcsfml src:libpappsomspp src:nmodl src:papilo src:purify src:rapidfuzz-cpp src:sdpa src:sol2 src:sopt src:spdlog src:tortoize src:tuning-library
> thanks
> 
> I'm adding all the packages I found which currently FTBFS with this error:
> 
> input SFrame sections with different format versions prevent .sframe generation
> 

Thanks for testing that. After a quick investigation, the problem is 
that these try to link with a library that is still in using SFrame v2. 
For instance dump FTBFS due to libcatch2-dev which has been built with 
gcc-14 14.3.0-6, which enabled SFrame generation.

There are ~650 sources packages that have a ELF binary in /usr/lib/* 
with SFrame v2 on amd64. That said the common denominator with the above 
failures, seems to be that they try to link against a static library 
with SFrame v2. Scanning the archive, I have found that the following 
source packages that have a binary package that ships a .a or a .o with 
SFrame v2 on amd64:

afflib_3.7.22-1
altos_1.9.22-2+b1
avahi_0.8-17
base16384_2.3.2-1
catch2_3.7.1-0.6
coinor-csdp_6.2.0-6
cpu_1.4.3-16
crossfire_1.75.0-9
dbus-test-runner_19.04.0-2
emoslib_2:4.5.9-12
funtools_1.4.8-2
gerbv_2.10.0-2
ginac_1.8.9-1
gmp-ecm_7.0.6+ds-2
haskell-bv-sized_1.0.5-2+b3
haskell-parameterized-utils_2.1.9.0-2
haskell-tasty-checklist_1.0.6.0-2+b3
haskell-what4_1.5.1-4+b4
ijs_0.35-16
irstlm_6.00.05-7
jpeg-xl_0.11.1-6
lapack_3.12.1-7
libdrilbo_0.2.11-2.2
libfizmo_0.7.15-2.2
libkal_0.9.0-6
libprintsys_0.6-14
libpyzy_1.0.1-9
librelp_1.12.0-1
libssh_0.11.3-1
libstb_0.0~git20250907.fede005+ds-1
libxt_1:1.2.1-1.3
litehtml_0.9-1
lmbench_3.0-a9+debian.1-10
lp-solve_5.5.2.14-4.1
lwipv6_1.5a-10.1
magics++_4.16.0+really4.16.0-2
meschach_1.2b-19
mojoshader_0.0~hg1314+git20250606.93d9d45+dfsg-1
openblas_0.3.30+ds-3
openzwave_1.6.1914+ds2-4
osra_2.1.3-4
persistent-cache-cpp_1.0.9-1
pgplot5_5.2.2-19.8
racket_8.18+dfsg1-1
rumur_2025.08.31-1
skycat_3.1.2+starlink1~b+dfsg-10
sqlite3_3.46.1-8
stalin_0.11-11
starlink-ast_9.2.10+dfsg-3
tclx8.4_8.4.1-6
triangle_1.6-7
wcstools_3.9.7-2
xnee_3.19-9.4

I guess binNMUing them should fix the issue.

Note that the src:gcc-XX-cross-ports FTBFS are probably fixed with 
cross-toolchain-base-ports version 76.

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

[toc] | [prev] | [next] | [standalone]

#409834

On 2026-01-24 10:54, Sebastian Ramacher wrote:
> On 2026-01-24 00:51:57 +0100, Sebastian Ramacher wrote:
> > On 2026-01-23 22:48:23 +0100, Aurelien Jarno wrote:
> > > Hi,
> > > 
> > > On 2026-01-23 02:16, Santiago Vila wrote:
> > > > severity 1125944 grave
> > > > affects 1125944 src:ableton-link src:density-fitness src:dump src:dynarmic src:fenics-dolfinx src:fizmo-console src:fizmo-ncursesw src:fuzzylite src:gcc-11-cross-ports src:gcc-12-cross-ports src:gcc-13-cross-ports src:gnome-system-monitor src:libbgcode src:libmcfp src:libodsstream src:libpdb-redo src:libsfml src:lomiri-thumbnailer src:metview src:metview src:metview src:mrc src:netgen src:nuspell src:oaknut src:openblas src:posixsignalmanager src:rdkit src:snapcast src:sqlite-modern-cpp src:swiftlang src:termpaint src:therion src:threeb src:tl-expected src:tl-optional src:tuiwidgets src:yuzu src:appstream-generator src:augustus src:cli11 src:corectrl src:dssp src:endless-sky src:fizmo-sdl2 src:gcc-14-cross-ports src:gcc-15-cross-ports src:genomicsdb src:highs src:j4-dmenu-desktop src:libcifpp src:libcsfml src:libpappsomspp src:nmodl src:papilo src:purify src:rapidfuzz-cpp src:sdpa src:sol2 src:sopt src:spdlog src:tortoize src:tuning-library
> > > > thanks
> > > > 
> > > > I'm adding all the packages I found which currently FTBFS with this error:
> > > > 
> > > > input SFrame sections with different format versions prevent .sframe generation
> > > > 
> > > 
> > > Thanks for testing that. After a quick investigation, the problem is 
> > > that these try to link with a library that is still in using SFrame v2. 
> > > For instance dump FTBFS due to libcatch2-dev which has been built with 
> > > gcc-14 14.3.0-6, which enabled SFrame generation.
> > > 
> > > There are ~650 sources packages that have a ELF binary in /usr/lib/* 
> > > with SFrame v2 on amd64. That said the common denominator with the above 
> > > failures, seems to be that they try to link against a static library 
> > > with SFrame v2. Scanning the archive, I have found that the following 
> > > source packages that have a binary package that ships a .a or a .o with 
> > > SFrame v2 on amd64:
> > > 
> > > afflib_3.7.22-1
> > > altos_1.9.22-2+b1
> > > avahi_0.8-17
> > > base16384_2.3.2-1
> > > catch2_3.7.1-0.6
> > > coinor-csdp_6.2.0-6
> > > cpu_1.4.3-16
> > > crossfire_1.75.0-9
> > > dbus-test-runner_19.04.0-2
> > > emoslib_2:4.5.9-12
> > > funtools_1.4.8-2
> > > gerbv_2.10.0-2
> > > ginac_1.8.9-1
> > > gmp-ecm_7.0.6+ds-2
> > > haskell-bv-sized_1.0.5-2+b3
> > > haskell-parameterized-utils_2.1.9.0-2
> > > haskell-tasty-checklist_1.0.6.0-2+b3
> > > haskell-what4_1.5.1-4+b4
> > > ijs_0.35-16
> > > irstlm_6.00.05-7
> > > jpeg-xl_0.11.1-6
> > > lapack_3.12.1-7
> > > libdrilbo_0.2.11-2.2
> > > libfizmo_0.7.15-2.2
> > > libkal_0.9.0-6
> > > libprintsys_0.6-14
> > > libpyzy_1.0.1-9
> > > librelp_1.12.0-1
> > > libssh_0.11.3-1
> > > libstb_0.0~git20250907.fede005+ds-1
> > > libxt_1:1.2.1-1.3
> > > litehtml_0.9-1
> > > lmbench_3.0-a9+debian.1-10
> > > lp-solve_5.5.2.14-4.1
> > > lwipv6_1.5a-10.1
> > > magics++_4.16.0+really4.16.0-2
> > > meschach_1.2b-19
> > > mojoshader_0.0~hg1314+git20250606.93d9d45+dfsg-1
> > > openblas_0.3.30+ds-3
> > > openzwave_1.6.1914+ds2-4
> > > osra_2.1.3-4
> > > persistent-cache-cpp_1.0.9-1
> > > pgplot5_5.2.2-19.8
> > > racket_8.18+dfsg1-1
> > > rumur_2025.08.31-1
> > > skycat_3.1.2+starlink1~b+dfsg-10
> > > sqlite3_3.46.1-8
> > > stalin_0.11-11
> > > starlink-ast_9.2.10+dfsg-3
> > > tclx8.4_8.4.1-6
> > > triangle_1.6-7
> > > wcstools_3.9.7-2
> > > xnee_3.19-9.4
> > > 
> > > I guess binNMUing them should fix the issue.
> > 
> > Scheduled. ghc is currently undergoing a transition, so haskell-* will
> > see uploads and rebuilds anyway.

Thanks!

This is the list for arm64:

emoslib_2:4.5.9-12
haskell-bv-sized_1.0.5-2+b3
haskell-parameterized-utils_2.1.9.0-2
haskell-tasty-checklist_1.0.6.0-2+b3
haskell-what4_1.5.1-4+b3
ne10_1.2.1-6

emoslib has an open FTBFS bug, haskell-* are undergoing a transition so 
only ne10 is left.

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

[toc] | [prev] | [next] | [standalone]

#409881

On 2026-01-24 14:23, Aurelien Jarno wrote:
> On 2026-01-24 10:54, Sebastian Ramacher wrote:
> > On 2026-01-24 00:51:57 +0100, Sebastian Ramacher wrote:
> > > On 2026-01-23 22:48:23 +0100, Aurelien Jarno wrote:
> > > > Hi,
> > > > 
> > > > On 2026-01-23 02:16, Santiago Vila wrote:
> > > > > severity 1125944 grave
> > > > > affects 1125944 src:ableton-link src:density-fitness src:dump src:dynarmic src:fenics-dolfinx src:fizmo-console src:fizmo-ncursesw src:fuzzylite src:gcc-11-cross-ports src:gcc-12-cross-ports src:gcc-13-cross-ports src:gnome-system-monitor src:libbgcode src:libmcfp src:libodsstream src:libpdb-redo src:libsfml src:lomiri-thumbnailer src:metview src:metview src:metview src:mrc src:netgen src:nuspell src:oaknut src:openblas src:posixsignalmanager src:rdkit src:snapcast src:sqlite-modern-cpp src:swiftlang src:termpaint src:therion src:threeb src:tl-expected src:tl-optional src:tuiwidgets src:yuzu src:appstream-generator src:augustus src:cli11 src:corectrl src:dssp src:endless-sky src:fizmo-sdl2 src:gcc-14-cross-ports src:gcc-15-cross-ports src:genomicsdb src:highs src:j4-dmenu-desktop src:libcifpp src:libcsfml src:libpappsomspp src:nmodl src:papilo src:purify src:rapidfuzz-cpp src:sdpa src:sol2 src:sopt src:spdlog src:tortoize src:tuning-library
> > > > > thanks
> > > > > 
> > > > > I'm adding all the packages I found which currently FTBFS with this error:
> > > > > 
> > > > > input SFrame sections with different format versions prevent .sframe generation
> > > > > 
> > > > 
> > > > Thanks for testing that. After a quick investigation, the problem is 
> > > > that these try to link with a library that is still in using SFrame v2. 
> > > > For instance dump FTBFS due to libcatch2-dev which has been built with 
> > > > gcc-14 14.3.0-6, which enabled SFrame generation.
> > > > 
> > > > There are ~650 sources packages that have a ELF binary in /usr/lib/* 
> > > > with SFrame v2 on amd64. That said the common denominator with the above 
> > > > failures, seems to be that they try to link against a static library 
> > > > with SFrame v2. Scanning the archive, I have found that the following 
> > > > source packages that have a binary package that ships a .a or a .o with 
> > > > SFrame v2 on amd64:
> > > > 
> > > > afflib_3.7.22-1
> > > > altos_1.9.22-2+b1
> > > > avahi_0.8-17
> > > > base16384_2.3.2-1
> > > > catch2_3.7.1-0.6
> > > > coinor-csdp_6.2.0-6
> > > > cpu_1.4.3-16
> > > > crossfire_1.75.0-9
> > > > dbus-test-runner_19.04.0-2
> > > > emoslib_2:4.5.9-12
> > > > funtools_1.4.8-2
> > > > gerbv_2.10.0-2
> > > > ginac_1.8.9-1
> > > > gmp-ecm_7.0.6+ds-2
> > > > haskell-bv-sized_1.0.5-2+b3
> > > > haskell-parameterized-utils_2.1.9.0-2
> > > > haskell-tasty-checklist_1.0.6.0-2+b3
> > > > haskell-what4_1.5.1-4+b4
> > > > ijs_0.35-16
> > > > irstlm_6.00.05-7
> > > > jpeg-xl_0.11.1-6
> > > > lapack_3.12.1-7
> > > > libdrilbo_0.2.11-2.2
> > > > libfizmo_0.7.15-2.2
> > > > libkal_0.9.0-6
> > > > libprintsys_0.6-14
> > > > libpyzy_1.0.1-9
> > > > librelp_1.12.0-1
> > > > libssh_0.11.3-1
> > > > libstb_0.0~git20250907.fede005+ds-1
> > > > libxt_1:1.2.1-1.3
> > > > litehtml_0.9-1
> > > > lmbench_3.0-a9+debian.1-10
> > > > lp-solve_5.5.2.14-4.1
> > > > lwipv6_1.5a-10.1
> > > > magics++_4.16.0+really4.16.0-2
> > > > meschach_1.2b-19
> > > > mojoshader_0.0~hg1314+git20250606.93d9d45+dfsg-1
> > > > openblas_0.3.30+ds-3
> > > > openzwave_1.6.1914+ds2-4
> > > > osra_2.1.3-4
> > > > persistent-cache-cpp_1.0.9-1
> > > > pgplot5_5.2.2-19.8
> > > > racket_8.18+dfsg1-1
> > > > rumur_2025.08.31-1
> > > > skycat_3.1.2+starlink1~b+dfsg-10
> > > > sqlite3_3.46.1-8
> > > > stalin_0.11-11
> > > > starlink-ast_9.2.10+dfsg-3
> > > > tclx8.4_8.4.1-6
> > > > triangle_1.6-7
> > > > wcstools_3.9.7-2
> > > > xnee_3.19-9.4
> > > > 
> > > > I guess binNMUing them should fix the issue.
> > > 
> > > Scheduled. ghc is currently undergoing a transition, so haskell-* will
> > > see uploads and rebuilds anyway.
> 
> Thanks!
> 
> This is the list for arm64:
> 
> emoslib_2:4.5.9-12
> haskell-bv-sized_1.0.5-2+b3
> haskell-parameterized-utils_2.1.9.0-2
> haskell-tasty-checklist_1.0.6.0-2+b3
> haskell-what4_1.5.1-4+b3
> ne10_1.2.1-6
> 
> emoslib has an open FTBFS bug, haskell-* are undergoing a transition so 
> only ne10 is left.
> 

And for reference this is the list for forky on amd64:

dcl_7.5.2-1+b1
emoslib_2:4.5.9-12
gsl_2.8+dfsg-5.1
gtk2hs-buildtools_0.13.11.0-1+b2
haskell-bv-sized_1.0.5-2+b3
haskell-filestore_0.6.5.1-1
haskell-hashtables_1.4.2-1
haskell-parameterized-utils_2.1.9.0-2
haskell-tasty-checklist_1.0.6.0-2+b3
haskell-what4_1.5.1-4+b4
jpeg-xl_0.11.1-6
xnee_3.19-9.4

and on arm64:

dcl_7.5.2-1+b1
emoslib_2:4.5.9-12
gsl_2.8+dfsg-5.1
haskell-bv-sized_1.0.5-2+b3
haskell-parameterized-utils_2.1.9.0-2
haskell-tasty-checklist_1.0.6.0-2+b3
haskell-what4_1.5.1-4+b3
ne10_1.2.1-6

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net

[toc] | [prev] | [next] | [standalone]

#409840

On Sat, Jan 24, 2026 at 11:50:52AM +0100, Santiago Vila wrote:
> On Sat, Jan 24, 2026 at 11:30:19AM +0100, Santiago Vila wrote:
> 
> > A weird one is "sdpa", which failed today at 2026-01-24 06:16 UTC.
> > I'm retesting that one too after the mirror sync of 8:00 UTC.
> 
> Good news: sdpa now builds ok.
> 
> However, there is another small set of packages which FTBFS
> because ld segfaults, and they still FTBFS today.
> 
> For example, asterisk ftbfs like this:
> 
> gcc -g -Wl,-znoexecstack -nostartfiles  -nodefaultlibs -nostdlib -r -Wl,-b,binary -o res_geolocation/pidf_lo_test.o re
> s_geolocation/pidf_lo_test.xml
> collect2: fatal error: ld terminated with signal 11 [Segmentation fault]
> 
> I initially assumed they could be related with this binutils issue,
> but I don't really know.

asterisk builds with binutils/forky.

ld segfaults with binutils/sid even when using -Wl,--discard-sframe.

Debian is currently following the upstream master branch of binutils,
based on the above I would suspect a binutils regression unrelated
to sframe.

Backtrace:
#0  0x0000555555572260 in ldelf_after_open (elfsize=64, prefix=0x5555555aa226 "/usr", is_freebsd=0, is_linux=1, native=1, 
    use_libpath=1) at ../../ld/ldelf.c:1333
#1  0x0000555555594805 in ldemul_after_open () at ../../ld/ldemul.c:80
#2  lang_process () at ../../ld/ldlang.c:8563
#3  0x000055555559a401 in main (argc=31, argv=<optimized out>) at ../../ld/ldmain.c:958

This is likely:
https://sourceware.org/bugzilla/show_bug.cgi?id=33780

> Thanks.

cu
Adrian

[toc] | [prev] | [next] | [standalone]

#409895

On Sat, Jan 24, 2026 at 06:06:20PM +0200, Adrian Bunk wrote:

> asterisk builds with binutils/forky.
> 
> ld segfaults with binutils/sid even when using -Wl,--discard-sframe.
> 
> Debian is currently following the upstream master branch of binutils,
> based on the above I would suspect a binutils regression unrelated
> to sframe.
> 
> Backtrace:
> #0  0x0000555555572260 in ldelf_after_open (elfsize=64, prefix=0x5555555aa226 "/usr", is_freebsd=0, is_linux=1, native=1, 
>     use_libpath=1) at ../../ld/ldelf.c:1333
> #1  0x0000555555594805 in ldemul_after_open () at ../../ld/ldemul.c:80
> #2  lang_process () at ../../ld/ldlang.c:8563
> #3  0x000055555559a401 in main (argc=31, argv=<optimized out>) at ../../ld/ldmain.c:958
> 
> This is likely:
> https://sourceware.org/bugzilla/show_bug.cgi?id=33780

Thanks a lot for the info.

I've reported the ld segfault issue as #1126397, but Matthias disputes
that the bug is RC and still tags the bug as "moreinfo". As a bug
reporter, I think I already did everything I could do and therefore do
not find such request reasonable.

Release Managers: Could you please look at the bug and adjust the
severity if appropriate?

With available data, I believe we should not allow this binutils
version in testing.

Thanks.

[toc] | [prev] | [next] | [standalone]

#410256 — Bug#1125944: marked as done (binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sun, 1 Feb 2026 11:20:19 +0100
with message-id <c7a10dbe-77b4-4bdf-832f-2cefc7d00474@debian.org>
and subject line closing, nothing to do anymore on the binutils side
has caused the Debian Bug report #1125944,
regarding binutils-x86-64-linux-gnu: input SFrame sections with different format versions prevent .sframe generation
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 owner@bugs.debian.org
immediately.)


-- 
1125944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125944
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web