Skip to content
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

Rebuild for Python 3.7, GCC 7, R 3.5.1, openBLAS 0.3.2 #14

Closed

Conversation

regro-cf-autotick-bot
Copy link
Contributor

It is likely this feedstock needs to be rebuilt.
Notes and instructions for merging this PR:

  1. Please merge the PR only after the tests have passed.
  2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

This package has the following downstream children:

And potentially more.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one.

This PR was created by the cf-regro-autotick-bot.
The cf-regro-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable.
Finally, feel free to drop us a line if there are any issues!

@conda-forge-linter
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

  • The outputs section contained an unexpected subsection name. run_exports is not a valid subsection name.
  • The outputs section contained an unexpected subsection name. run_exports is not a valid subsection name.

@scopatz
Copy link
Member

scopatz commented Sep 22, 2018

I don't understand why we can't find certain packages on the new compilers.

conda.exceptions.ResolvePackageNotFound: 
  - openmp==5.0.0
  - clangdev==5.0.0
  - llvmdev==5.0.0
  - flang-meta

Any ideas @isuruf?

@isuruf
Copy link
Member

isuruf commented Sep 22, 2018

They are not built yet

@scopatz
Copy link
Member

scopatz commented Sep 22, 2018

Ahh weird that this was issued at all then

@rth
Copy link
Member

rth commented Nov 7, 2018

we can't find certain packages on the new compilers.

Currently, the only remaining one is openmp in conda-forge/openmp-feedstock#14 .

flang-meta doesn't need to be rebuilt, does it?

@SylvainCorlay
Copy link
Member

Ahh weird that this was issued at all then

This was issued because llvmdev and clangdev 7.x were rebuilt

I have run the migration for the 6.x stack. The 5.x stack is still missing clangdev because of a bug in conda-build.

@rth
Copy link
Member

rth commented Nov 7, 2018

The 5.x stack is still missing clangdev because of a bug in conda-build.

Right, conda-forge/clangdev-feedstock#41 thanks for the details!

@h-vetinari
Copy link
Member

@conda-forge-admin, please rerender

@h-vetinari
Copy link
Member

Seems like compilation runs through, but fails to find crti.o:

[...]
[100%] Linking Fortran static library ../../lib/libflang.a
[100%] Built target flang_static
[100%] Linking Fortran shared library ../../lib/libflang.so
/usr/bin/ld: crti.o: No such file: No such file or directory
clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [lib/libflang.so] Error 1
make[1]: *** [runtime/flang/CMakeFiles/flang_shared.dir/all] Error 2
make: *** [all] Error 2

PS. I became interested in this PR since it's the only open one and flang still depends on llvm=5.0.0, which then makes it impossible to install with more current openmp:

> conda install "openmp>=8" "openblas>=0.3.7"
[...]
Package clangdev conflicts for:
openblas[version='>=0.3.7'] -> libflang[version='>=5.0.0'] -> openmp==5.0.0 -> clangdev[version='5.0.0|5.0.0.*']
Package llvm-meta conflicts for:
openblas[version='>=0.3.7'] -> libflang[version='>=5.0.0'] -> openmp==5.0.0 -> llvm-meta[version='5.0.0|5.0.0.*']
Package llvm-openmp conflicts for:
openmp[version='>=8'] -> llvm-openmp[version='8.0.0|8.0.1',build='h1ad3211_0|h1ad3211_1|h1ad3211_0']
Package openmp conflicts for:
openblas[version='>=0.3.7'] -> libflang[version='>=5.0.0'] -> openmp==5.0.0
openmp[version='>=8']

I also checked the current state of the upstream which hasn't been updated in 1.5yrs, but it seems that things are still slowly progressing.

@h-vetinari
Copy link
Member

Closing this one as (very) outdated.

@h-vetinari h-vetinari closed this Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants