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, 13 Jul 2023 22:11:19 +0200 [thread overview]
Message-ID: <20230713221119.0c83afa4@windsurf> (raw)
In-Reply-To: <20230713075740.328213-1-james.hilliard1@gmail.com>
On Thu, 13 Jul 2023 01:57:40 -0600
James Hilliard <james.hilliard1@gmail.com> 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.
But then isn't there a chance that the bundled headers are too *recent*
compared to the running kernel? What happens in this case?
Thomas
--
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
next prev parent reply other threads:[~2023-07-13 20:11 UTC|newest]
Thread overview: 4+ 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 [this message]
2023-07-13 20:40 ` Maxim Kochetkov via buildroot
2023-07-13 21:33 ` James Hilliard
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=20230713221119.0c83afa4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox