Skip to content

6.34.06 (for non- osx-x86_64 archs) #298

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

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

kratsg
Copy link

@kratsg kratsg commented Jul 20, 2025

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

This builds off of #288 by @vepadulano . Honestly ended up coming down to just having the re-renders of various dependent libs to make this all work. Particularly, both llvmdev and clangdev got a bit unlucky in release the root_63406 variant with libxml==2.14 before conda-forge globally bumped that back down to 2.13. A bit of a nasty race condition that ended up delaying getting this working.

For this to work, we need to re-render dependencies using libxml < 2.14 rather than the original pin (for some reason not getting picked up automatically?):

@conda-forge-admin
Copy link
Contributor

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

@conda-forge-admin
Copy link
Contributor

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

I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

@conda-forge-admin
Copy link
Contributor

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

@kratsg
Copy link
Author

kratsg commented Jul 22, 2025

@conda-forge-admin, please rerender

1 similar comment
@kratsg
Copy link
Author

kratsg commented Jul 22, 2025

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub Actions workflow below for more details. You can also ping conda-forge/core (using the @ notation) for further assistance or you can try rerendering locally.

The following suggestions might help debug any issues:

  • Is the recipe/{meta.yaml,recipe.yaml} file valid?
  • If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnnings.
  • Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16433442552. Examine the logs at this URL for more detail.

@kratsg
Copy link
Author

kratsg commented Jul 23, 2025

@conda-forge-admin, please rerender

@kratsg
Copy link
Author

kratsg commented Jul 23, 2025

Build failures are on osx_64 primarily due to

2025-07-23T14:46:50.6706770Z  │ │ $SRC_DIR/build-dir/etc/cling/std_darwin.modulemap:540:12: error: header 'experimental/__memory' not found
2025-07-23T14:46:50.6712270Z  │ │     header "experimental/__memory"
2025-07-23T14:46:50.6717120Z  │ │            ^
2025-07-23T14:46:50.6727250Z  │ │ input_line_1:1:10: note: submodule of top-level module 'std' implicitly imported here
2025-07-23T14:46:50.6747370Z  │ │ #include <new>
2025-07-23T14:46:50.6874610Z  │ │          ^
2025-07-23T14:46:50.6880030Z  │ │ Warning in cling::IncrementalParser::CheckABICompatibility():
2025-07-23T14:46:50.6906230Z  │ │   Failed to extract C++ standard library version.
2025-07-23T14:46:50.6915580Z  │ │ Warning in cling::IncrementalParser::CheckABICompatibility():
2025-07-23T14:46:50.6919700Z  │ │   Possible C++ standard library mismatch, compiled with _LIBCPP_ABI_VERSION '1'
2025-07-23T14:46:50.6934760Z  │ │   Extraction of runtime standard library version was: ''
2025-07-23T14:46:50.6976030Z  │ │ [ 47%] Copying $SRC_DIR/root-source/test/ProofBench/Draw_Slave_Access.C
2025-07-23T14:46:50.7059660Z  │ │ [ 47%] Copying $SRC_DIR/root-source/test/ProofBench/Draw_Time_Hists.C
2025-07-23T14:46:50.7087480Z  │ │ While building module 'Core':
2025-07-23T14:46:50.7128360Z  │ │ While building module 'Cling_Runtime' imported from input_line_2:1:
2025-07-23T14:46:50.7160870Z  │ │ While building module 'Cling_Runtime_Extra' imported from $SRC_DIR/build-dir/etc/cling/Interpreter/RuntimeUniverse.h:27:
2025-07-23T14:46:50.7197940Z  │ │ $SRC_DIR/build-dir/etc/cling/std_darwin.modulemap:540:12: error: header 'experimental/__memory' not found
2025-07-23T14:46:50.7374560Z  │ │     header "experimental/__memory"
2025-07-23T14:46:50.7431700Z  │ │            ^
2025-07-23T14:46:50.7438720Z  │ │ $SRC_DIR/build-dir/etc/cling/Interpreter/DynamicExprInfo.h:13:10: note: submodule of top-level module 'std' implicitly imported here
2025-07-23T14:46:50.7450530Z  │ │ #include <string>
2025-07-23T14:46:50.7459650Z  │ │          ^
2025-07-23T14:46:50.7473450Z  │ │ $SRC_DIR/build-dir/etc/cling/Interpreter/DynamicExprInfo.h:40:7: error: use of undeclared identifier 'std'
2025-07-23T14:46:50.7479820Z  │ │       std::string m_Result;
2025-07-23T14:46:50.7486480Z  │ │       ^
2025-07-23T14:46:50.7498900Z  │ │ While building module 'Core':
2025-07-23T14:46:50.7522060Z  │ │ While building module 'Cling_Runtime' imported from input_line_2:1:
2025-07-23T14:46:50.7539870Z  │ │ While building module 'Cling_Runtime_Extra' imported from $SRC_DIR/build-dir/etc/cling/Interpreter/RuntimeUniverse.h:27:
2025-07-23T14:46:50.7735440Z  │ │ $SRC_DIR/build-dir/etc/cling/std_darwin.modulemap:540:12: error: header 'experimental/__memory' not found
2025-07-23T14:46:50.7753150Z  │ │     header "experimental/__memory"
2025-07-23T14:46:50.7759740Z  │ │            ^
2025-07-23T14:46:50.7765500Z  │ │ $SRC_DIR/build-dir/etc/cling/Interpreter/DynamicLookupLifetimeHandler.h:12:10: note: submodule of top-level module 'std' implicitly imported here
2025-07-23T14:46:50.7771550Z  │ │ #include <string>
2025-07-23T14:46:50.7775430Z  │ │          ^
2025-07-23T14:46:50.7787770Z  │ │ $SRC_DIR/build-dir/etc/cling/Interpreter/DynamicLookupLifetimeHandler.h:56:7: error: use of undeclared identifier 'std'
2025-07-23T14:46:50.7794090Z  │ │       std::string m_Type;
2025-07-23T14:46:50.7803050Z  │ │       ^
2025-07-23T14:46:50.7812510Z  │ │ While building module 'Core':
2025-07-23T14:46:50.7832900Z  │ │ While building module 'Cling_Runtime' imported from input_line_2:1:
2025-07-23T14:46:50.7870870Z  │ │ While building module 'Cling_Runtime_Extra' imported from $SRC_DIR/build-dir/etc/cling/Interpreter/RuntimeUniverse.h:27:
2025-07-23T14:46:50.7877070Z  │ │ $SRC_DIR/build-dir/etc/cling/std_darwin.modulemap:540:12: error: header 'experimental/__memory' not found
2025-07-23T14:46:50.7906030Z  │ │     header "experimental/__memory"
2025-07-23T14:46:50.7915110Z  │ │            ^
2025-07-23T14:46:50.7945360Z  │ │ $SRC_DIR/build-dir/etc/cling/Interpreter/Value.h:15:10: note: submodule of top-level module 'std' implicitly imported here
2025-07-23T14:46:50.7953910Z  │ │ #include <cstdint> // for uintptr_t
2025-07-23T14:46:50.7997510Z  │ │          ^
2025-07-23T14:46:50.8109260Z  │ │ $SRC_DIR/build-dir/etc/cling/Interpreter/Value.h:152:23: error: use of undeclared identifier 'uintptr_t'
2025-07-23T14:46:50.8122690Z  │ │           return (T) (uintptr_t) V.getAs<void*>();
2025-07-23T14:46:50.8165110Z  │ │                       ^
2025-07-23T14:46:50.8271740Z  │ │ $SRC_DIR/build-dir/etc/cling/Interpreter/Value.h:166:24: error: use of undeclared identifier 'uintptr_t'
2025-07-23T14:46:50.8286160Z  │ │           return (T*) (uintptr_t) V.getAs<void*>();
2025-07-23T14:46:50.8294950Z  │ │                        ^
2025-07-23T14:46:50.8308110Z  │ │ $SRC_DIR/build-dir/etc/cling/Interpreter/Value.h:313:25: error: use of undeclared identifier 'uintptr_t'
2025-07-23T14:46:50.8331110Z  │ │     return (void*)getAs<uintptr_t>();
2025-07-23T14:46:50.8519870Z  │ │                         ^
2025-07-23T14:46:50.8532150Z  │ │ While building module 'Core':
2025-07-23T14:46:50.8548180Z  │ │ While building module 'Cling_Runtime' imported from input_line_2:1:
2025-07-23T14:46:50.8553060Z  │ │ In file included from <module-includes>:1:
2025-07-23T14:46:50.8629490Z  │ │ $SRC_DIR/build-dir/etc/cling/Interpreter/RuntimeUniverse.h:27:10: fatal error: could not build module 'Cling_Runtime_Extra'
2025-07-23T14:46:50.8641650Z  │ │ #include "cling/Interpreter/Visibility.h"
2025-07-23T14:46:50.8646520Z  │ │  ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2025-07-23T14:46:50.8653280Z  │ │ input_line_2:1:10: fatal error: could not build module 'Cling_Runtime'
2025-07-23T14:46:50.8683730Z  │ │ #include <cling/Interpreter/RuntimeUniverse.h>
2025-07-23T14:46:50.8712450Z  │ │  ~~~~~~~~^

which looks suspiciously the same as seen in Homebrew/homebrew-core#217574 and root-project/root#18429 . This looks like a nightmare admittedly. Wonder if it makes sense to skip straight to 6.34.08 / 12 -- if we can't get 06 built for everything.

@kratsg
Copy link
Author

kratsg commented Jul 23, 2025

@vepadulano -- I have more progress here. osx arm builds, and most of the linux builds should succeed.

@kratsg kratsg mentioned this pull request Jul 23, 2025
5 tasks
@kratsg
Copy link
Author

kratsg commented Jul 23, 2025

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Jul 23, 2025

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/recipe.yaml) and found some lint.

Here's what I've got...

For recipe/recipe.yaml:

  • ❌ The feedstock has no .ci_support files and thus will not build any packages.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16477268108. Examine the logs at this URL for more detail.

@kratsg
Copy link
Author

kratsg commented Jul 23, 2025

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16477928123. Examine the logs at this URL for more detail.

@conda-forge-admin
Copy link
Contributor

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

@kratsg
Copy link
Author

kratsg commented Jul 23, 2025

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Jul 23, 2025

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/recipe.yaml) and found some lint.

Here's what I've got...

For recipe/recipe.yaml:

  • ❌ The feedstock has no .ci_support files and thus will not build any packages.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16485459210. Examine the logs at this URL for more detail.

@kratsg
Copy link
Author

kratsg commented Jul 24, 2025

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

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

kratsg and others added 2 commits July 24, 2025 03:31
@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16485730579. Examine the logs at this URL for more detail.

Copy link
Member

@matthewfeickert matthewfeickert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heck yeah! 🚀 Great to see things passing @kratsg. As this is also bumping to a new ROOT version, can you update the PR title and body to summarize the great work here?

@kratsg kratsg changed the title rerendering 6.34.06 (for non- osx-x86_64 archs) Jul 24, 2025
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.

4 participants