Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dmitry Chestnykh <dm.chestnykh@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 RESEND] package/uclibc-ng-test: Fix musl build
Date: Fri, 26 Jul 2024 09:35:24 +0200	[thread overview]
Message-ID: <20240726093524.1345a522@windsurf> (raw)
In-Reply-To: <20240725082703.615109-1-dm.chestnykh@gmail.com>

On Thu, 25 Jul 2024 11:27:03 +0300
Dmitry Chestnykh <dm.chestnykh@gmail.com> wrote:

> Musl doesn't provide sys/asm.h header
> so we should add some defines inside
> mips-specific header file to avoid build errors
> 
> Fixes:
>  http://autobuild.buildroot.net/results/af7a1d00930485f87f77762b34cae01873a8cd41/
> 
> Signed-off-by: Dmitry Chestnykh <dm.chestnykh@gmail.com>
> ---
> Musl doesn't provide sys/asm.h header.
> I think no one has enabled this test before for mips musl builds
> so perhaps this error has only appeared now
> ---
>  .../0001-Fix-error-absent-sys-asm-h.patch     | 61 +++++++++++++++++++
>  1 file changed, 61 insertions(+)
>  create mode 100644 package/uclibc-ng-test/0001-Fix-error-absent-sys-asm-h.patch

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-07-26  7:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25  8:27 [Buildroot] [PATCH v3 RESEND] package/uclibc-ng-test: Fix musl build Dmitry Chestnykh
2024-07-26  7:35 ` Thomas Petazzoni via buildroot [this message]
2024-09-01  8:40 ` 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=20240726093524.1345a522@windsurf \
    --to=buildroot@buildroot.org \
    --cc=dm.chestnykh@gmail.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