From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] package/strace: use bundled headers
Date: Thu, 22 Oct 2026 13:29:33 +0200 [thread overview]
Message-ID: <atnzfzaDFOtqR5Oz@windsurf> (raw)
In-Reply-To: <20230713075740.328213-1-james.hilliard1@gmail.com>
On Thu, Jul 13, 2023 at 01:57:40AM -0600, James Hilliard wrote:
> There is a bug in the configure script, while we could apply the
> upstream patching fixing this bug the better solution is to switch
> to using the bundled headers instead.
>
> The reason for this is that strace needs the headers of the running
> kernel rather than those that were used to build the toolchain.
>
> The running kernel is often more recent than the one used in the
> toolchain so we do want to use the more up-to-date headers.
>
> As such we should use the strace bundled headers as they will be
> the most up-to-date headers.
>
> Details: https://github.com/strace/strace/issues/253
>
> Fixes:
> - http://autobuild.buildroot.net/results/867/8675aeca53653d9d792182be61a28ea550dc530d
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
As reported in the discussion, the root issue was fixed in strace 6.4,
to which we updated a long time ago, so I believe this change is no
longer needed. I'll mark this patch as Rejected in patchwork.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-22 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 7:57 [Buildroot] [PATCH v2 1/1] package/strace: use bundled headers James Hilliard
2023-07-13 20:11 ` Thomas Petazzoni via buildroot
2023-07-13 20:40 ` Maxim Kochetkov via buildroot
2023-07-13 21:33 ` James Hilliard
2026-10-22 11:29 ` Thomas Petazzoni via buildroot [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=atnzfzaDFOtqR5Oz@windsurf \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@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 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.