Seth R. Johnson

Hi @tclune , since I made my (pretty minor, infrastructure-only) contribution through my official ORNL duties, I spoke to our lab's IP law group, which declines to sign the contract....

@eyalroz I had to make some changes to your tentative span to get it to compile with `nvcc` (some errors, some warnings). ```diff diff --git a/span.h b/span.h index 380402b..41a20da 100644...

Yuck. Literally an hour ago I also hit a trilinos/xpetra/muelu build error (https://github.com/spack/spack/pull/17971). Can you try building trilinos with `gotype=long_long`? I heard a rumor that the `` instantiation will eventually...

The trilinos spack recipe sets `gotype=long` by default, so that's why you're getting `-DTpetra_INST_INT_LONG:BOOL=ON`. It also looks like you're getting `Tpetra_INST_INT_INT` turned on as well, which seems impossible from the...

@amklinv-nnl For any selection of variants/dependencies that causes a build/configure error, you should add a `conflicts` statement to the package recipe. Because Trilinos has a basically boundless list of variants...

@keitat Don't you want `gotype=long_long`? I thought that Trilinos 13 was moving to hard-coding long long for global types.

Ask them "what's the deal.II with using `gotype=int`" 😆

@jwillenbring @aprokop Apparently I misunderstood our conversation about global/local type simplification in Trilinos 13. I thought Trilinos was moving to hardcode `int32_t, uint64_t` for the local/global pairs and remove a...

Excellent, thanks @jwillenbring ! It sounds like the change is that *multiple* simultaneous types will no longer be supported (this is consistent with the spack Trilinos package), and that the...

@keitat Did anything ever come of the index data type interview? I hit this issue recently because e4s is installed on spock with `trilinos gotype=long`, but some of our software...