[MacPorts] #74182: Frequent build warnings: Configuration logfiles contain indications of -Wimplicit-...

[MacPorts]

#74182: Frequent build warnings: Configuration logfiles contain indications of
-Wimplicit-...
---------------------------+--------------------------------
  Reporter:  seamusdemora  |      Owner:  (none)
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.12.5
Resolution:                |   Keywords:  Wimplicit warnings
      Port:                |
---------------------------+--------------------------------

Comment (by seamusdemora):

 Replying to [comment:1 jmroot]:
 > The tl;dr is that the message is aimed at port maintainers and may or
 may not indicate an actual problem. See wiki:WimplicitFunctionDeclaration
 for (exhaustive) details.

 OK... thanks for the link. I read some of it, but frankly I understood
 virtually none of it. I am not a developer, and do not have the ability to
 perform the {{{"diagnosis to make useful bug report"}}}. The gist of the
 message seems to be this - and please correct me if I get something wrong:

 {{{
 It might be important, or it might not - it's impossible to say without
 analysis.
 If you see these warnings, you should report it in a MacPort ticket.
 }}}

 At any rate, this ticket has been filed, and I have now provided my OS
 version and architecture above. And I guess once the "build machines" work
 through their backlog - dummies such as myself won't have to see these
 "build errors"???

 I wonder... would it not make sense to just halt all package upgrades
 until the backlog is fixed? I certainly don't want my macOS Tahoe machine
 to fall into complete "port dysfunction" as my Mojave machine has. I will
 hazard a guess that I am not the only one struggling with these issues...
 Is there a general recommendation from the development team in terms of
 how regular users should deal with this? I mean - given that (apparently)
 no one can say whether the warnings are significant or not, is it really
 wise to build ''**any**'' port now?? And - Is there some way to know
 whether or not a port will require "building" ''**before**'' the {{{port
 upgrade outdated}}} command is run???

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