Skip to content

lib: add upstream fixes related to uClibc and C only toolchains#7266

Merged
leonardo-albertovich merged 10 commits into
fluent:masterfrom
ThomasDevoogdt:bugfix/add-upstream-fixes
May 8, 2023
Merged

lib: add upstream fixes related to uClibc and C only toolchains#7266
leonardo-albertovich merged 10 commits into
fluent:masterfrom
ThomasDevoogdt:bugfix/add-upstream-fixes

Conversation

@ThomasDevoogdt
Copy link
Copy Markdown
Contributor

@ThomasDevoogdt ThomasDevoogdt commented Apr 25, 2023

! please, also review and merge my upstream PR's !

Main reason for this patch series is the buildroot support that was added 2 months ago:
https://github.com/buildroot/buildroot/tree/master/package/fluent-bit

Other related PRs:

This PR can be dropped if this one is merged:


Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

  • [N/A] Example configuration file for the change
  • [N/A] Debug log output from testing the change
  • [N/A] Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

  • [N/A] Run local packaging test showing all targets (including any new ones) build.
  • Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

  • [N/A] Documentation required for this feature

Backporting

  • [N/A] Backport to latest stable release.

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

@ThomasDevoogdt ThomasDevoogdt temporarily deployed to pr April 25, 2023 12:23 — with GitHub Actions Inactive
@ThomasDevoogdt ThomasDevoogdt temporarily deployed to pr April 25, 2023 12:23 — with GitHub Actions Inactive
@ThomasDevoogdt ThomasDevoogdt temporarily deployed to pr April 25, 2023 12:23 — with GitHub Actions Inactive
@ThomasDevoogdt ThomasDevoogdt changed the title Bugfix/add upstream fixes add upstream fixes Apr 25, 2023
@ThomasDevoogdt ThomasDevoogdt changed the title add upstream fixes lib: add upstream fixes Apr 25, 2023
@ThomasDevoogdt ThomasDevoogdt temporarily deployed to pr April 25, 2023 12:45 — with GitHub Actions Inactive
@ThomasDevoogdt ThomasDevoogdt changed the title lib: add upstream fixes lib: add upstream fixes related to uClibc and C only toolchains Apr 25, 2023
@ThomasDevoogdt ThomasDevoogdt force-pushed the bugfix/add-upstream-fixes branch from 7f104f7 to 5afc696 Compare April 25, 2023 18:55
@ThomasDevoogdt ThomasDevoogdt temporarily deployed to pr April 25, 2023 18:56 — with GitHub Actions Inactive
@ThomasDevoogdt ThomasDevoogdt temporarily deployed to pr April 25, 2023 18:56 — with GitHub Actions Inactive
@ThomasDevoogdt ThomasDevoogdt temporarily deployed to pr April 25, 2023 18:56 — with GitHub Actions Inactive
@ThomasDevoogdt ThomasDevoogdt temporarily deployed to pr April 25, 2023 19:17 — with GitHub Actions Inactive
cosmo0920
cosmo0920 previously approved these changes Apr 26, 2023
Copy link
Copy Markdown
Contributor

@cosmo0920 cosmo0920 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From my side, there is no objections for these changes.

@ThomasDevoogdt
Copy link
Copy Markdown
Contributor Author

From my side, there is no objections for these changes.

Can you also have a look at the other open PRs, see the list at the top. So that every change is in sync with upstream.

@cosmo0920
Copy link
Copy Markdown
Contributor

From my side, there is no objections for these changes.

Can you also have a look at the other open PRs, see the list at the top. So that every change is in sync with upstream.

Got it. I have seen the listed PRs and everything would be nice for merging. 👍

@patrick-stephens
Copy link
Copy Markdown
Contributor

It looks like there are some unit test failures.
I'd also like to ensure we build for all targets to verify it is ok.

@ThomasDevoogdt
Copy link
Copy Markdown
Contributor Author

It looks like there are some unit test failures. I'd also like to ensure we build for all targets to verify it is ok.

I don't see why. But rebased my branch to see if it still occurs.

@ThomasDevoogdt ThomasDevoogdt temporarily deployed to pr April 26, 2023 15:24 — with GitHub Actions Inactive
@ThomasDevoogdt ThomasDevoogdt temporarily deployed to pr April 26, 2023 15:24 — with GitHub Actions Inactive
@ThomasDevoogdt
Copy link
Copy Markdown
Contributor Author

@patrick-stephens, @cosmo0920, @leonardo-albertovich, @edsiper, can you also merge this PR, or tell me if something else is needed from my side?

@patrick-stephens patrick-stephens added the ok-package-test Run PR packaging tests label Apr 28, 2023
@patrick-stephens patrick-stephens temporarily deployed to unstable April 28, 2023 09:45 — with GitHub Actions Inactive
@patrick-stephens patrick-stephens temporarily deployed to pr April 28, 2023 09:46 — with GitHub Actions Inactive
@patrick-stephens patrick-stephens temporarily deployed to pr-package-test April 28, 2023 09:46 — with GitHub Actions Inactive
@patrick-stephens patrick-stephens temporarily deployed to pr April 28, 2023 09:54 — with GitHub Actions Inactive
@patrick-stephens patrick-stephens temporarily deployed to pr-package-test April 28, 2023 09:54 — with GitHub Actions Inactive
@patrick-stephens patrick-stephens temporarily deployed to pr April 28, 2023 09:54 — with GitHub Actions Inactive
Copy link
Copy Markdown
Contributor

@cosmo0920 cosmo0920 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no against from my side. Seems OK for me.

Comment thread lib/c-ares-1.19.0/m4/ax_cxx_compile_stdcxx_11.m4
@ThomasDevoogdt
Copy link
Copy Markdown
Contributor Author

@edsiper, all relevant PR's are merged in the upstream repos, so I guess this one can be merged?

Copy link
Copy Markdown
Contributor

@patrick-stephens patrick-stephens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, builds for all targets

chunkio is written in c, so only enforce a c compiler

upstream: fluent/chunkio#94

Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
onigmo is written in c, so only enforce a c compiler

upstream: fluent/onigmo#7

Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
lwrb is written in c, so only enforce a c compiler

upstream: MaJerle/lwrb#26

Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
tutf8e is written in c, so only enforce a c compiler

upstream: nigels-com/tutf8e#9

Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
msgpack is written in c, so only enforce a c compiler

upstream: msgpack/msgpack-c#1055

Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
Not defined in uClibc, so replace them with the equivalent POLL{OUT,IN}.

https://www.man7.org/linux/man-pages/man2/poll.2.html

POLLWRNORM
       Equivalent to POLLOUT.

POLLRDNORM
       Equivalent to POLLIN.

upstream: bytecodealliance/wasm-micro-runtime#2069

Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
…C_ASSERT

Use `_Static_assert`, which is part of the C11 language.

upstream: fluent/cfl#32

Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
"undefined reference to 'static_assert'"

Not defined when using uClibc or if not C++ >= 11.

upstream: c-ares/c-ares#504

Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
Synced to:
https://github.com/arsenm/sanitizers-cmake/tree/c3dc841af4dbf44669e65b82cb68a575864326bd

Fix for:

CMake Error at cmake/sanitizers-cmake/cmake/sanitize-helpers.cmake:127 (if):
  if given arguments:

    "SANITIZE_LINK_STATIC" "AND" "(" "STREQUAL" "GNU" ")"

  Unknown arguments specified
Call Stack (most recent call first):
  cmake/sanitizers-cmake/cmake/FindASan.cmake:46 (sanitizer_check_compiler_flags)
  cmake/sanitizers-cmake/cmake/FindSanitizers.cmake:37 (find_package)
  lib/chunkio/CMakeLists.txt:53 (find_package)

-- Configuring incomplete, errors occurred!

Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
This is an upstream lib: https://github.com/arsenm/sanitizers-cmake,
so shellcheck is not applicable.

Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
@ThomasDevoogdt
Copy link
Copy Markdown
Contributor Author

Rebased since the commit from #7253 was already merged.

@leonardo-albertovich
Copy link
Copy Markdown
Contributor

I think it's time to merge this PR If @edsiper doesn't have anything against it I'll merge it by the end of the day.

The only thing I don't know is, I usually do squash merges because because the PRs I merge are localized patches but this one is all over the place and I was wondering if a commit merge or a rebase merge would be better options.

Do you have an opinion on that @ThomasDevoogdt?

Thanks for the patience, I really appreciate the effort.

@ThomasDevoogdt
Copy link
Copy Markdown
Contributor Author

The only thing I don't know is, I usually do squash merges because because the PRs I merge are localized patches but this one is all over the place and I was wondering if a commit merge or a rebase merge would be better options.

I personally always prefer clean rebase merges to have a linear tree. I already rebased the PR, so fast forward should also be possible if there are no contributions in between.

Thx also!
Will bump fluent-bit in buildroot at the next release then.

@ThomasDevoogdt
Copy link
Copy Markdown
Contributor Author

@leonardo-albertovich, kind ping ;)

@leonardo-albertovich
Copy link
Copy Markdown
Contributor

Thanks for reminding me of this @ThomasDevoogdt, I totally forgot about it.

@leonardo-albertovich
Copy link
Copy Markdown
Contributor

And obviously thanks for all the work you've put towards these improvements, it's much appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-required ok-package-test Run PR packaging tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants