search

conda-forge / ifcopenshell-feedstock

A conda-smithy repository for ifcopenshell.
BSD 3-Clause "New" or "Revised" License
3 stars 6 forks source link

Rebuild for python311 #24

Closed regro-cf-autotick-bot closed 1 year ago

regro-cf-autotick-bot commented 1 year ago

This PR has been triggered in an effort to update python311.

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.

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. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/3431010810, please use this URL for debugging.

conda-forge-linter commented 1 year 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.

Krande commented 1 year ago

For some reason all the OSX builds suddenly stopped working :( They all finish the compilation stage, but grinds to a halt when it's time to do the packaging and ultimately times out. I've tried re-rendering a bunch of times, and also discarding the python 3.11 PR completely and requesting a new PR be made (which is this one).

FYI: Last PR that was merged was upgrading support for boost from v1.74 to v1.78. That PR did create some merge conflicts that I did manually resolve. So maybe I did something wrong there?

Or maybe it's something regarding the macOS SDK (we have a daily developer build of ifcopenshell compiled using github actions. The OSX conda build compiles and packages just fine there, but that's compiled on macOS 11 & 12). Before I go down the rabbit hole and try to experiment with newer macOS SDK's and stuff like that (looking at the docs) maybe it's best to follow the advice in the docs and ask the @conda-forge/core (I hope I'm using the tag system correctly?) team first for any help on debugging if this could be related to the macOS SDK's or if it is really something else? Any help on this would be much appreciated!

Best Regards Kristoffer

jakirkham commented 1 year ago

@conda-forge-admin, please re-render

jakirkham commented 1 year ago

@Krande , can you please take a look?

Upgraded the version of LIEF used to fix library linkages, which appears to have fixed the macOS builds