search

conda-forge / normaliz-feedstock

A conda-smithy repository for normaliz.
BSD 3-Clause "New" or "Revised" License
0 stars 4 forks source link

normaliz v3.8.1 #9

Closed regro-cf-autotick-bot closed 5 years ago

regro-cf-autotick-bot commented 5 years ago

It is very likely that the current package version for this feedstock is out of date. Notes for merging this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version. Checklist before merging this PR:
    • [ ] Dependencies have been updated if changed
    • [ ] Tests have passed
    • [ ] Updated license if changed and license_file is packaged

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 commented 5 years ago

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 (recipe) and found it was in an excellent condition.

saraedum commented 5 years ago

Let's try again once https://github.com/conda-forge/nauty-feedstock/pull/7 is in.

saraedum commented 5 years ago

@isuruf: So the upload failed at https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=79707 but 2.6.11 was pulled in anyway??

saraedum commented 5 years ago

I don't really know what's the problem here. But maybe asking for and ~extern "C"~ volatile from C just doesn't work.

saraedum commented 5 years ago

I wonder what happens when linking to it from C…

saraedum commented 5 years ago

Oh, that kill volatile is not inside the extern C block in nauty.h.

saraedum commented 5 years ago

Not sure whether I am allowed to redeclare here…

saraedum commented 5 years ago

No, I'm not:

A function can be re-declared without a linkage specification after it was declared with a language specification, the second declaration will reuse the first language linkage. The opposite is not true: if the first declaration has no language linkage, it is assumed "C++", and redeclaring with another language is an error.

saraedum commented 5 years ago

But the other way round should be fine.

isuruf commented 5 years ago

New warnings?

WARNING (normaliz,bin/normaliz): Needed DSO lib/libmpfr.so.6 found in ['mpfr']
WARNING (normaliz,bin/normaliz): .. but ['mpfr'] not in reqs/run, (i.e. it is overlinking) (likely) or a missing dependency (less likely)
   INFO (normaliz,bin/normaliz): Needed DSO lib/libstdc++.so.6 found in defaults::libstdcxx-ng-9.1.0-hdf63c60_0
WARNING (normaliz,bin/normaliz): Needed DSO lib/libarb.so.2 found in ['arb']
WARNING (normaliz,bin/normaliz): .. but ['arb'] not in reqs/run, (i.e. it is overlinking) (likely) or a missing dependency (less likely)
saraedum commented 5 years ago

Yes, it's overlinking: https://github.com/Normaliz/Normaliz/blob/master/configure.ac#L254