onnxruntime v1.23.2

[regro-cf-autotick-bot]

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

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about 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.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. 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 @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name	Upstream Version	Current Version
protobuf	33.2

_{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/cf-scripts/actions/runs/20198643182 - please use this URL for debugging.}

[conda-forge-admin]

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

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

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

[hmaarrfk]

CUDA related stuff:

• [CUDA] fp16 intB gemm microsoft/onnxruntime#24854 -- looks suspect since a line of it was reverted below
• [CUDA] Fix cuda 13 build microsoft/onnxruntime#26153

[hmaarrfk]

@h-vetinari do you mind giving this a shot? i think i'm stuck on some linkages against the conda-forge abseil for windows.

[hmaarrfk]

illegal access for osx might be:
microsoft/onnxruntime#25881

[h-vetinari]

@h-vetinari do you mind giving this a shot? i think i'm stuck on some linkages against the conda-forge abseil for windows.

To me it looks like the build runs fine, and the error happens during testing in

TEST START: /home/conda/feedstock_root/build_artifacts/linux-64/onnxruntime-cpp-1.23.2-hc421db2_0_cpu.conda
WARNING: Multiple meta files found. The meta.yaml file in the base directory (/tmp/tmp22k57z04/info/recipe) will be used.
Adding in variants from /tmp/tmp22k57z04/info/recipe/conda_build_config.yaml
Reloading output folder: ...working... done
Solving environment (_test_env): ...working... done

## Package Plan ##

  environment location: /home/conda/feedstock_root/build_artifacts/onnxruntime_1766880006478/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac


The following NEW packages will be INSTALLED:

    _libgcc_mutex:            0.1-conda_forge           conda-forge
    _openmp_mutex:            4.5-2_gnu                 conda-forge
    binutils_impl_linux-64:   2.45-default_hfdba357_105 conda-forge
    binutils_linux-64:        2.45-default_h4852527_105 conda-forge
    gcc_impl_linux-64:        14.3.0-he8b2097_16        conda-forge
    gcc_linux-64:             14.3.0-h298d278_17        conda-forge
    gxx_impl_linux-64:        14.3.0-h2185e75_16        conda-forge
    gxx_linux-64:             14.3.0-h310e576_17        conda-forge
    kernel-headers_linux-64:  3.10.0-he073ed8_18        conda-forge
    ld_impl_linux-64:         2.45-default_hbd61a6d_105 conda-forge
    libgcc:                   15.2.0-he0feb66_16        conda-forge
    libgcc-devel_linux-64:    14.3.0-hf649bbc_116       conda-forge
    libgomp:                  15.2.0-he0feb66_16        conda-forge
    libsanitizer:             14.3.0-h8f1669f_16        conda-forge
    libstdcxx:                15.2.0-h934c35e_16        conda-forge
    libstdcxx-devel_linux-64: 14.3.0-h9f08a49_116       conda-forge
    libzlib:                  1.3.1-hb9d3cd8_2          conda-forge
    onnxruntime-cpp:          1.23.2-hc421db2_0_cpu     local      
    sysroot_linux-64:         2.17-h0157908_18          conda-forge
    tzdata:                   2025c-h8577fbf_0          conda-forge
    zstd:                     1.5.7-hb78ec9c_6          conda-forge

Preparing transaction: ...working... done
Verifying transaction: ...working... done
Executing transaction: ...working... done

I don't know what the test is doing, but it's not surprising that the build fails to link to abseil and protobuf if those libraries are not even present in the environment.

[hmaarrfk]

Great find. Thx

[regro-cf-autotick-bot]

Due to the bot-rerun label I'm closing this PR. I will make another PR as appropriate. You should expect to wait at least a few hours, or possibly much longer, for a new PR.

_{This message was generated by https://github.com/regro/cf-scripts/actions/runs/20559313552 - please use this URL for debugging.}