build for 3.9.0#32
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 ( I do have some suggestions for making it better though... For recipe:
|
|
OK, this is failing with undefined symbols, e.g. OSX: There are a couple of patches upstream that address build errors (openblas also carried another bugfix, for example), maybe it'll be necessary to do that here as well? Windows OTOH errors even earlier |
|
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 ( I do have some suggestions for making it better though... For recipe:
|
|
@conda-forge-admin, please rerender |
|
Alright, with the switch to vs2017, windows is now building at least. :) It fails with which looks to be related to the errors when building on linux/osx: Looking into this a bit further, linux seems to be giving the clearest errors as to why that's happening. Seems the functions are only defined implicitly (note the different logs seem to be racy; the warning follows 1-2 lines too late): ... and so on for the other functions that error at link time. |
|
I looked into the functions upstream, and first found that all the function where the linker struggles have been set as deprecated in While both That's about as far as I got now... @conda-forge/lapack |
|
@h-vetinari do you mind removing me as a maintainer? |
Sure, I can do that. |
See conda-forge/pull/32#issuecomment-619091229
|
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 ( I do have some suggestions for making it better though... For recipe:
|
|
@conda-forge-admin, please rerender |
This was the right conclusion - it has been fixed upstream in Reference-LAPACK/lapack#367, but it doesn't look like they'll release 3.9.1 anytime soon, so I'm adding the patch. While I was at it, I also added a (cleaned-up) patch I saw being carried by openblas, and cleaned up the existing patches/diffs. |
|
@isuruf If there's something that I can make out, it's that the header function signature doesn't match the callsite signature, and we get errors like etc. |
|
Let's just go with the upstream patch. Sorry about the mess. |
1e72361 to
ac718ef
Compare
|
Since azure is gonna throw the logs away again (although let's see if the permalinks work; edit: nope), I'm recording another build error here on windows. This happens on linux/osx as well, but there it's just a warning: |
|
@conda-forge-admin, please rerender |
|
@isuruf @jjhelmus @mbargull, any comment on the following?
|
See conda-forge/pull/32#issuecomment-619091229
Turn .diff into actual patch and rebase on 3.9.0; move to /patches. Also remove unused 4-year-old patch
Fixes conda-forge#33 (see discussion there).
Co-Authored-By: Isuru Fernando <isuruf@gmail.com>
Since `{{ version }}` goes down to patch level, this doesn't changes
anything, but without it, there are warnings like:
Adding .* to spec 'libblas 3.9.0' to ensure satisfiability. Please consider putting
{{ var_name }}.* or some relational operator (>/</>=/<=) on this spec in meta.yaml,
or if req is also a build req, using {{ pin_compatible() }} jinja2 function instead.
See https://conda.io/docs/user-guide/tasks/build-packages/variants.html#pinning-at-the-variant-level
Also includes some fixes for regressions, bugs & undefined behaviour that are being carried by the OpenBLAS project.
…nda-forge-pinning 2020.09.04.10.00.02
|
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day! |
Carry some upstream patches (that were pending for #32)
Checklist
0(if the version changed)conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)Note: url for sources changed between 3.8.0 and 3.9.0.
Edit: Fix #33.