> you could test with paxctl on the cmake file With paxctl +m /usr/pkg/bin/cmake (inside the chroot, of course), it now core dumps even earlier in the build, with
#0 0x000000000079d33c in cmsys::SystemTools::FilesDiffer(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () (gdb) bt #0 0x000000000079d33c in cmsys::SystemTools::FilesDiffer(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () #1 0x0000000000437072 in cmGeneratedFileStreamBase::Close() () #2 0x0000000000437141 in cmGeneratedFileStreamBase::~cmGeneratedFileStreamBase() () #3 0x0000000000437263 in cmGeneratedFileStream::~cmGeneratedFileStream() () #4 0x00000000006ec4da in cmLocalUnixMakefileGenerator3::ScanDependencies(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::map<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, cmDepends::DependencyVector, std::less<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, cmDepends::DependencyVector> > >&) () #5 0x00000000006ecbe4 in cmLocalUnixMakefileGenerator3::UpdateDependencies(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool, bool) () #6 0x000000000041d958 in cmcmd::ExecuteCMakeCommand(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> > > >&) () #7 0x000000000040cb41 in main () > Maybe you should set sysctl security.pax.mprotect.global=0 while building > the old pkgs? That works. What I don't understand is why it dumps core while reporting an error.
