All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Brandon Maier <brandon.maier@collins.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/openssh: fix build error on powerpc
Date: Thu, 29 Feb 2024 16:31:06 +0100	[thread overview]
Message-ID: <87y1b3fft1.fsf@48ers.dk> (raw)
In-Reply-To: <20240205185616.13fb5202@windsurf> (Thomas Petazzoni via buildroot's message of "Mon, 5 Feb 2024 18:56:16 +0100")

>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:

 > On Thu, 18 Jan 2024 22:23:01 +0000
 > Brandon Maier via buildroot <buildroot@buildroot.org> wrote:

 >> Fixes the following error message introducted by OpenSSH v9.6p1.
 >> 
 >> sshkey.c: In function 'sshkey_set_filename':
 >> sshkey.c:3705:1: sorry, unimplemented: '-fzero-call-used-regs' not supported on this target
 >> 3705 | }
 >> 
 >> Fixes:
 >> http://autobuild.buildroot.org/results/ec7/ec780aed5b1c4fdf9b91f6e7be99e8d4c42efa58
 >> 
 >> Signed-off-by: Brandon Maier <brandon.maier@collins.com>
 >> ---
 >> ...ction-of-broken-fzero-call-used-regs.patch | 57 +++++++++++++++++++
 >> package/openssh/openssh.mk                    |  3 +
 >> 2 files changed, 60 insertions(+)
 >> create mode 100644 package/openssh/0001-better-detection-of-broken-fzero-call-used-regs.patch

 > Applied to master, thanks.

Committed to 2023.02.x and 2023.11.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-02-29 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 22:23 [Buildroot] [PATCH 1/1] package/openssh: fix build error on powerpc Brandon Maier via buildroot
2024-02-05 17:56 ` Thomas Petazzoni via buildroot
2024-02-29 15:31   ` Peter Korsgaard [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=87y1b3fft1.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=brandon.maier@collins.com \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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.