From: Eric Biggers <ebiggers@kernel.org>
To: bug-make@gnu.org
Cc: stable@vger.kernel.org, Dmitry Goncharov <dgoncharov@users.sf.net>
Subject: No progress output when make 4.4.1 builds Linux 4.19 and earlier
Date: Tue, 7 Mar 2023 22:13:45 -0800 [thread overview]
Message-ID: <ZAgnmbYtGa80L731@sol.localdomain> (raw)
After upgrading to make v4.4.1 (released last week), there's no longer any
progress output from builds of the Linux kernel v4.19 and earlier. It seems the
actual build still works, but it's now silent except for warnings and errors.
It bisects to the following 'make' commit:
commit dc2d963989b96161472b2cd38cef5d1f4851ea34
Author: Dmitry Goncharov <dgoncharov@users.sf.net>
Date: Sun Nov 27 14:09:17 2022 -0500
[SV 63347] Always add command line variable assignments to MAKEFLAGS
Is this an intentional breakage from the 'make' side?
- Eric
next reply other threads:[~2023-03-08 6:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 6:13 Eric Biggers [this message]
2023-03-08 6:17 ` No progress output when make 4.4.1 builds Linux 4.19 and earlier Greg KH
2023-03-08 6:34 ` Eric Biggers
2023-03-08 13:12 ` Dmitry Goncharov
2023-03-08 13:27 ` Greg KH
2023-03-08 13:57 ` Paul Smith
2023-03-08 14:31 ` Greg KH
2023-03-08 14:39 ` Dmitry Goncharov
2023-03-08 15:53 ` David Laight
2023-03-08 17:50 ` Paul Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZAgnmbYtGa80L731@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=bug-make@gnu.org \
--cc=dgoncharov@users.sf.net \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.