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
Makefile: Fix missing slashes #28659
Conversation
|
LGTM, but please add a NEWS entry. https://blurb-it.herokuapp.com/ |
|
Done. |
|
Done. I couldn't find anything in the devguide telling what a NEWS entry must contain so went with my best judgement. |
|
While diagnosing a Mac build of a Pyenv user. pyenv/pyenv#1678 (comment) |
|
(reopening to restart failed azure pipeline) |
|
Thanks @native-api for the PR, and @JulienPalard for merging it |
|
GH-28690 is a backport of this pull request to the 3.10 branch. |
(cherry picked from commit 417faa6) Co-authored-by: native-api <vano@mail.mipt.ru>
|
GH-28691 is a backport of this pull request to the 3.9 branch. |
(cherry picked from commit 417faa6) Co-authored-by: native-api <vano@mail.mipt.ru>
|
Ah, thanks for finding that. This should never be an issue in real life except in a theoretical case where you are re-using a build directory but with different configure arguments on a macOS universal build. But the original is incorrect so it's fine to fix it. I'm a bit concerned about adding a blurb entry with no associated bpo issue. The blurb utility won't let you do that and I know of no precedent for having a NEWS item in the changelog without a bpo. In this case, the change is so minor and should have no practical effect that it's definitely not worth opening an issue for it; I would prefer to see the NEWS item removed instead. |
|
I've restored the PR branch so you can push more commits there and merge it again if you need to... |
|
I'm removing the news entry in #28703 |
There are missing slashes in the two command lines, resulting in invocations like this:
Applies to everything since 3.4.