Bug#1087564: pcre2: FTBFS on 32-bit: test failures, memory allocations smaller than expected
Simon McVittie <[email protected]> Fri, 15 Nov 2024 10:38:17 +0000
| Newsgroups | gmane.linux.debian.ports.hppa |
|---|---|
| Message-ID | <Zzckmal-ie7xvqHi__40747.7481685177$1731667346$gmane$org@remnant.pseudorandom.co.uk> |
Source: pcre2 Version: 10.44-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: [email protected], [email protected], [email protected], [email protected] User: [email protected] Usertags: armhf https://buildd.debian.org/status/fetch.php?pkg=pcre2&arch=armhf&ver=10.44-2&stamp=1731586953&raw=0 shows lots of test failures that look like this: > /((?i)b)/ > -Memory allocation - compiled block : 153 > +Memory allocation - compiled block : 129 > Memory allocation - code portion : 17 armel has a different failure mode (some of the tests crash) which I have reported as a separate bug - that's out of scope here. All of the other 32-bit architectures (i386, hppa, powerpc, x32) show symptoms similar to armhf, which makes me think this is a general 32-bit problem rather than being architecture-specific (and armel would probably have the same issue if its tests hadn't crashed first). Is this perhaps just an overly-strict test that is making assumptions about the size of data structures on 64-bit architectures, which aren't going to be true on 32-bit because pointers and 'long' are smaller there? 10.44-1 in experimental previously failed with similar symptoms. smcv