-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
coin-lemon: fixed C++17 and C++20 compilation warnings. #15516
Conversation
This comment has been minimized.
This comment has been minimized.
@rturrado Thank you for your patch, could you please send it directly to the upstream? It seems be a portability patch which makes more sense there than here, otherwise, we would need to update it for each new version. |
@uilianries Thanks for the comment! May I ask what do you mean by 'send it directly to the upstream'? Do you mean to send the patch to whoever is maintaining I initially thought that's what I should do so, yes. And it should be the library owners who updated the library, gathering the latest patches into a new version, and then created a new conan package with that version. I tried to create a conan package myself because I saw they hadn't created a new version of the library since 2014 (even though they have been publishing patches until 2021). Please confirm if I understood you correctly and I will proceed as you suggest. Thanks again. |
@rturrado Correct, sending to the authors.
Sorry, I didn't check it. In that case, let's add here, but please, don't forget to send to authors too. I also commented some updates to be added to conandata.yml Thank you for your contribution! |
This comment has been minimized.
This comment has been minimized.
…20_compilation_errors.patch, and updated conandata.yml as suggested in the pull request review.
I've seen that my changes seem to have broken a compilation with gcc 5. How can I know all the different combinations a package is built for? And how can I test that locally before uploading? Thanks, and sorry for the inconveniences I may be causing! |
This comment has been minimized.
This comment has been minimized.
Indeed there are many environments, but you don't need to test all them before pushing if you feel safe. |
…ow to use 'using' type aliases).
This comment has been minimized.
This comment has been minimized.
Hooks produced the following warnings for commit 788b028coin-lemon/1.3.1
|
I detected other pull requests that are modifying coin-lemon/all recipe: This message is automatically generated by https://github.com/ericLemanissier/conan-center-conflicting-prs so don't hesitate to report issues/improvements there. |
@@ -6,3 +6,9 @@ patches: | |||
"1.3.1": | |||
- patch_file: "patches/cmake-add-runtime-destination_1.3.1.patch" | |||
- patch_file: "patches/0001-remove-register-keyword.patch" | |||
- patch_file: "patches/fix_cpp_17_compilation_warnings.patch" | |||
patch_type: "portability" | |||
patch_description: "Fix C++17 compilation warnings regarding the use of the deprecated std::iterator" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure the warnings deserve a patch. These are costly to maintain and we really want ones to make "working software"
Does this fail to build with later cppstd? I would prefer less patches otherwise
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @prince-chrismc ,
I'm more in favour of a 'treatiing warnings as errors' policy. Anyway, yes, some of these warnings cause failures when compiling with C++17 or newer (see #15515 ).
Best regards,
Roberto.
patch_description: "Fix C++17 compilation warnings regarding the use of the deprecated std::iterator" | ||
- patch_file: "patches/fix_cpp_20_compilation_errors.patch" | ||
patch_type: "portability" | ||
patch_description: "Fix C++20 compilation errors regarding the use of allocator.construct and allocator.destroy" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add the patch_source
too with the PR to upstream were you submitted this 🙏 so others can benefit from it too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @prince-chrismc ,
I tried to get in touch with the maintainers of the Lemon Graph library via their website and their user mailing list, without luck. The last version of the library is from 2014.
I've issued a new ticket, and attached the first of the patches (C++17), to: https://lemon.cs.elte.hu/trac/lemon/attachment/ticket/680/fix_cpp_17_compilation_warnings.patch
The second patch (C++20) is actually part of this other attachment to a previous ticket (I only took the patch section for array_map.h
because the patch section for path.h
wasn't patching correctly): http://lemon.cs.elte.hu/trac/lemon/attachment/ticket/631/93c983122692.patch
I think I should update this second patch with the fixes for path.h
as well.
If you reckon, I can add those two links mentioned above as patch_source
.
Thanks,
Roberto.
Conan v1 pipeline ❌Failure in build 6 (
Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability. Conan v2 pipeline (informative, not required for merge) ❌
The v2 pipeline failed. Please, review the errors and note this will be required for pull requests to be merged in the near future. See details:Failure in build 5 (
Note: To save resources, CI tries to finish as soon as an error is found. For this reason you might find that not all the references have been launched or not all the configurations for a given reference. Also, take into account that we cannot guarantee the order of execution as it depends on CI workload and workers availability. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This pull request has been automatically closed because it has not had recent activity. Thank you for your contributions. |
@rturrado do you still work on this one? I've hit this issue in EDIT: I've opened #17338 |
Sorry for the late reply, @SpaceIm. I had abandoned this Conan package for a while. I'm glad you're trying to fix it in a new PR. |
Specify library name and version: coin-lemon/1.3.1
Fixes issue #15515.
I've recently been playing with a project that is using C++11 and
coin-lemon/1.3.1
, which is the latest official release of this library. Changing the project's C++ standard to C++23 raises a few compiler warnings, some of them coming fromcoin-lemon
. This commit adds two patches to thecoin-lemon
recipe that remove the compilation warnings. I have only tried compiling with gcc 12.2.0 on Linux.