Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Daniel Palmer <daniel@0x0f.com>
Cc: buildroot@buildroot.org,
	 Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/musl: Add upstream patch to fix building strace on m68k
Date: Tue, 11 Mar 2025 12:22:41 +0200	[thread overview]
Message-ID: <87ikofamtq.fsf@tarshish> (raw)
In-Reply-To: <20250311101153.3567108-1-daniel@0x0f.com> (Daniel Palmer's message of "Tue, 11 Mar 2025 19:11:53 +0900")

Hi Daniel,

On Tue, Mar 11 2025, Daniel Palmer wrote:
> Currently it's not possible to build strace on m68k when using
> musl because the version of musl in buildroot doesn't have the
> m68k specific definitions of POLLWRNORM and POLLWRBAND.
>
> This is already fixed upstream so manually apply the patch
> until the next release.

A link to autobuilder failure is missing:

  http://autobuild.buildroot.net/results/ec3de790a66373f270f731519e2ef51c293ba683/

> Signed-off-by: Daniel Palmer <daniel@0x0f.com>
> ---
>  package/musl/0006-m68k-fix-poll.patch | 25 +++++++++++++++++++++++++
>  1 file changed, 25 insertions(+)
>  create mode 100644 package/musl/0006-m68k-fix-poll.patch
>
> diff --git a/package/musl/0006-m68k-fix-poll.patch b/package/musl/0006-m68k-fix-poll.patch
> new file mode 100644
> index 000000000000..45d5dcede459
> --- /dev/null
> +++ b/package/musl/0006-m68k-fix-poll.patch
> @@ -0,0 +1,25 @@
> +From b09e3174a695d1db60b2abc442d29ed3f87f0358 Mon Sep 17 00:00:00 2001
> +From: Baruch Siach <baruch@tkos.co.il>
> +Date: Wed, 7 Aug 2024 08:51:03 +0300
> +Subject: m68k: fix POLLWRNORM and POLLWRBAND
> +
> +As noted in commit f5011c62c3 ("fix POLLWRNORM and POLLWRBAND on mips")
> +m68k uses a different definition.

You should add your sign-off and an upstream tags here.

See the manual:

  https://buildroot.org/downloads/manual/manual.html#_format_and_licensing_of_the_package_patches

> +---
> + arch/m68k/bits/poll.h | 2 ++
> + 1 file changed, 2 insertions(+)
> + create mode 100644 arch/m68k/bits/poll.h
> +
> +(limited to 'arch/m68k/bits/poll.h')

What is this comment meant to say?

baruch

> +
> +diff --git a/arch/m68k/bits/poll.h b/arch/m68k/bits/poll.h
> +new file mode 100644
> +index 00000000..00063f41
> +--- /dev/null
> ++++ b/arch/m68k/bits/poll.h
> +@@ -0,0 +1,2 @@
> ++#define POLLWRNORM POLLOUT
> ++#define POLLWRBAND 256
> +-- 
> +cgit v1.2.1
> +

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-03-11 10:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11 10:11 [Buildroot] [PATCH] package/musl: Add upstream patch to fix building strace on m68k Daniel Palmer
2025-03-11 10:22 ` Baruch Siach via buildroot [this message]
2025-03-11 11:01   ` Daniel Palmer
2025-03-12 18:14     ` Peter Korsgaard
2025-03-12 21:24       ` Daniel Palmer
2025-03-21 15:59       ` Peter Korsgaard

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=87ikofamtq.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=daniel@0x0f.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox