-
Notifications
You must be signed in to change notification settings - Fork 11
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
build: Require C11 #5
Conversation
@jtojnar could you share some more details please? Which compiler/version are we talking about? Is this when building libutp itself (which uses C++, not C internally) or when building some other project that's using it (which one? does it use C or C++?)? |
It is when building libutp standalone from fda9f4b, using GCC 12.2.0. Here is the full log:
|
Could you also fixup the readme, based on bittorrent#100? FYI I appreciate you opening this PR, but the main use-case for this repository and this non-main branch is to be built as a submodule in the main Transmission repo (which doesn't build/need ucat, just the library), not standalone. We don't intend to provide support for libutp here (or at least it certainly wasn't the original intention), so publishing a package using this repo and this branch, and built as static, is... somewhat odd IMHO, although of course always your choice e.g. if some other package(s) will make good use of it too. Still, kind of nice to have the standalone build passing. |
Since transmission@c95738b, the compiler will complain “ISO C99 doesn't support unnamed structs/unions”. Let’s switch to C11 standard, which support that feature.
Done. We are using the standalone libutp as a dependency for Transmission (and few other clients based on libtransmission). Currently updating the package to 4.0. |
Since c95738b, the compiler will complain “ISO C99 doesn't support unnamed structs/unions”.
Let’s switch to C11 standard, which support that feature.