[MacPorts] #68175: postgresql15 @15.4: warning about implicit declaration of strchr should be suppressed

[MacPorts]

#68175: postgresql15 @15.4: warning about implicit declaration of strchr should be
suppressed
---------------------------+----------------------
  Reporter:  ryandesign    |      Owner:  dgilman
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.8.1
Resolution:                |   Keywords:
      Port:  postgresql15  |
---------------------------+----------------------

Comment (by ryandesign):

 This ticket is about the `strchr` warning only. The reason why it should
 be suppressed in this port is specific to this port. The warning will only
 appear if the configure script was built with autoconf 2.71 or later or if
 autoreconf is used (since the MacPorts version of autoconf is 2.71 or
 later).

 I cannot speak to the other implicit function declarations reported which
 is why I did not mention them. If they are standard functions on other
 operating systems that just don't exist on macOS, then they should be
 listed in [source:macports-
 ports/_resources/port1.0/checks/implicit_function_declaration the global
 files], not in the portfile. You said they exist on arm but not on x86. I
 do not know how that should be handled in MacPorts since the global files
 are global and not architecture-specific. You could ask on the macports-
 dev mailing list. It would be good to have a standard way of handling
 this, if this seems likely to be a common situation in other ports.

 CI and buildbot do not provide a way for you to access the config.log
 files.

 MacPorts' detection of implicit function declarations relies on parsing
 the config.log files for warnings with a particular wording, based on the
 wording used in Apple Clang 12 and 13. llvm.org Clang 15 and later also
 contains this feature but uses a different wording for the message and
 Apple adopted that new wording in Apple Clang 14 and later. MacPorts base
 has been updated to handle the new wording (#67504) but there has not yet
 been a new release of MacPorts containing that fix. You can either build
 with older versions of Clang to get warnings with the old wording or you
 can [https://guide.macports.org/#installing.macports.git build the
 MacPorts base master from source] so that it understands the new wording.

-- 
Ticket URL: <https://trac.macports.org/ticket/68175#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS