mirror of
https://github.com/jmcnamara/libxlsxwriter.git
synced 2026-05-15 22:02:06 -06:00
[GH-ISSUE #381] Compile warnings in minizip #306
Labels
No labels
awaiting user feedback
bug
cmake
cmake
docs
feature request
in progress
long term
medium term
medium term
pull-request
question
question
ready to close
short term
under investigation
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/libxlsxwriter#306
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jeroen on GitHub (Oct 17, 2022).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/381
Originally assigned to: @jmcnamara on GitHub.
We see these warnings when compiling with
-Wstrict-prototypes@jmcnamara commented on GitHub (Oct 17, 2022):
Thanks for the report. What OS and compiler version are you using?
@jmcnamara commented on GitHub (Oct 17, 2022):
I can't reproduce this on macOS:
I'll try with some Linux variants.
By the way, the minizip code is third party code from the zlib examples. It may not be warning free with recent compilers. It is probably best not to compile it with additional constraints. It is also possible to link against libminizip so that you don't have to compile it: https://libxlsxwriter.github.io/getting_started.html#gsg_minizip
The libxlsxwriter code itself should be warning clean with
-Wstrict-prototypes.@jeroen commented on GitHub (Oct 17, 2022):
This happens with clang 15 and gcc 12 (tested on both debian and fedora).
@jmcnamara commented on GitHub (Oct 17, 2022):
I'll look into it, but since it is third party code it may not be fixed externally in which case it won't be fixable.
Could you disable, or not add that check for that part of the compilation? It is a pretty harmless warning and libxlsxwriter should be warning free.
@jeroen commented on GitHub (Oct 17, 2022):
This is enforced downstream in the CRAN repository in prep for C23, I cannot disable this unfortunately: https://cran.r-project.org/web/checks/check_results_writexl.html
But I can fix it in my copy of the vendored writexl code, the solution is trivial.
@jmcnamara commented on GitHub (Oct 18, 2022):
The writexl fix for reference:
75c7029626@jmcnamara commented on GitHub (Dec 29, 2022):
Fixed on main. Thanks for the report.