On 30/01/2017 16:03, Satish Sherikar wrote:
Hi,

I dont understand where it is coming from. I have manually configured HDF5 with same command as used by easybuild while configuration. But at this time it ran successfully. By using eb command only it is giving me an error.

If you required any other data i'll provide you.

Try running the 'eb' command you're using with '-x'. The resulting output will include a set of commands to define the build environment as it is set up by EasyBuild.
Maybe something in there is messing up the build?


I have attached config.log of manual configuration with same configuration command.

The config.log you provided doesn't seem to be the correct one; that configure command exited with exit status 0, and there was no mention of libbat.so at all.

And can you please provide me how to create my own/dummy toolchain for this cluster. ( Preffered intel toolchain)

There's (outdated) documentation available at https://github.com/hpcugent/easybuild/wiki/Compiler-toolchains, but you should reconsider this probably.

It's recommended to use a toolchain that is commonly used in the community, see for example http://easybuild.readthedocs.io/en/latest/Common-toolchains.html.

It seems like you also want to just use readily available compilers/libraries rather than installing the toolchain itself using EasyBuild?


regards,

Kenneth


Regards,
Satish

On Mon, Jan 30, 2017 at 6:19 PM, Robert Schmidt <rjesc...@gmail.com <mailto:rjesc...@gmail.com>> wrote:

    libbat.so is part of LSF. It is probably included somewhere in the
    environment. It is pretty "messy" so perhaps there is an
    LD_LIBRARY_PATH that was set before easybuild took over that
    normally handled making sure it is available?

    On Mon, Jan 30, 2017 at 7:48 AM Ward Poelmans <wpoel...@gmail.com
    <mailto:wpoel...@gmail.com>> wrote:

        Hi Satish,

        On Mon, Jan 30, 2017 at 1:36 PM, Satish Sherikar
        <sherikar1...@gmail.com <mailto:sherikar1...@gmail.com>> wrote:
        > Hi Ward,
        >
        > I have attached config.log for HDF5.
        >
        > We are using mpiicc, mpiifort and mpiif90 in our cluster.
        But it is taking
        > FC=mpif90.
        >
        > I didnt understand how to change all these.

        You are building HDF5 with the `goolf` toolchain. This
        combines GCC
        with OpenMPI and that's the reason why EB is using mpif90.

        If you want to use the intel compilers, you must use the `intel`
        toolchain. I see both have it in your PATH already. EB cannot
        use this
        directly: it wants a intel installation done by EB itself.


        The HDF5 configure scripts fails because of:
        configure:4476: mpicc -o conftest  -O2 -march=native -fPIC
        
-I/gpfs1/home/ibm/.local/easybuild/software/OpenBLAS/0.2.6-gompi-1.4.10-LAPACK-3.4.2/include
        
-I/gpfs1/home/ibm/.local/easybuild/software/ScaLAPACK/2.0.2-gompi-1.4.10-OpenBLAS-0.2
        .6-LAPACK-3.4.2/include
        
-I/gpfs1/home/ibm/.local/easybuild/software/FFTW/3.3.3-gompi-1.4.10/include
        
-I/gpfs1/home/ibm/.local/easybuild/software/zlib/1.2.7-goolf-1.4.10/include
        -I/gpfs1/home/ibm/.local/easybuild/software/Szip/2.1-goolf-1.4
.10/include -L/gpfs1/home/ibm/.local/easybuild/software/GCC/4.7.2/lib64
        -L/gpfs1/home/ibm/.local/easybuild/software/GCC/4.7.2/lib
        
-L/gpfs1/home/ibm/.local/easybuild/software/OpenBLAS/0.2.6-gompi-1.4.10-LAPACK-3.4.2/lib
        -L/gpfs1/home/ibm/
        
.local/easybuild/software/ScaLAPACK/2.0.2-gompi-1.4.10-OpenBLAS-0.2.6-LAPACK-3.4.2/lib
        -L/gpfs1/home/ibm/.local/easybuild/software/FFTW/3.3.3-gompi-1.4.10/lib
        -L/gpfs1/home/ibm/.local/easybuild/software/zlib/1.2.7-goolf-1.4.10/lib
        -L/gpfs
        1/home/ibm/.local/easybuild/software/Szip/2.1-goolf-1.4.10/lib
        conftest.c -lm -lpthread >&5
        configure:4480: $? = 0
        configure:4487: ./conftest
        ./conftest: error while loading shared libraries: libbat.so:
        cannot
        open shared object file: No such file or directory


        I've never heard of `libbat.so` and it doesn't get linked in.
        Any idea
        where it comes from?

        Ward



Reply via email to