[Bug 274703] clang-16.0.6 crashes on science/rdkit rdkit-2023.09.1 on 15.0-CURRENT amd64

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274703

--- Comment #4 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
(In reply to Mark Millard from comment #3)

That is not the issue: /usr/bin/c++ is in use. I'll note that:

[ 21% 166/640] /usr/bin/c++ -DBOOST_SERIALIZATION_DYN_LINK -DGraphMol_EXPORTS
-DRDKIT_DYN_LINK -DRDKIT_GRAPHMOL_BUILD -DRDK_64BIT_BUILD
-DRDK_BUILD_COORDGEN_SUPPORT -DRDK_BUILD_DESCRIPTORS3D
-DRDK_BUILD_MAEPARSER_SUPPORT -DRDK_BUILD_THREADSAFE_SSS -DRDK_HAS_EIGEN3
-DRDK_TEST_MULTITHREADED -DRDK_USE_BOOST_SERIALIZATION
-DRDK_USE_STRICT_ROTOR_DEFINITION -DRDK_USE_URF
-I/wrkdirs/usr/ports/science/rdkit/work/rdkit-Release_2023_09_1/External
-I/wrkdirs/usr/ports/science/rdkit/work/rdkit-Release_2023_09_1/External/RingFamilies/RingDecomposerLib/src/RingDecomposerLib
-I/usr/local/include/python3.9
-I/usr/local/lib/python3.9/site-packages/numpy/core/include
-I/wrkdirs/usr/ports/science/rdkit/work/rdkit-Release_2023_09_1/Code
-I/usr/local/include -isystem /usr/local/include/eigen3 -O2 -pipe
-fstack-protector-strong -fno-strict-aliasing -mpopcnt -Wall -Wextra
-Wno-deprecated -Wno-unused-function -fno-strict-aliasing -Wno-format
-Wno-logical-op-parentheses -fPIC -O2 -pipe -fstack-protector-strong
-fno-strict-aliasing   -DNDEBUG -std=gnu++17 -fPIC -pthread -MD -MT
Code/GraphMol/CMakeFiles/GraphMol.dir/Canon.cpp.o -MF
Code/GraphMol/CMakeFiles/GraphMol.dir/Canon.cpp.o.d -o
Code/GraphMol/CMakeFiles/GraphMol.dir/Canon.cpp.o -c
/wrkdirs/usr/ports/science/rdkit/work/rdkit-Release_2023_09_1/Code/GraphMol/Canon.cpp

worked just fine in my build  (amd64 context).

This might suggest corrupted file system data at the time on the FreeBSD
port -> package build server at the time or some other corruption at the
time?

Have the FreeBSD build servers been dealing with all the updates for
recently known ZFS corruption problems? I note that the host is listed
as:

Host OSVERSION: 1500000
Jail OSVERSION: 1500002

This suggests that the actual kernel involved (Host) might not have all
the updates. But it is also not clear what zpool features were or are
enabled.

-- 
You are receiving this mail because:
You are the assignee for the bug.