Fix clobbering

[isuruf]

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.

[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/19709841439. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly conda-forge automerge bot!

Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

[h-vetinari]

Presumably this will fix #197

[h-vetinari]

There's a bunch of failing jobs, for different reasons. The most benign one fails because it needs a build osx-64/gcc_impl_linux-ppc64le-15.2.0-hd4c9bb7_12.conda that failed on main, though that build is passing now, so it'll work upon restarting after the merge once the first build has been uploaded.

Another (osx-64/gcc_impl_win-64-15.2.0) fails due to

error: $BUILD_PREFIX/bin/x86_64-apple-darwin13.4.0-install_name_tool: changing install names or rpaths can't be redone for: $PREFIX/bin/x86_64-w64-mingw32-gcov-tool (for architecture x86_64) because larger updated load commands do not fit (the program must be relinked, and you may need to use -headerpad or -headerpad_max_install_names)

The majority is failing due to

+ test -f $PREFIX/lib/gcc/{{ target }}/15.2.0/libgomp.spec

Also worth noting is the following warning (for osx-64/gcc_impl_osx-arm64-15.2.0-hdec9a96_13.conda)

ld: warning: object file ($PREFIX/lib/gcc/arm64-apple-darwin20.0.0/15.2.0/libgcc.a(floatuntitd.o)) was built for newer macOS version (11.0) than being linked (10.13)

which indicates that something with the SDK/sysroot isn't being picked up correctly.

[conda-forge-admin]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: failed

Thus the PR was not passing and not merged.

[conda-forge-admin]

Hi! This is the friendly conda-forge automerge bot!

Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

[isuruf]

which indicates that something with the SDK/sysroot isn't being picked up correctly.

That's okay. MACOSX_DEPLOYMENT_TARGET is setup properly in feedstocks only.