-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MNT: rerender #248
MNT: rerender #248
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
…nda-forge-pinning 2023.05.23.18.17.57
@mkitti any idea about this error?
|
What happened to the compiler? |
Compiler versions were upgraded as we move them in conda-forge: on osx64: |
No, I mean the Julia compiler
|
Yeah, but we are merely reusing the same tar that used to build fine. So the issue is from our end (compilers), right? I wonder if julia isn’t happy with the new compilers for some reason. We can specify a specific c/cxx version easily if we have to |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2023.05.25.07.41.09
Btw, @mkitti we will move to follow your suggestion of using the official tar (instead of the github one) the next time we merge a PR (either this or the 1.9 one) |
This reverts commit 47060d4.
…nda-forge-pinning 2023.05.25.07.41.09
The warning here looks problematic.
|
Yeah, I am quite confused about what triggered this though. It’s not the change of compilers and it’s an unlikely a change in the tar ball. I will try to see if conda-forge’s build system or patchelf has changed recently |
…nda-forge-pinning 2023.05.25.16.15.35
Julia 1.8.5 uses rpath
Julia 1.9.0 uses runpath
|
Julia 1.8.5
Julia 1.9.0
|
See also JuliaLang/julia#46255 which was not backported to Julia 1.8 |
Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #246.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.