When this feature is unavailable, #cmakedefine leaves its macro undefined, triggering -Wundef. I noticed this while building the kernel for iOs.
Use #cmakedefine01 to always generate 0 or 1.
When this feature is unavailable, #cmakedefine leaves its macro undefined, triggering -Wundef. I noticed this while building the kernel for iOs.
Use #cmakedefine01 to always generate 0 or 1.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/36023.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline and AI policy for information on the review process. A summary of reviews will appear here.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
I haven't observed HAVE_FDATASYNC myself, but applied the same change anyway.
Please don't make random changes for no reason.
Maybe simply revert 976b034b13d28877aee641833d5ee28a8cc5d83f?
When this feature is unavailable, #cmakedefine leaves its macro
undefined, triggering -Wundef. Use #cmakedefine01 to always generate 0
or 1.