Conversation
8328be6 to
23c7e0a
Compare
| url = "https://github.com/flame/libflame/archive/5.1.0.tar.gz" | ||
| git = "https://github.com/flame/libflame.git" | ||
|
|
||
| version('develop', branch='master') |
There was a problem hiding this comment.
You can just call this version master if you want.
There was a problem hiding this comment.
Isn't the convention in spack develop>[numeric versions]>all other string versions ? Since the last release was so long ago, I'd prefer to keep it as develop unless I'm missing sth.
There was a problem hiding this comment.
That was the convention, until #1983 was merged. Now develop > master > numeric versions > all other string versions.
There was a problem hiding this comment.
Great! , it used to cause a lot confusion outside spack as to why is spack calling a version develop when the package developers call it master.
|
|
||
| provides('lapack', when='+lapack2flame') | ||
|
|
||
| variant('lapack2flame', default=True) |
| variant('lapack2flame', default=True, | ||
| description='Map legacy LAPACK routine invocations | ||
| to their corresponding native C implementations | ||
| in libflame.') |
There was a problem hiding this comment.
This will result in extra spaces in spack info. You'll have to either put the entire variant on one line, or wrap it with more quotes.
new file: var/spack/repos/builtin/packages/libflame/Makefile_5.1.0.patch new file: var/spack/repos/builtin/packages/libflame/package.py
eebc8c4 to
d1c8d8b
Compare
|
I tried building this and got the following error during Any idea how to fix this? |
|
Have a look at the advice given here : flame/libflame#21 Did you get this error for master or release? I implemented the above for master since release didn’t have any issues. |
|
I got the error for the latest release. I'll try adding that flag for all versions. |
|
I tried the latest release again with that flag but now I'm seeing a completely different problem: Going to try |
|
Nope, I give up. |
|
Do you want me to test this with clang on CentOS ? I'm not sure how MacOS/Clang deal with the While I don't have access to a mac build-env, I see no issues on CentOS 7.5 : |
|
With my latest commit in #12170, I've gotten a little closer to building EDIT: This is on CentOS 7 with GCC 4.8.5. On macOS 10.14.5, with Clang 10.0.1, I'm getting: This is even with the max arg hack flag. |
|
Was the error for release or master on mac ? Looks like a fix was commited in master as per flame/libflame#3. With your latest commit, I see : Edit : I see an error for the release branch as well with #12170. I've opened an issue upstream : flame/libflame#22 |
|
I tried the patches listed in flame/libflame#3 but still got the same max arg list error. The master branch got a lot closer on macOS but I still got: I was able to build |
* Add libflame new file: var/spack/repos/builtin/packages/libflame/Makefile_5.1.0.patch new file: var/spack/repos/builtin/packages/libflame/package.py * modified: var/spack/repos/builtin/packages/libflame/package.py
Add the libflame package that provides LAPACK functionality. To be included as a new interface for Numpy-1.17.0
Note that libflame does not have a blas dependency and one would have to set independently.
@adamjstewart