stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jason Self <jason@bluehome.net>
Cc: stable@vger.kernel.org
Subject: Re: Linux 5.14.11
Date: Mon, 11 Oct 2021 15:45:47 +0200	[thread overview]
Message-ID: <YWRACxAz3zlvBQg8@kroah.com> (raw)
In-Reply-To: <20211011063040.7ab8c623@bellevue.lan>

On Mon, Oct 11, 2021 at 06:30:40AM -0700, Jason Self wrote:
> On Sat,  9 Oct 2021 15:26:41 +0200
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > I'm announcing the release of the 5.14.11 kernel.
> 
> Starting with 5.14.10 I get this when doing make bindeb-pkg when
> compiling for MIPS, for the Loongson 2F. I do have a sufficient
> version of binutils installed (2.37), which was working well until
> until 5.14.10 came out.
> 
>   OBJCOPY arch/mips/boot/compressed/vmlinux.bin
>   GZIP    arch/mips/boot/compressed/vmlinux.bin.z
>   OBJCOPY arch/mips/boot/compressed/piggy.o
>   HOSTCC  arch/mips/boot/compressed/calc_vmlinuz_load_addr
>   LD      vmlinuz
>   STRIP   vmlinuz
> make KERNELRELEASE=5.14.11-gnu.loongson-2f ARCH=mips
>   KBUILD_BUILD_VERSION=1.0 -f ./Makefile intdeb-pkg sh
>   ./scripts/package/builddeb arch/mips/loongson2ef//Platform:36: ***
>   only binutils >= 2.20.2 have needed option -mfix-loongson2f-nop.
>   Stop. cp: cannot stat '': No such file or directory
>   scripts/Makefile.package:87: recipe for target 'intdeb-pkg' failed
>   make[4]: *** [intdeb-pkg] Error 1 Makefile:1576: recipe for target
>   'intdeb-pkg' failed make[3]: *** [intdeb-pkg] Error 2
> debian/rules:13: recipe for target 'binary-arch' failed
> make[2]: *** [binary-arch] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit
>   status 2 scripts/Makefile.package:82: recipe for target 'bindeb-pkg'
>   failed make[1]: *** [bindeb-pkg] Error 2
> Makefile:1576: recipe for target 'bindeb-pkg' failed
> make: *** [bindeb-pkg] Error 2

Can you use 'git bisect' to try to find the issue?

And does the same thing happen in 5.15-rc5, or does that build properly
for you?

thanks,

greg k-h

      reply	other threads:[~2021-10-11 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-09 13:26 Linux 5.14.11 Greg Kroah-Hartman
2021-10-09 13:26 ` Greg Kroah-Hartman
2021-10-11 13:30 ` Jason Self
2021-10-11 13:45   ` Greg KH [this message]

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=YWRACxAz3zlvBQg8@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jason@bluehome.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).