Compiler warning with fileno when building with non-gnu C extensions#926
Compiler warning with fileno when building with non-gnu C extensions#926pmqs wants to merge 1 commit intomadler:developfrom
Conversation
|
Applied. |
@madler, just spotted a failure in the MacOS clang build with this change (see https://github.com/madler/zlib/actions/runs/7789724438/job/21241964719 and https://github.com/madler/zlib/actions/runs/7789724436/job/21241964381) Backing out this change makes the issue go away. Interestingly the Mac builds using gcc work fine with this change (see https://github.com/madler/zlib/actions/runs/7789724436/job/21241964567). Does |
|
Yes, I develop on a Mac. I changed it to |
|
After some testing, I changed that to |
|
@madler I merged the All is fine apart from the combination of Ubuntu + clang + cmake with c89 or iso9899:199409 Error in both cases is It does work with the configure build, so the issue must to be something in the generation of Right - I see the issue. The configure build adds Don't see any code in |
|
Merged commit: |
Building zlib throws up this compiler warning when the non-gnu extensions are enabled - so that is with gcc & clang using the
-stdoption with any of the valuesc99,c11,c17, andc2x. This issue was found using the workflow file contained in #925Looking at
filenoinstdio.hon my Ubuntu setup I see it is guarded by__USE_POSIXThis change mirrors what is done in
gzguts.hto define_POSIX_SOURCEif it isn't already defined.