Changes between Version 1 and Version 2 of WimplicitFunctionDeclaration


Ignore:
Timestamp:
Jan 24, 2022, 5:37:09 AM (2 years ago)
Author:
JDLH (Jim DeLaHunt)
Comment:

Link to MacPorts archive entry for Ryan's message about -Wimplicit-function-declaration. Strip out email addresses so they don't invite spam.

Legend:

Unmodified
Added
Removed
Modified
  • WimplicitFunctionDeclaration

    v1 v2  
    55TODO: write more page content. This is just an initial stub.
    66
    7 Email "Re: Warning: -Wimplicit-function-declaration" from Ryan Schmidt <ryandesign@macports.org> to MacPorts Users <macports-users@lists.macports.org> on Thu, 20 May 2021 01:05:07 -0500:
     7Email "[https://lists.macports.org/pipermail/macports-users/2021-May/049998.html Re: Warning: -Wimplicit-function-declaration]" from Ryan Schmidt to the MacPorts Users list on Thu May 20 06:05:07 UTC 2021:
    88    Sometimes programs are written to use functions before declaring them. This has not been correct ever since the introduction of the 1999 version of the C standard decades ago, but because it was allowed by the earlier 1989 C standard many C99 compilers still allowed this with a warning. But it can cause programs to crash or behave incorrectly on ARM processors, therefore to avoid problems on Apple Silicon Macs, the version of clang in included with Xcode 12 and later considers this to be an error. This causes some ports to fail to build. Worse, many configure tests have this problem, but when they fail, it doesn't cause configure to immediately fail and tell you that; instead, configure just makes wrong determinations about your system. In the best case, the build still succeeds and works fine. Or, the build fails with a bizarre error later. Or the build succeeds but is wrong.
    99