Richard Berger

I can confirm that this is a valuable feature. In the past it would already have been helpful if an included file could have other includes as well. In my...

The current CI failures match what I'm observing in my projects. `Boost::stacktrace` isn't defined, although the documentation claims: > CMake library Boost::stacktrace provides the best available implementation:

I don't think only removing the launch compiler is enough. All compile and link options in `Kokkos::kokkoscore` need to be guarded via [generator expressions](https://cmake.org/cmake/help/latest/manual/cmake-generator-expressions.7.html#genex:COMPILE_LANG_AND_ID) for matching the Kokkos compiler (and...

And how would one get Kokkos include headers for CPU only portions that aren't compiler specific?

@JBludau Ok, fair. So what you're saying is, this should be enough for a project to create a single subdirectory/target with launch compiler activated to act as a shim for...

Bisecting shows that the concretization was "better" before 4743171d6c26458eb3a7e66f46c4e24f25a5ab40 and it chooses meaningful package versions. However, the preference to `clang` is ignored and `gcc` always wins. Which would indicate the...

I have similar use cases and I started looking into adding that feature.

> but we may want to strongly suggest the user set ControlMaster auto @sethrj I now give a warning if I detect ControlMaster isn't turned on.

@teissler Coming late to the party, but.... that's not a bug, just a typo in the import command line used. It should be `--arch=x86_64` instead of `--arch x86_64`: ``` cobbler...

@teissler I had the error when I imported the mounted ISO with the typo. It disappeared without the typo. Sorry I jumped to conclusions. I’ll check again with a full...