-
-
Notifications
You must be signed in to change notification settings - Fork 7
6.1.4 again #23
base: main
Are you sure you want to change the base?
6.1.4 again #23
Conversation
patch mostly based on the patch by dougalsutherland
…nda-forge-pinning 2020.05.11.16.49.47
…da-forge-pinning 2020.05.13.13.23.43
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 ( |
…da-forge-pinning 2020.05.13.13.23.43
…da-forge-pinning 2020.05.13.13.23.43
Failing on Linux with Something wonky is going on with the build system here...any ideas @vigsterkr? |
Also, hmm – as is, I think it's using the generic blas version of |
@djsutherland yep.... still the same problem... see #18 (comment) and messages after |
Hmm, I missed all of that. I'll try a new shogun-cpp build with the newest conda-build, just in case that helps, since there's an update I wanted to make anyway (conda-forge/shogun-cpp-feedstock#38).... |
Okay, new builds didn't help
|
Sorry to bug, @isuruf / @mingwandroid, but I missed the whole thing with path rewriting in 3.18.12 and am not sure how to proceed from here with
even though the build of (Doesn't seem like it should be relevant, but I checked and |
I haven't checked if conda-build has a bug here or not. A workaround would be to do |
@djsutherland the python3.8 looks like a typical swig problem. |
Trying to further #18 here, since that doesn't have "allow edits by maintainers" checked.
@vigsterkr: the reason it was picking up the old ones is because the new
shogun-cpp
builds have had theirarpack
andhdf5
migrated, while #18 hasn't. I applied those migrations here, and now it's getting the new builds; let's see if that worked.Closes #18, closes #13, closes #15, closes #17, closes #20, closes #19.