reentrant mode selected by default with cmake

[Dimitri Lesnoff]

Hello,

I would like to know if it is usual that cmake selected the reentrant mode.

The single mode is clearly stated to be the default in the documentation.

When running the cmake configuration, I got some failed tests and highlight in green the line saying that the reentrant mode has been selected.

I use cmake because there seems to be an issue with the bootstrap.sh .

Autotools configuration worked fine on my laptop, but not on the server.

$ cmake .. -DBUILD_SHARED_LIBS=ON

-- The C compiler identification is GNU 10.2.1
-- The CXX compiler identification is GNU 10.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found GMP: /usr/include/x86_64-linux-gnu (Required is at least version "6.0.0")
-- Found MPFR: /usr/include (Required is at least version "1.0.0")
-- Found PythonInterp: /opt/miniconda3/bin/python (found version "3.9.12")
-- Found CBLAS: /usr/include/x86_64-linux-gnu  
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE  
-- Performing Test HAS_FLAG_MPOPCNT
-- Performing Test HAS_FLAG_MPOPCNT - Success
-- Performing Test HAS_FLAG_UNROLL_LOOPS
-- Performing Test HAS_FLAG_UNROLL_LOOPS - Success
-- Performing Test FLINT_USES_POPCNT
-- Performing Test FLINT_USES_POPCNT - Success
-- Performing Test FLINT_USES_FENV
-- Performing Test FLINT_USES_FENV - Success
-- Performing Test FLINT_USES_CPUSET
-- Performing Test FLINT_USES_CPUSET - Failed
-- Using FLINT memory manager: reentrant
-- Checking for IPO
-- Checking for IPO - found
-- Configuring done
-- Generating done
-- Build files have been written to: /dsk/l1/libraries/flint2/build

[Fredrik Johansson]

Hi Dimitri,

Thanks for reporting this. I think it should be changed to build single mode by default ("single" and "reentrant" are misnomers, because both are threadsafe these days). I created issue https://github.com/flintlib/flint2/issues/1392

Fredrik

--

---
You received this message because you are subscribed to the Google Groups "flint-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flint-devel...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/flint-devel/85245073-14fd-4a9d-81d0-d6f05040b417n%40googlegroups.com.

[Fredrik Johansson]

By the way, could you share the problem you're having with bootstrap.sh?

Is it the same as reported here: https://github.com/flintlib/flint2/issues/1386 ?

Fredrik

[Dimitri Lesnoff]

It is a little bit worse than what you describe in your issue. Running bootstrap.sh does not produce a ./configure, and running manually the commands given in the askUbuntu forum, I get similar warnings to the one you describe in your issue but it produces a ./configure. Finally, running a ./configure gives the no install.sh error.

Essentially it is the same issue.

Regards,

Dimitri