[MacPorts] #68578: c-ares 1.21.0 is broken now on powerpc: CMake Error: Generator: execution of make failed. Make command was: /opt/local/bin/cmake -E env VERBOSE=1 /usr/bin/make -f Makefile cmTC_c4da1/fast

MacPorts noreply at macports.org
Sun Oct 29 10:43:30 UTC 2023


#68578: c-ares 1.21.0 is broken now on powerpc: CMake Error: Generator: execution
of make failed. Make command was: /opt/local/bin/cmake -E env VERBOSE=1
/usr/bin/make -f Makefile cmTC_c4da1/fast
-------------------------+-------------------------------------------------
  Reporter:              |      Owner:  barracuda156
  barracuda156           |
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.8.1
Resolution:              |   Keywords:  tiger, leopard, snowleopard,
      Port:  c-ares      |  powerpc
-------------------------+-------------------------------------------------

Comment (by barracuda156):

 Replying to [comment:1 kencu]:
 > Well, we don't really know about "powerpc" in general, tiger, or
 leopard.
 >
 > We know that on the day you tried to build this on 10.6-for-PPC, at
 least, it failed once.
 >
 > And we know it builds on every system on the buildbots, according to the
 build success page.
 >
 > I presume you tried the usual things, restarting your system, cleaning,
 trying again. Nobody has a 10.6-on-PowerPC system but you, so I guess this
 is your ticket to fix.

 Looks like it is either a bug in CMake 3.28 itself, or a result of legacy-
 support-devel mess in a course of testing.

 Because with everything else identical, CMake 3.27 builds `c-ares` fine.
 CMake 3.28 fails. Moreover, old version of `c-ares` fails with it
 identically, which I have installed on the same system (so it has been
 proven to build).

 I also got same weird errors with `libical` now, where build uses `gcc13`
 (unlike `c-ares` which uses gcc-4.2).

 We can rule out toolchain issues or SDK bugs. I will need to either
 rebuild a bunch of stuff with, possibly, several versions of `legacy-
 support`, or just test on another machine, where, I hope, I kept an older
 legacy-support, but where I do have every CMake to switch between.

 P. S. Cannot test on 10.5 now, I nuked libgcc there when trying to force a
 non-universal ppc64 build. :)
 That issue is fixed by the way. But I need to build the toolchain anew
 there.

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


More information about the macports-tickets mailing list