spack: Failed to bootstrap pkg-config with pgi compiler
I failed to bootstrap pkg-config with pgi@16.10. The error says “PGC-F-0249-#error – Your platform/compiler is missing constructor support (glib-init.c: 284)”. Shall I submit a bug report to pkg-config?
$ spack purge; spack clean pkg-config; spack install pkg-config %pgi@16.10
==> Installing pkg-config
==> Using cached archive: /tmp/rpm/spack_source_cache/pkg-config/pkg-config-0.29.1.tar.gz
==> Already staged pkg-config-0.29.1-acbcjyz6mwiu7fnleuuatbxolunoszhl in /home/rpm/spack/var/spack/stage/pkg-config-0.29.1-acbcjyz6mwiu7fnleuuatbxolunoszhl
==> Already patched pkg-config
==> Building pkg-config [Package]
==> Executing phase : 'install'
==> Error: ProcessError: Command exited with status 2:
'make'
/home/rpm/spack/var/spack/repos/builtin/packages/pkg-config/package.py:63, in install:
53 def install(self, spec, prefix):
54 args = ["--prefix={0}".format(prefix),
55 "--enable-shared"]
56 if "+internal_glib" in spec:
57 # There's a bootstrapping problem here;
58 # glib uses pkg-config as well, so break
59 # the cycle by using the internal glib.
60 args.append("--with-internal-glib")
61 configure(*args)
62
>> 63 make()
64 make("install")
See build log for details:
/tmp/rpm/spack_stage/spack-stage/spack-stage-w24BST/pkg-config-0.29.1/spack-build.out
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Comments: 18 (17 by maintainers)
Ran into this issue when trying to install
openmpi@3.1.2withpgi@19.10. I pointed spack to the system installed pkg-config (@0.27.1), but very quickly ran into another error when buildinglibpciaccess@0.13.5regarding undefined references toinw,outw,inb,outb,inl, andoutlinlibpciaccess.so. I’m not sure if this is related to using an older pkg-config or if it’s completely unrelated, but it would be nice if spack was able to install pkg-config in order to help debug this issue.I’ve ran into this bug as well but hadn’t yet gotten around to submitting a bug report. You’re actually better off submitting a bug report to the glibc developers. pkg-config depends on glibc, but glibc depends on pkg-config. The developers realized this would cause a circular dependency, so pkg-config contains glibc in one of its sub-directories. If the glibc developers give you a patch for glibc, you can also apply it to the pkg-config package. PGI is a much stricter compiler than GCC, so I’m not surprised it doesn’t build glibc. I’ve found developers to be fairly responsive about PGI patches.