This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mdk
Recipients mdk, xdegaye
Date 2017-12-26.22:10:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1514326238.69.0.213398074469.issue32429@psf.upfronthosting.co.za>
In-reply-to
Content
The devguide advise to run `make -j`, why not, but in any cases between `make -j4` and `make -j` the warning:

    -----------------------------------------------
    Modules/Setup.dist is newer than Modules/Setup;
    check to make sure you have all the updates you
    need in your Modules/Setup file.
    Usually, copying Modules/Setup.dist to Modules/Setup will work.
    -----------------------------------------------

is invisible (gets on screen first, and get kicked real quick by the compilation lines).

This got me once, and I'm not alone: https://bugs.python.org/issue32335 (And I suspect we're more than just two).

I propose to make this stop the compilation, proposing two cases:

- You modified the file? Touch it so it gets seen as up to date by makefile
- You didn't modified it? Copy Modules/Setup.dist to Modules/Setup

Something like:

    $ make
    -----------------------------------------------
    Modules/Setup.dist is newer than Modules/Setup;
    check to make sure you have all the updates you
    need in your Modules/Setup file.
    Usually, copying Modules/Setup.dist to Modules/Setup will work.
    Or if you want to keep your modifications, touch Modules/Setup
    to skip this warning.
    -----------------------------------------------
    Makefile:703: recipe for target 'Modules/Setup' failed
    make: *** [Modules/Setup] Error 1
History
Date User Action Args
2017-12-26 22:10:38mdksetrecipients: + mdk, xdegaye
2017-12-26 22:10:38mdksetmessageid: <1514326238.69.0.213398074469.issue32429@psf.upfronthosting.co.za>
2017-12-26 22:10:38mdklinkissue32429 messages
2017-12-26 22:10:38mdkcreate