How to support macos builds given tool renaming

[matthewfeickert]

In PR #9 all the macos build fail with

  On Mac OSX, the GNU libtool and libtoolize scripts, renamed
  glibtol and glibtoolize respectively by Apple to avoid
  conflict with Apple-provided libtool, should be used.

  They should be already installed, together with Apple developer tools,
  in /usr/bin. If you see this message, they are not.

even though

fastjet-feedstock/recipe/meta.yaml

Line 31 in f73dac7

- libtool

has a macos install.

In

fastjet-feedstock/recipe/meta.yaml

Line 31 in f73dac7

- libtool

@lgray had gotten around this (in PR scikit-hep/fastjet#134) with

      - name: Install compiler tools on macOS
        if: runner.os == 'macOS'
        run: |
          brew install make automake swig gmp mpfr boost
          export PATH="/usr/local/opt/make/libexec/gnubin:$PATH"

but everything that needs to be installed needs to be specified in the meta.yaml for conda-forge and should already be in the build requirements.

fastjet-feedstock/recipe/meta.yaml

Lines 22 to 34 in f73dac7

	requirements:
	build:
	- {{ compiler('c') }}
	- {{ compiler('cxx') }}
	- {{ stdlib("c") }}
	- cross-python_{{ target_platform }} # [build_platform != target_platform]
	- python # [build_platform != target_platform]
	- autoconf
	- automake
	- libtool
	- make
	- patch
	- swig

How can this get addressed? Or does this required patching the build system for these existing fastjet releases?

cc @henryiii and @chrisburr if they have any ideas.