From: Lance Fredrickson <lancethepants@gmail.com>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/2] package/softether: fix various build errors
Date: Thu, 1 Jan 2026 10:56:43 -0700 [thread overview]
Message-ID: <be0e78c7-77eb-489e-92ef-d506eefb19de@gmail.com> (raw)
In-Reply-To: <20260101183709.2dcdedcb@windsurf>
The first commit fixes build errors in the package and then next commit
removes the package? Not advocating for keeping the package, just looks
puzzling.
Lance
On 1/1/2026 10:37 AM, Thomas Petazzoni via buildroot wrote:
> On Fri, 29 Aug 2025 09:45:06 +0200
> Thomas Perale via buildroot <buildroot@buildroot.org> wrote:
>
>> This patch add several upstream patches that fix build error we are
>> experiencing on the autobuilder related to host-gcc15 and gcc14.
> Thanks, I've applied both patches!
>
> Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-01-01 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 7:45 [Buildroot] [PATCH v2 1/2] package/softether: fix various build errors Thomas Perale via buildroot
2025-08-29 7:45 ` [Buildroot] [PATCH v2 2/2] package/softether: remove package Thomas Perale via buildroot
[not found] ` <20250829074509.77782-2-thomas.perale__12087.02362362$1756453561$gmane$org@mind.be>
2025-11-01 11:23 ` Bernd Kuhls
2026-01-01 17:37 ` [Buildroot] [PATCH v2 1/2] package/softether: fix various build errors Thomas Petazzoni via buildroot
2026-01-01 17:56 ` Lance Fredrickson [this message]
2026-01-09 15:46 ` Thomas Perale via buildroot
2026-01-13 19:45 ` Arnout Vandecappelle via buildroot
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=be0e78c7-77eb-489e-92ef-d506eefb19de@gmail.com \
--to=lancethepants@gmail.com \
--cc=buildroot@buildroot.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.
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.