Closed paciorek closed 10 months ago
@paciorek I don't have immediate access to an M2 (or M1) Mac to test this on. The place where it comes up (line 227 of nimbleEigenNimArr.h) is in a templated function, meaning it is not compiled until it is used with specific types. My guess is that it is not compiled during package building and so was not caught when we cleaned up previous instances like this. And evidently the compiler setup on your M2 chooses to error instead of warn, which I have no idea about. Anyway it looks like it would be correct to replace "|" with "||" at that spot on line 227. I could be not seeing some deeper issue, but that might be all that is necessary.
Changing to ||
caused that specific error to disappear. The warnings remain, and I think we should understand why they are happening. I'm going to wait on that until we figure out the next item below.
More importantly, I'm now getting compilation failure because nimbleCppADbaseClass.o
(and corresponding .so file) is not being generated. I'm investigating that.
Ok, the compilation goes fine (not sure what was happening with nimbleCppADbaseClass.o
.
So the remaining question is the warnings about intermediate variables set but not used.
The warnings about typedefs are discussed in issue #1391
I'm going to close this and open a new issue about the warnings about intermediate variables.
I'm getting compilation issues on my new M2 Mac when trying to run
test-ADlaplace.R
. Strangely there are warnings about the bitwise|
that I thought we dealt with. Also, despite everything below seeming to be just warnings, the compilation fails.Using 1.0.1 things seem fine, as does using devel on an Intel-based Mac.
Failure occurs on the first test case: