From: Peter Korsgaard <peter@korsgaard.com>
To: thomas@devoogdt.com
Cc: Thomas Devoogdt <thomas.devoogdt@barco.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 2/3] package/fluent-bit: add support for non glibc toolchain
Date: Wed, 15 Feb 2023 10:21:07 +0100 [thread overview]
Message-ID: <87ttzn473w.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20230211182546.633728-2-thomas@devoogdt.com> (thomas@devoogdt.com's message of "Sat, 11 Feb 2023 19:25:44 +0100")
>>>>> "thomas" == thomas <thomas@devoogdt.com> writes:
> From: Thomas Devoogdt <thomas.devoogdt@barco.com>
> - require threads and dynamic library support
> - require sync_4 support
> - provide fts.h trough musl-fts
> static_assert is not available if no C++ toolchain or no glibc
> is used, so add two patches to fix this
> Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
Committed, thanks. We do have xxhash and c-ares packages in Buildroot,
could you have a look at using those instead of these vendored
libraries?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-15 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 18:25 [Buildroot] [PATCH v2 1/3] package/fluent-bit: bump to version 2.0.9 thomas
2023-02-11 18:25 ` [Buildroot] [PATCH v2 2/3] package/fluent-bit: add support for non glibc toolchain thomas
2023-02-15 9:21 ` Peter Korsgaard [this message]
2023-02-15 11:41 ` Thomas Devoogdt
2023-02-15 12:52 ` Peter Korsgaard
2023-02-11 18:25 ` [Buildroot] [PATCH v2 3/3] package/fluent-bit: fix builds on s390x architectures thomas
2023-02-15 9:22 ` Peter Korsgaard
2023-02-15 9:19 ` [Buildroot] [PATCH v2 1/3] package/fluent-bit: bump to version 2.0.9 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=87ttzn473w.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=thomas.devoogdt@barco.com \
--cc=thomas@devoogdt.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.