spack / spack

A flexible package manager that supports multiple versions, configurations, platforms, and compilers.

Home Page:https://spack.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Installation issue: libtool from buildcache keeps CI compiler wrapper

pranav-sivaraman opened this issue · comments

Steps to reproduce the issue

$ spack spec -I libtool
Input spec
--------------------------------
 -   libtool

Concretized
--------------------------------
[+]  libtool@2.4.7%apple-clang@15.0.0 build_system=autotools arch=darwin-ventura-aarch64
[+]      ^findutils@4.9.0%apple-clang@15.0.0 build_system=autotools patches=440b954 arch=darwin-ventura-aarch64
[+]      ^gmake@4.4.1%apple-clang@15.0.0~guile build_system=generic arch=darwin-ventura-aarch64
[+]      ^gnuconfig@2022-09-17%apple-clang@15.0.0 build_system=generic arch=darwin-ventura-aarch64
[+]      ^m4@1.4.19%apple-clang@15.0.0+sigsegv build_system=autotools patches=9dc5fbd,bfdffa7 arch=darwin-ventura-aarch64
[+]          ^diffutils@3.10%apple-clang@15.0.0 build_system=autotools arch=darwin-ventura-aarch64
[+]              ^libiconv@1.17%apple-clang@15.0.0 build_system=autotools libs=shared,static arch=darwin-ventura-aarch64
[+]          ^libsigsegv@2.14%apple-clang@15.0.0 build_system=autotools arch=darwin-ventura-aarch64

Error message

Error message Just some examples of wrong variable set found in the libtool
# A language specific compiler.
CC="/Users/gitlab-runner-p-0/builds/axdaqY6y/0/spack/spack/lib/spack/env/clang/clang"
# A language specific compiler.
CC="/Users/gitlab-runner-p-0/builds/axdaqY6y/0/spack/spack/lib/spack/env/clang/gfortran"

Information on your system

  • Spack: 0.22.0.dev0 (4a40a76)
  • Python: 3.9.6
  • Platform: darwin-sonoma-m1
  • Concretizer: clingo

Additional information

I ran into this issue when libtool was a dependency and the build crashed because of the invalid compiler paths.

General information

  • I have run spack debug report and reported the version of Spack/Python/Platform
  • I have run spack maintainers <name-of-the-package> and @mentioned any maintainers
  • I have uploaded the build log and environment files
  • I have searched the issues of this repo and believe this is not a duplicate

Since this is package is tagged as build-tools maybe we should not put them in the build cache?

Sort of related to this issue. I think in the context of the buildcache might be to just not include it.