On Wed, Mar 8, 2023 at 1:37 AM Greg KH wrote:
> On Tue, Mar 07, 2023 at 10:13:45PM -0800, Eric Biggers wrote:
...
> > Is this an intentional breakage from the 'make' side?
No it is not an intentional breakage.
This is a fix for https://savannah.gnu.org/bugs/?63347.
> The fact that kernels 5.4
On Wed, Mar 08, 2023 at 08:57:34AM -0500, Paul Smith wrote:
> On Wed, 2023-03-08 at 08:12 -0500, Dmitry Goncharov wrote:
> > > > Is this an intentional breakage from the 'make' side?
> > No it is not an intentional breakage.
> > This is a fix for https://savannah.gnu.org/bugs/?63347.
>
> Just to
On Wed, Mar 8, 2023 at 8:58 AM Paul Smith wrote:
> Does anyone know why this commit is using a make version comparison?
Kernel build system is expected to work with gnu make-3.82.
make-3.82 puts long options before short ones.
$ cat makefile
$(info at parse time makeflags=$(MAKEFLAGS))
all:;
On Wed, Mar 08, 2023 at 08:12:57AM -0500, Dmitry Goncharov wrote:
> On Wed, Mar 8, 2023 at 1:37 AM Greg KH wrote:
> > On Tue, Mar 07, 2023 at 10:13:45PM -0800, Eric Biggers wrote:
> ...
> > > Is this an intentional breakage from the 'make' side?
> No it is not an intentional breakage.
> This is a
On Wed, Mar 08, 2023 at 07:17:37AM +0100, Greg KH wrote:
> On Tue, Mar 07, 2023 at 10:13:45PM -0800, Eric Biggers wrote:
> > 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
> >
> it's been bugging me locally for a bit
I posted a quiet= work around on the make command line, for those of us who
wouldn't easily be able to apply any change to the kernel side, a couple of
weeks ago to:
https://savannah.gnu.org/bugs/?63818
V=1 stopped working for Linux kernel module builds
On Tue, 2023-03-07 at 20:18 -0600, Satish Balay wrote:
> Ok - try a build without guile:
>
> balay@ypro make-4.4.1 % ./configure --without-guile && make -j8
>
> Now it works! :
>
> balay@ypro ~ % ./make-4.4.1/make
> CONFIGDIR: /Users/balay/testdir/share/config
> balay@ypro ~ %
>
>
> So there
...
> Does anyone know why this commit is using a make version comparison?
> That seems totally unnecessary to me; am I forgetting something? As
> far as I remember,
>
> silence := $(findstring s,$(firstword -$(MAKEFLAGS)))
Adding a $(filter-out --%,...) should help with old makes:
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
On Tue, Mar 07, 2023 at 10:13:45PM -0800, Eric Biggers wrote:
> 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
On Wed, 2023-03-08 at 08:12 -0500, Dmitry Goncharov wrote:
> > > Is this an intentional breakage from the 'make' side?
> No it is not an intentional breakage.
> This is a fix for https://savannah.gnu.org/bugs/?63347.
Just to note, it was possible to run into this problem with earlier
versions of
On Wed, 2023-03-08 at 15:31 +0100, Greg KH wrote:
> > Does anyone know why this commit is using a make version
> > comparison? That seems totally unnecessary to me; am I forgetting
> > something? As far as I remember,
> >
> > silence := $(findstring s,$(firstword -$(MAKEFLAGS)))
> >
> >
On Wed, 2023-03-08 at 09:39 -0500, Dmitry Goncharov wrote:
> On Wed, Mar 8, 2023 at 8:58 AM Paul Smith wrote:
> > Does anyone know why this commit is using a make version
> > comparison?
>
> Kernel build system is expected to work with gnu make-3.82.
> make-3.82 puts long options before short
13 matches
Mail list logo
