New submission from Julien Palard <julien+pyt...@palard.fr>:
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
----------
assignee: mdk
components: Build
messages: 309066
nosy: mdk, xdegaye
priority: low
severity: normal
status: open
title: Outdated Modules/Setup warning is invisible
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32429>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
