gh-122402: Eliminate conflicts between build variants installed to a common prefix #122403
+54
−76
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using
configure
-based (i.e. non-Windows) Python installations, if more than one build variant is installed to the same prefix, some files in thebin
andlib/pkgconfig
directories currently are installed with the same name by each variant, with potentially unpredictable and undesired results.See issue #122402 for background and details.
This PR addresses identified issues for installs of non-default build variants
{v}
), i.e debug (d
), free-threading (t
), and free-threading debug (td
), by changing:make altinstall
ford
,t
, andtd
variants:make install
ford
,t
, andtd
variants:The PR also eliminates similar conflicts in the
Unix Tools
symlinks installed for macOS frameworks builds.