Re: cmake ftbfs on ppc64el (and ppc64)
Hello,
the bug is definitely still present and I'm therefore not sure whether
downgrading the priority to normal is justified.
On ppc64, cmake still crashes regularly when configuring the LLVM build
for example [1]:
-- Looking for pow in m - found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Looking for backtrace in execinfo
Segmentation fault
I have performed a local LLVM test build and obtained a backtrace with gdb
which also indicates a crash in libuv:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000000000000000 in ?? ()
[Current thread is 1 (Thread 0x7fff811f6e60 (LWP 2635470))]
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 <signal handler called>
#2 0x00007fff82eee784 in __GI_epoll_pwait (epfd=4, events=0x7fffd3808cc8, maxevents=1024, timeout=-1, set=0x0) at ../sysdeps/unix/sysv/linux/epoll_pwait.c:40
#3 0x00007fff83545238 in uv__io_poll (loop=0x10015e8edd0, timeout=-1) at ./src/unix/linux.c:1365
#4 0x00007fff8352aa84 in uv_run (loop=0x10015e8edd0, mode=UV_RUN_ONCE) at ./src/unix/core.c:447
#5 0x0000000132669d8c in cmExecuteProcessCommand (args=..., status=...) at ./Source/cmExecuteProcessCommand.cxx:358
#6 0x0000000132561d38 in InvokeBuiltinCommand (status=..., args=..., command=@0x133045248: 0x1326682b0 <cmExecuteProcessCommand(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, cmExecutionStatus&)>)
at ./Source/cmState.cxx:420
#7 operator() (status=..., args=..., __closure=<optimized out>) at ./Source/cmState.cxx:430
#8 std::__invoke_impl<bool, cmState::AddBuiltinCommand(const std::string&, BuiltinCommand)::<lambda(const std::vector<cmListFileArgument>&, cmExecutionStatus&)>&, const
std::vector<cmListFileArgument, std::allocator<cmListFileArgument> >&, cmExecutionStatus&> (__f=...) at /usr/include/c++/13/bits/invoke.h:61
#9 std::__invoke_r<bool, cmState::AddBuiltinCommand(const std::string&, BuiltinCommand)::<lambda(const std::vector<cmListFileArgument>&, cmExecutionStatus&)>&, const std::vector<cmListFileArgument,
std::allocator<cmListFileArgument> >&, cmExecutionStatus&> (__fn=...) at /usr/include/c++/13/bits/invoke.h:114
#10 std::_Function_handler<bool(const std::vector<cmListFileArgument, std::allocator<cmListFileArgument> >&, cmExecutionStatus&), cmState::AddBuiltinCommand(const std::string&,
BuiltinCommand)::<lambda(const std::vector<cmListFileArgument, std::allocator<cmListFileArgument> >&, cmExecutionStatus&)> >::_M_invoke(const std::_Any_data &, const std::vector<cmListFileArgument,
std::allocator<cmListFileArgument> > &, cmExecutionStatus &) (__functor=..., __args#0=..., __args#1=...) at /usr/include/c++/13/bits/std_function.h:290
This bug has also been reported for openSUSE [2] and Simon Lees at SUSE said he
would be looking into it. In case he comes up with a solution, I will report it
here.
Adrian
> [1] https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-17&arch=ppc64&ver=1%3A17.0.6-4%2Bb2&stamp=1704985815&raw=0
> [2] https://bugzilla.suse.com/show_bug.cgi?id=1218365
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Reply to: