Bug#1098756: mame: FTBFS on arm64: pp01.cpp:(.text.unlikely+0x20): relocation truncated to fit: R_AARCH64_CALL26 against symbol `address_map::operator()(unsigned int, unsigned int)' defined in .text s

truncated to fit: R_AARCH64_CALL26 against symbol `address_map::operator()(unsigned int, unsigned int)' defined in .text section in ../../../../../scripts/src/libemu.a(addrmap.o) pp01.cpp:(.text.unlikely+0x1dc): additional relocation overflows omitted from the output collect2: error: ld returned 1 exit status make[4]: *** [mame.make:272: ../../../../../mame] Error 1 Cheers -- Sebastian Ramacher

Re: RFC: dropping armel from Debian for the upcoming release

here a conclusion to the discussion on d-arm@l.d.o? What is the opinion of the two porters that we currently have listed for armel (added to CC)? Cheers -- Sebastian Ramacher

Re: Status of the t64 transition

autopkgtests [1] and report or fix any issues related to failing tests. * Check if source-only uploads for Arch: all packages are missing. Cheers [1] Note that wecurrently ignore autopkgtest results on armel and armhf. -- Sebastian Ramacher

Re: Status of the t64 transition

Hi Andreas, please stop reopening the time_t bugs where transitions are staged in experimental. When we eventually start those transitions, they do not need to change the package name again as they will enter unstable with a new SONAME and built with the 64 bit time_t ABI. Cheers -- Sebastian

Re: Status of the t64 transition

On 2024-04-19 06:02:03 +0200, Andreas Metzler wrote: > On 2024-04-18 Sebastian Ramacher wrote: > [...] > > Let's start with the first category. Those are packages that could be > > binNMUed, but there are issues that make those rebuilds not have the > > desired effec

Status of the t64 transition

it to testing. The dd-list of the packages above is attached. Cheers -- Sebastian Ramacher A Mennucc1 dvbstreamer Adam Borowski kbtin termrec Adrian Knoth qstopmotion (U) Agathe Porte ortools (U) Alastair McKinstry cctools ggcov mathgl (U) ncl pyferret p

Bug#1068288: openjdk-21: bootstrap builds required on armel and armhf

t64 conflicts with: - libcups2:armhf (< 2.4.7-1.2) Somebody did the work to provide boostrap builds of openjdk-17 on armel and armhf. We need the same for openjdk-21. Cheers -- Sebastian Ramacher

Re: Bug#1065756: pngnq: FTBFS on arm{el, hf}: rwpng.c:242:13: error: implicit declaration of function ‘strncmp’ [-Werror=implicit-function-declaration]

error level in > arm{el, hf} arch than before. > > Thanks! > > 在 2024/3/10 08:36, xiao sheng wen(肖盛文) 写道: > > Hi, > > > >     Thanks for your report. > > The upstream of this package almost dead. > > > > The patch is welcome. > > > >

Re: Bug#1017538: dietlibc: FTBFS on armhf: selected processor does not support vldm in ARM mode

> Solange man keine schmutzigen Tricks macht, und ich meine *wirklich* > schmutzige Tricks, wie bei einer doppelt verketteten Liste beide > Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz > hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r -- Sebastian Ramacher

Re: Bug#1000255: mpv: autopkgtest failures

xel=dest_bits_per_pixel@entry=32, dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 and so on. I have no idea why that's happening, so any help is welcome. CCing the ARM porters and the libx11 maintainer for input. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature