Geoffrey Oxberry

Adding #415 to this thread.

Related upstream `spack` PR for `py-fprettify`: https://github.com/spack/spack/pull/19699

I've also run into this bug. Definitely worth sending a fix.

I've run into these issues with LiDO and normally kludge around it (the typical offender is `tensor_unit_tests`) -- psyched to see a fix land in upstream.

> Similarly, I think "aarch64" is the appropriate entry for "target" on the newer machines On an M1 Mac, I'd use `arch=m1`. > but I couldn't find good information about...

> > I'm dreading having to manually go into that packages.yaml file and manually edit the specific directories and versions of each of the 17 packages. Why do I have...

> It seems untenable that our build system requires a human to manually specify that readline is at exactly version 8.1.2.000. The argument that this sort of thing is necessary...

I've tried to add some additional comments where parts of config files can be automatically generated using Spack commands. All of the comments assume use of whatever the commit of...

@white238 No problem! I agree; environments have the potential to clean up build instructions significantly.

Managed to get bfd support working also, and native system libunwind support.