Building from source on Rocky 8.10 eigen3 library not found

[trevorkarn]

I am trying to install from source on a Rocky 8.10 system which I don't have admin access on.

I tried following the directions at https://macaulay2.com/Downloads/SourceCode/, cloned from GitHub into ~/M2/ and ran

cd ${HOME}/M2/M2
make 
mkdir ${HOME}/M2/M2/BUILD/foo
cd ${HOME}/M2/M2/BUILD/foo
../../configure --prefix=${HOME}/local CPPFLAGS="-I/${HOME}/local/include" LIBS="-L/${HOME}/local/lib64/"

I initially had issues with tbb, but followed #3055, and installed the newest version of tbb using cmake following https://github.com/oneapi-src/oneTBB/blob/master/INSTALL.md. I did use -DCMAKE_INSTALL_PREFIX=${HOME}/local since I don't have admin access. That solved the tbb problem.

After solving the tbb problem, I again ran

../../configure --prefix=${HOME}/local CPPFLAGS="-I/${HOME}/local/include" LIBS="-L/${HOME}/local/lib64/"

from M2/BUILD/foo. Then I got the error

checking whether eigen3 library is installed... configure: error: eigen library not found

and the build stopped. I tried building the eigen3 library but that did not work for some reason. I think that eigen3 did install, because I am able to run the toy program from https://eigen.tuxfamily.org/dox/GettingStarted.html that prints a matrix by running

% g++ -I ${HOME}/local/include/eigen3 my_program.cpp -o my_program
% ./my_program 
  3  -1
2.5 1.5

I would have thought that setting CPPFLAGS="-I/${HOME}/local/include" would have been enough to fix the problem, but I am wrong.

[d-torrance]

Does CPPFLAGS="-I/${HOME}/local/include/eigen3 help?

[mahrud]

@d-torrance should autotools build also have a target to download/configure/install eigen? (it's a header-only library so there's nothing to build really)

[trevorkarn]

I ended up doing

 export PKG_CONFIG_PATH=${HOME}/local/share/pkgconfig/
 export LD_LIBRARY_PATH=${HOME}/local/lib64

and running

 ../../configure --prefix=${HOME}/local CPPFLAGS="-I/${HOME}/local/include" LDFLAGS="-L/${HOME}/local/lib64/ -L/${HOME}/local/lib" --without-libffi --enable-download

I then ran make and that seems to be working, but the build has not completely finished yet.

[d-torrance]

should autotools build also have a target to download/configure/install eigen?

Yeah, that's a good idea.

[mahrud]

@trevorkarn did the build succeed? I added a reference to this issue in the wiki. Feel free to add any other details that would be helpful for people building M2 on RHEL in the future.

[trevorkarn]

It did not succeed. I am now struggling with GIVARO

[d-torrance]

For what it's worth, once #3487 is merged, eigen should be discovered without having to mess with pkg-config, so long as it's installed in a standard header directory or CPPFLAGS is set correctly. And if it's not found, then it will be installed automatically in the build directory. (It's also possible to avoid this entirely on RHEL by installing the eigen3 package from EPEL.)

What specific givaro issues are you having? I've also been trying to get the build to work in RHEL 8, ideally before the next release, but there are lots of little issues like this since so few packages are available in the RHEL repositories.

[trevorkarn]

I installed givaro, by following https://github.com/linbox-team/givaro?tab=readme-ov-file#download-and-install with

./autogen.sh --prefix=${HOME}/givaro

I am again having trouble configuring. I tried

export PKG_CONFIG_PATH=${HOME}/local/share/pkgconfig/:${HOME}/local/lib64/pkgconfig/:${HOME}/givaro/lib/pkgconfig
export LD_LIBRARY_PATH=${HOME}/local/lib64
export GIVARO_LIBS=${HOME}/givaro/include
../../configure --prefix=${HOME}/local CPPFLAGS="-I/${HOME}/local/include" LDFLAGS="-L/${HOME}/local/lib64/ -L/${HOME}/local/lib" --without-libffi --enable-download

and get the error

checking whether getaddrinfo can handle numeric service (port) numbers... configure: error: test file failed to compile

If I ignore that error, and run make anyway, since I think a previous configuration seemed to work (how do I check that?), I get

...
## --------------------------------------- ##
##        START FFLAS-FFPACK CONFIG        ##
## --------------------------------------- ##
checking for family name of compiler... checking whether g++ supports C++11 features by default... yes
---------------------------------------
checking whether to enable debugging options in the library... no
checking whether to enable profiling everything in the library... no
checking whether to enable warnings when compiling the library... no
checking whether C++ compiler accepts -march=native... yes
configure: "Adding '-march=native' to OPTIM_FLAGS"
---------------------------------------
checking size of char... 1
checking size of short... 2
checking size of int... 4
checking size of long... 8
checking size of long long... 8
checking size of __int64_t... 8
checking for __int128_t... yes
checking whether byte ordering is bigendian... no
---------------------------------------
checking for OpenMP... no
Default path = /usr /usr/local
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GIVARO... yes
checking for GIVARO usability... no
configure: error: The Givaro library could not be used with the compiler and the flags set up by the configure script
make: *** [GNUmakefile:211: submodules/fflas_ffpack/Makefile] Error 1

[trevorkarn]

I reinstalled givaro in ~/local using ./autogen.sh --prefix=${HOME}/local instead of what I did above. Then things get further:

% cd ~/M2/M2/BUILD/foo
% export PKG_CONFIG_PATH=${HOME}/local/share/pkgconfig/:${HOME}/local/lib64/pkgconfig/:${HOME}/local/lib/pkgconfig/
% make

which gives output ending in

## --------------------------------------- ##
##        START FFLAS-FFPACK CONFIG        ##
## --------------------------------------- ##
checking for family name of compiler... checking whether g++ supports C++11 features by default... yes
---------------------------------------
checking whether to enable debugging options in the library... no
checking whether to enable profiling everything in the library... no
checking whether to enable warnings when compiling the library... no
checking whether C++ compiler accepts -march=native... yes
configure: "Adding '-march=native' to OPTIM_FLAGS"
---------------------------------------
checking size of char... 1
checking size of short... 2
checking size of int... 4
checking size of long... 8
checking size of long long... 8
checking size of __int64_t... 8
checking for __int128_t... yes
checking whether byte ordering is bigendian... no
---------------------------------------
checking for OpenMP... no
Default path = /usr /usr/local
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GIVARO... yes
checking for GIVARO usability... yes
---------------------------------------
checking for use of MKL... no 
checking for BLAS... problem
*******************************************************************************
 ERROR: BLAS not found!
 BLAS routines are required for this library to compile. Please
 make sure BLAS are installed and specify its location with the option
 --with-blas-libs=<libs> and if necessary --with-blas-cflags=<cflags>
 when running configure.
*******************************************************************************
make: *** [GNUmakefile:211: submodules/fflas_ffpack/Makefile] Error 1
make: Leaving directory '/users/0/karnx018/M2/M2/BUILD/foo'

[d-torrance]

You shouldn't have to build givaro yourself -- the M2 build script will do it for you.

That being said, I'm getting stuck at the same spot you are. The BLAS part of the autotools build needs an overhaul -- I'm hoping to work on that soon.

[trevorkarn]

How do I tell which things I should have to build myself and which things the M2 build script will/is supposed to do for me?

I didn't have BLAS installed, so I am trying to install BLAS from source now.

[d-torrance]

Basically, if you get an error before configure finishes (like the one you were getting with eigen), then the M2 build script expects it to be installed already. If configure finishes without an error, then it will build everything that it needs. You can see the list of things it will build by looking for this output towards the end:

configure: using BUILDLIST     =  gc gmp mpfi normaliz ntl flint factory lapack mpsolve frobby glpk cddlib givaro fflas_ffpack gtest memtailor mathic mathicgb eigen 4ti2 gfan csdp nauty lrslib gftables topcom cohomcalg msolve

If you build BLAS manually, then you might be able to point fflas-ffpack in the right direction by modifying M2/libraries/fflas_ffpack/Makefile.in and adding CONFIGOPTIONS += --with-blas-libs=... --with-blas-cflags=....