On Sun, 14 Sep 2025 12:40:41 +0200 Rene Engelhard <[email protected]> wrote:
> Version: 1.3.14-7
>
> Hi,
>
> Am 14.09.25 um 12:35 schrieb Adrian Bunk:
> > ...
> > CMake Error at CMakeLists.txt:5 (project):
> > The CMAKE_CXX_COMPILER:
> >
> > g++-14
> >
> > is not a full path and was not found in the PATH.
> >
> > Tell CMake where to find the compiler by setting either the
environment
> > variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the
full path
> > to the compiler, or to the compiler name if it is in the PATH.
> >
> >
> > -- Configuring incomplete, errors occurred!
>
> already fixed in -7. Which was already uploaded, but, well, dak (or
better: lintian)...
>
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:
# debian/tests/test: 5:14
export CTEST_OUTPUT_ON_FAILURE=True
case $(uname -m) in
aarch64 | ppc64le | loongarch64)
export CXX=g++-14
export CC=gcc-14
;;
*)
;;
esac
This adds test failure information, which can be helpful. It resolves the
issue on arm64. However, the issue on ppcel64 remains. 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.
#debian/rules: 6:20
# https://github.com/silnrsi/graphite/issues/96
ifeq "$(DEB_HOST_ARCH)" "arm64"
export CXX := g++-14
export CC := gcc-14
endif
ifeq "$(DEB_HOST_ARCH)" "ppc64el"
export CXX := g++-14
export CC := gcc-14
endif
ifeq "$(DEB_HOST_ARCH)" "loong64"
export CXX := g++-14
export CC := gcc-14
endif
>
> Regards,
>
>
> Rene
>
>
>
