spack: Missing libisl when installing gcc@5.4.0 on system gcc@5.4.0

Following the spack install instructions for PIConGPU, an error occurs when installing gcc via

spack install gcc@5.4.0

Expected Result

gcc 5.4.0 is installed succesfully

Actual Result

==> Installing gcc
==> Fetching http://ftp.gnu.org/gnu/gcc/gcc-5.4.0/gcc-5.4.0.tar.bz2
[ ... ]
==> Error: ProcessError: Command exited with status 2:
    'make' '-j8'

6 errors found in build log:
[ ... ]
  >> 15250 /tmp/berceanu/spack-stage/spack-stage-e9ZEMa/gcc-5.4.0/spack-build/./gcc/cc1: error while loading shared libraries: libisl.so.13: cannot open shared object file: No such file or directory
[ ... ]
  >> 15370 checking for suffix of object files... configure: error: in `/tmp/berceanu/spack-stage/spack-stage-e9ZEMa/gcc-5.4.0/spack-build/x86_64-unknown-linux-gnu/libgcc':
  >> 15371 configure: error: cannot compute suffix of object files: cannot compile
     15372 See `config.log' for more details.
     15373 Makefile:16271: recipe for target 'configure-stage2-target-libgcc' failed
  >> 15374 make[2]: *** [configure-stage2-target-libgcc] Error 1
     15375 make[2]: Leaving directory '/tmp/berceanu/spack-stage/spack-stage-e9ZEMa/gcc-5.4.0/spack-build'
     15376 Makefile:20856: recipe for target 'stage2-bubble' failed
  >> 15377 make[1]: *** [stage2-bubble] Error 2
     15378 make[1]: Leaving directory '/tmp/berceanu/spack-stage/spack-stage-e9ZEMa/gcc-5.4.0/spack-build'
     15379 Makefile:902: recipe for target 'all' failed
  >> 15380 make: *** [all] Error 2

Steps to reproduce the issue

git clone https://github.com/spack/spack.git $HOME/src/spack
source $HOME/src/spack/share/spack/setup-env.sh
spack bootstrap
spack install gcc@5.4.0

Information on your system

$ uname -m && cat /etc/*release
x86_64
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS"
NAME="Ubuntu"
VERSION="16.04.3 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.3 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
$ gcc --version
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.5) 5.4.0 20160609
$ uname -a
Linux berceanu-GL552JX 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Reactions: 1
  • Comments: 21 (14 by maintainers)

Commits related to this issue

Most upvoted comments

GCC 7.3 works, with mpfr up to 3.1.6 and isl up to 0.18. GCC 5.4 works, with mpfr up to 3.1.6 and isl@0.15.

Gosh, due to the CUDA constrains on host compilers and this bug, the only way I can make sure users are getting a specific version of GCC would be to ask them to do something like this in our instructions:

spack compiler list | grep gcc@5.4.0 || spack install gcc@5.4.0 && spack load gcc@5.4.0 && spack compiler add

related: #5101

@ax3l, here is ~/src/spack/var/spack/stage/gcc-5.4.0-76obpu3dy6lc3chia6xjdoqyciy6guci/gcc-5.4.0/spack-build.out, and here is /tmp/berceanu/spack-stage/spack-stage-O98UI4/gcc-5.4.0/spack-build/config.log.

I realize I can use the system’s gcc, but I’m guessing other users will also run into this problem when following the install instructions 😃

I just took the max one in ftp://gcc.gnu.org/pub/gcc/infrastructure/. I tested, it’s safe to bump up to 3.1.6.

Setting this

    #depends_on('isl@0.15:', when='@6:')
    depends_on('isl@0.15:0.18', when='@6:8.9')
    depends_on('isl@0.15:0.20', when='@9:')

in ./src/spack/var/spack/repos/builtin/packages/gcc/package.py seems to work.

However, I also needed to limit mpfr to

#depends_on('mpfr@2.4.2:')
depends_on('mpfr@2.4.2:3.1.4')

as 4.0.1 did not work with isl 0.18. mpfr 3.1.4 also seems to be the highest version in GCC’s auto-boundle install scripts (ftp://gcc.gnu.org/pub/gcc/infrastructure/)

Just to clarify, you’re using the system GCC 5.4.0 to install GCC 5.4.0 with Spack? While this isn’t a bad idea, you certainly don’t need to do this if you are running into problems. You can just use the system GCC for all of your installs if you want to.

Can you post the output of the following command:

$ spack config get compilers

I just want to make sure your compilers.yaml is set up correctly.

@ax3l may be interested in this issue.