pulseaudio @17.0 -x11: build fails on m4 tool

[DrLex0 (Alexander Thomas)]

Similar to #69467, but its fix does not work for this build.

The dreaded “The m4 command requires the command line developer tools” dialog shows up, and the build aborts. Looks like something (CMake?) still wants to use the m4 tool that Apple forgot to provide:

:info:configure Program m4 found: YES (/usr/bin/m4)

This is a usable workaround:

sudo ln -s /Library/Developer/CommandLineTools/usr/bin/gm4 /Library/Developer/CommandLineTools/usr/bin/m4

[DrLex0 (Alexander Thomas)]

Build log

[ryandesign (Ryan Carsten Schmidt)]

The pulseaudio port uses the meson build system, not cmake. It does install cmake files for use by other ports that use the cmake build system and want to use it to find pulseaudio. The pulseaudio meson build system uses the m4 program to transform the template cmake file into the final file. From its meson.build file:

  m4 = find_program('m4', required: true)

  custom_target('PulseAudioConfig.cmake',
    input : cmake_template_file,
    output : 'PulseAudioConfig.cmake',
    capture : true,
    command : [m4, '@INPUT@'],
    build_by_default : true,
    install : true,
    install_dir : cmakedir,
  )

[ryandesign (Ryan Carsten Schmidt)]

I can't figure out how to override meson's find_program from the command line. I've filed a bug report asking for help: ​https://github.com/mesonbuild/meson/issues/13096

[ryandesign (Ryan Carsten Schmidt)]

In 44fefdc4cfbddcabfab8e7cc1598dc6899821ed5/macports-ports (master):

pulseaudio: Use MacPorts m4

Closes: #69745

[RJVB (René Bertin)]

Any idea why this only gets exposed with the x11 variant unset?