[MacPorts] #73796: muniversal portgroup: Text file merging is broken on Tahoe

[MacPorts]

#73796: muniversal portgroup: Text file merging is broken on Tahoe
--------------------------------+--------------------
  Reporter:  TellowKrinkle      |      Owner:  (none)
      Type:  defect             |     Status:  new
  Priority:  Normal             |  Milestone:
 Component:  ports              |    Version:  2.12.4
Resolution:                     |   Keywords:  tahoe
      Port:  muniversal, glib2  |
--------------------------------+--------------------

Comment (by ryandesign):

 Parsing error messages can be fragile. We would need to check whether
 there were any variations in the wording over time, and keep up with any
 future changes. For example, on my macOS 12 system, I get:

 {{{
 % /usr/bin/libtool a.txt b.txt -o c.txt
 error:
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool:
 file: a.txt is not an object file (not allowed in a library)
 error:
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool:
 file: b.txt is not an object file (not allowed in a library)
 }}}

 As another example, we parse the config.log for indications of implicit
 function declarations and implicit int, but those messages have changed
 over time, so [ticket:67504 we had to go back and fix it], and probably
 are still only handling clang's wordings and not gcc's.

 I favor [comment:5 the options I already presented].

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