Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

workflows: add sanity check for toolchains w/ CXX support #9277

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

ThomasDevoogdt
Copy link
Contributor

@ThomasDevoogdt ThomasDevoogdt commented Aug 25, 2024

Fluent-bit is written in C. There is no reason to have a CXX compiler. (Except for some libs which are all individually optional.) So add a check that enforces a C-only toolchain. E.g. useful for buildroot which does support platforms with only a C compiler.

This PR is WIP, I otherwise don't have a way to test the GitHub actions.


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.
  • [N/A]] 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 force-pushed the feature/enforce-no-cxx-support branch from 06b1ed2 to 7cb18ea Compare August 25, 2024 18:37
@ThomasDevoogdt ThomasDevoogdt changed the title Feature/enforce no cxx support workflows: add sanity check for toolchains w/ CXX support Aug 25, 2024
@ThomasDevoogdt ThomasDevoogdt force-pushed the feature/enforce-no-cxx-support branch 3 times, most recently from ddf2522 to a3c1402 Compare August 25, 2024 20:21
@cosmo0920
Copy link
Contributor

Hi, we don't want to modify the vendored libraries by ourselves.
Instead, could you send you patch into librdkafka repo?
https://github.com/confluentinc/librdkafka

@ThomasDevoogdt
Copy link
Contributor Author

Hi, we don't want to modify the vendored libraries by ourselves. Instead, could you send you patch into librdkafka repo? https://github.com/confluentinc/librdkafka

Understand that, see my other PR/ remark #7765 (comment). There is an upstream PR: confluentinc/librdkafka#4366, but no reply in over a year.

@ThomasDevoogdt
Copy link
Contributor Author

Hi @cosmo0920, is it possible to re-evaluate this? I don't get an answer from upstream, but the changes are relevant IMHO. So I think that we should go forward with it. I know that changes exists that this issue wrt librdkafka gets re-introduced when syncing upstream, but the added workflows will tell us about this at that time.

@ThomasDevoogdt ThomasDevoogdt force-pushed the feature/enforce-no-cxx-support branch from d734a74 to 6c93936 Compare November 17, 2024 08:02
ThomasDevoogdt and others added 5 commits December 15, 2024 15:19
…fluent#7741

e.g. fluent-bit is a c-only library, so allow compilation without cxx

Upstream: confluentinc/librdkafka#4366
Signed-off-by: Thomas Devoogdt <[email protected]>
Fluent-bit is c only, so no need to compile cxx.
This fixes also a compile error in buildroot.

Signed-off-by: Thomas Devoogdt <[email protected]>
Fluent-bit is written in C, so don't require CXX,
also not from the libs.

Signed-off-by: Thomas Devoogdt <[email protected]>
@ThomasDevoogdt ThomasDevoogdt force-pushed the feature/enforce-no-cxx-support branch from 6c93936 to 539bf0a Compare December 15, 2024 14:20
@ThomasDevoogdt
Copy link
Contributor Author

@edsiper It has been a while. Any chance that this gets approved? I try to reduce my own patch list.

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

Successfully merging this pull request may close these issues.

2 participants