diff options
author | Greg Becker <becker33@llnl.gov> | 2022-11-02 21:09:43 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-11-02 21:09:43 -0700 |
commit | c716c6ca95e300ac247f668237fc13f75e1b5289 (patch) | |
tree | c83a7ef527d8bb89da1fd87325ffc685b2b7074c /bin/spack.bat | |
parent | b652fe72d7a55150813c6ffbb68e9c724737fc0a (diff) | |
download | spack-c716c6ca95e300ac247f668237fc13f75e1b5289.tar.gz spack-c716c6ca95e300ac247f668237fc13f75e1b5289.tar.bz2 spack-c716c6ca95e300ac247f668237fc13f75e1b5289.tar.xz spack-c716c6ca95e300ac247f668237fc13f75e1b5289.zip |
Bugfix for spec objects modified by flag handlers (#33682)
This issue was introduced in #29761:
```
==> Installing ncurses-6.3-22hz6q6cvo3ep2uhrs3erpp2kogxncbn
==> No binary for ncurses-6.3-22hz6q6cvo3ep2uhrs3erpp2kogxncbn found: installing from source
==> Using cached archive: /spack/var/spack/cache/_source-cache/archive/97/97fc51ac2b085d4cde31ef4d2c3122c21abc217e9090a43a30fc5ec21684e059.tar.gz
==> No patches needed for ncurses
==> ncurses: Executing phase: 'autoreconf'
==> ncurses: Executing phase: 'configure'
==> ncurses: Executing phase: 'build'
==> ncurses: Executing phase: 'install'
==> Error: AttributeError: 'str' object has no attribute 'propagate'
The 'ncurses' package cannot find an attribute while trying to build from sources. This might be due to a change in Spack's package format to support multiple build-systems for a single package. You can fix this by updating the build recipe, and you can also report the issue as a bug. More information at https://spack.readthedocs.io/en/latest/packaging_guide.html#installation-procedure
/spack/lib/spack/spack/build_environment.py:1075, in _setup_pkg_and_run:
1072 tb_string = traceback.format_exc()
1073
1074 # build up some context from the offending package so we can
>> 1075 # show that, too.
1076 package_context = get_package_context(tb)
1077
1078 logfile = None
```
It turns out this was caused by a bug that had been around much longer, in which the flags were passed by reference to the flag_handler, and the flag_handler was modifying the spec object, not just the flags given to the build system. The scope of this bug was limited by the forking model in Spack, which is how it went under the radar for so long.
PR includes regression test.
Diffstat (limited to 'bin/spack.bat')
0 files changed, 0 insertions, 0 deletions