From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: [PATCH] tools/xdp-forwarder: Fix build
Date: Sat, 04 Oct 2025 17:47:23 +0200 [thread overview]
Message-ID: <87ldlq1xf8.fsf@alyssa.is> (raw)
In-Reply-To: <20251003-fix-forwarder-build-v1-1-856b78ae5656@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
Demi Marie Obenour <demiobenour@gmail.com> writes:
> Clang complains that it can't fine gnu-stubs32.h. Drop the ICMP parsing
> code to avoid this error. No functional change as the code is not
> actually used.
>
> Signed-off-by: Demi Marie Obenour <demiobenour@gmail.com>
> ---
> tools/xdp-forwarder/parsing_helpers.h | 57 -----------------------------------
> 1 file changed, 57 deletions(-)
What did you do that produced this error? We're supposed to have a
reproducible environment, so something is going wrong if you're getting
errors others don't.
As previously discussed, we don't want to modify these headers, because
then it'll get harder to sync them with upstream.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2025-10-04 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 17:14 [PATCH] tools/xdp-forwarder: Fix build Demi Marie Obenour
2025-10-04 15:47 ` Alyssa Ross [this message]
2025-10-05 3:36 ` Demi Marie Obenour
2025-10-06 7:30 ` [PATCH RFC DOESNOTBUILD v2] tools/xdp-forwarder: Do not include libc headers in eBPF programs Demi Marie Obenour
2025-10-06 7:45 ` Demi Marie Obenour
2025-10-08 17:22 ` [PATCH v3] " Demi Marie Obenour
2025-10-18 10:56 ` Alyssa Ross
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=87ldlq1xf8.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=demiobenour@gmail.com \
--cc=devel@spectrum-os.org \
/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.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).