[MacPorts] #69467: graphviz @9.0.0: libtool: Version mismatch error (was: graphviz @9.0.0 build fails on Sonoma, libtool version mismatch)

[MacPorts]

#69467: graphviz @9.0.0: libtool: Version mismatch error
------------------------+------------------------
  Reporter:  astrofitz  |      Owner:  ryandesign
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.9.1
Resolution:             |   Keywords:
      Port:  graphviz   |
------------------------+------------------------

Comment (by ryandesign):

 We are running autoreconf in the graphviz port which should be
 regenerating aclocal.m4 and everything else about the autotools build
 system with new copies from MacPorts; MacPorts libtool is at version
 2.4.7.

 It looks like graphviz has two aclocal.m4 files—one at the root level and
 one in the libltdl directory—but when I run configure, both of them get
 updated.

 This is not a general macOS Sonoma problem. We had successful
 [https://ports.macports.org/port/graphviz/builds/ builds of graphviz] on
 every OS version on our buildbot system, most recently on macOS Sonoma in
 January 2024. We are not yet using Xcode 15.3 yet however so it is
 possible that something new has broken there. libtool has been at 2.4.7
 since April 2022 so that hasn't been a problem before.

 Here's the response one of the developers of Graphviz received on the
 libtool mailing list when this happened to them 15 years ago:

 https://lists.gnu.org/archive/html/bug-libtool/2009-01/msg00023.html

 I'm not certain yet whether any of the suggestions there apply in this
 case. Does the problem persist if you `sudo port clean graphviz` and then
 try again?

 The message you mentioned about m4 requiring the command-line tools,
 despite those being installed, is also very strange. Such messages should
 only be coming from Apple's wrapper programs like /usr/bin/m4 but the
 build shouldn't be using that; it should be using /opt/local/bin/gm4. And
 even if /usr/bin/m4 were used, it shouldn't say to install something
 that's already installed. (And the fact that it says that would be out of
 our control to fix, since that's Apple software.) It might be worth trying
 to reinstall the command line tools manually using
 [https://developer.apple.com/download/all/?q=command%20line%20tools the
 installer] even though they appear already to be installed.

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