[Pkg-cmake-team] Bug#911400: cmake: Locks up when running autogen on m68k, upstream version works fine

John Paul Adrian Glaubitz glaubitz at physik.fu-berlin.de
Fri Oct 19 18:20:49 BST 2018


Source: cmake
Version: 3.12.3-2
Severity: normal
User: debian-68k at lists.debian.org
Usertags: m68k

Hi!

Since version 3.11.0, cmake is using libuv for more parallel processing
which has caused some regressions resulting in cmake locking up which
has been fixed in [2].

Unfortunately, on m68k, cmake >= 3.11.0 does still lock up which can be
seen in many packages failing on the buildds with a timeout [3]:

make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-m68k-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-m68k-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/obj-m68k-linux-gnu /<<PKGBUILDDIR>>/obj-m68k-linux-gnu /<<PKGBUILDDIR>>/obj-m68k-linux-gnu/CMakeFiles/nitrokey-app_autogen.dir/DependInfo.cmake --color=
Scanning dependencies of target nitrokey-app_autogen
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-m68k-linux-gnu'
/usr/bin/make -f CMakeFiles/nitrokey-app_autogen.dir/build.make CMakeFiles/nitrokey-app_autogen.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-m68k-linux-gnu'
[  2%] Automatic MOC and UIC for target nitrokey-app
/usr/bin/cmake -E cmake_autogen /<<PKGBUILDDIR>>/obj-m68k-linux-gnu/CMakeFiles/nitrokey-app_autogen.dir/AutogenInfo.cmake Release
E: Build killed with signal TERM after 600 minutes of inactivity

I have already done lots of testing but I was unable so far to figure
out what the exact problem is. However, I do know that cmake taken from
upstream works fine. That is, downloading the latest release tarball
(even pre-release) and building with "./bootstrap && make && make install"
builds and installs a version which does not lock up on m68k.

On the other hand, any Debianized version of cmake >= 3.11.0 shows the
problem and locks up. Among the things I have tried are stripping
off "--system-libs" from the bootstrap parameters as well as playing
around with setting various cmake builds flags (e.g. disabling libuv),
nothing helped so far. I have even updated a local package build
to the 3.13 pre-release without luck.

Thus, I have therefore disabled "cmake" on m68k for the time being
and uploaded a manual build of 3.10.3 with a forged version number
to the Debian Ports "unreleased" distribution so that cmake packages
continue to build fine on m68k until I have found the problem.

I will keep digging into the problem until I have figured out what
the problem is and will hopefully be able to provide a fix in the
near future.

Thanks,
Adrian

> [1] https://github.com/Kitware/CMake/commit/b5e21d7d2ed3168c9efcbc25c67d2c330d76d4d0
> [2] https://gitlab.kitware.com/cmake/cmake/merge_requests/1918
> [3] https://buildd.debian.org/status/fetch.php?pkg=nitrokey-app&arch=m68k&ver=1.3.1-1&stamp=1533934949&raw=0

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz at debian.org
`. `'   Freie Universitaet Berlin - glaubitz at physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



More information about the Pkg-cmake-team mailing list