Hi, Am 29.09.25 um 14:32 schrieb John Chittum:
recent uploads fixed build issues in Debian, but autopkgtests are still failing. This is due to using gcc-15 when compiling the test files. in Ubuntu, I'm proposing:
yes, noticed that too. Didn't deem it too important to warrant an immediate upload :) (And it would need to be kept in sync with rules...)
# debian/tests/test: 5:14 export CTEST_OUTPUT_ON_FAILURE=True
Ah, that's interesting. But it's probably better directly do ctest --verbose instead of make test (but that would need a cmake dependency...). So this and make test VERBOSE=true is as best as we can get in autopkgtest...
case $(uname -m) in aarch64 | ppc64le | loongarch64)
Can't we just use dpkg-architecture here? We are in a autopkgtest here and can assume dpkg tooling (and be it via a dependency. And if I understand it right @buildddeps@ installs build-essential which installs dpkg-dev anyway.
export CXX=g++-14
ACK
export CC=gcc-14
See below
This adds test failure information, which can be helpful. It resolves the issue on arm64. However, the issue on ppcel64 remains.
Interesting.
You can see an example autopkgtest failure in Ubuntu with the patch in place here: https://autopkgtest.ubuntu.com/results/autopkgtest-questing-jchittum-graphite2-lp2124952/questing/ppc64el/g/graphite2/20250926_112302_5a2ef@/log.gz Further, if LTO gets enabled for builds, this will fail as it needs the CC:= flag set as well. current proposed patch for Ubuntu is. just adds the CC:=gcc-14 flag as needed. Needed for Ubuntu, since we enable LTO by default.
Hmm, OK. Something for later then. Added export CTEST_OUTPUT_ON_FAILURE=True and the case with dpkg-architecture in git. But next time please send a proper diff -u... (or directly do a MR on salsa). Regards, Rene
