[MacPorts] #60698: mod_gnutls: error: use of unknown builtin '__builtin_add_overflow'

[MacPorts]

#60698: mod_gnutls: error: use of unknown builtin '__builtin_add_overflow'
-------------------------+-------------------------------------------------
  Reporter:  ryandesign  |      Owner:  Schamschula
      Type:  defect      |     Status:  closed
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.6.2
Resolution:  fixed       |   Keywords:  yosemite mavericks mountainlion
      Port:  mod_gnutls  |  lion
-------------------------+-------------------------------------------------

Comment (by Schamschula):

 No. That was based on the commit and comments https://github.com/macports
 /macports-
 ports/commit/018c4fb684733ea47d8ce71ed8a7a85bc103185e#commitcomment-40227141
 and https://github.com/macports/macports-
 ports/commit/8a0a94aa447e917d3b2bec0cc33cebd87792a7b8,
 https://github.com/macports/macports-
 ports/commit/316b25605910ad25fe023e74dd35d36100cf63dd, and
 https://github.com/macports/macports-
 ports/commit/cd4ac232782cefc89ca18e951f683f4ae98d4836, leading up to it.

 Similar to the comments I received on an unrelated recent  ticket for
 libgpg-error, I suspect that most upstream developers are not likely to
 want to add code for 'obsolete' macOS versions. Hence, my approach was to
 find a work-around on our end.

 I hesitate submitting bug reports that I can't locally reproduce.
 Unfortunately, I don't have the time and space to set up old machines
 (which I do have in storage) to test everything on older macOS versions.

 I'm set up to build on current, current - 1 or  current + 1 (often
 incomplete, as the build tools often are broken), depending on the time of
 year..

 I greatly appreciate the help from Sergey Federov, Kencu and Renee Otten
 who apparently do have these resources, and often submit PRs to fix these
 legacy OS builds of my ports.

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