meson is now more picky about unrecognized arguments.

This will have to be removed, and then making sure it uses the right NM
might have to be done another way:

lt_cv_path_NM=/opt/local/bin/nm





> *info:configure meson: error: unrecognized arguments:
> */opt/local/var/macports/build/_Users_multix_code_LeopardPorts_x11_pango/pango/work/build
> :*info:configure Command failed:  cd
> *"/opt/local/var/macports/build/_Users_multix_code_LeopardPorts_x11_pango/pango/work/pango-1.48.9"
> && /opt/local/bin/meson setup --prefix=/opt/local -Dxft=disabled
> -Dintrospection=enabled lt_cv_path_NM=/opt/local/bin/nm
> /opt/local/var/macports/build/_Users_multix_code_LeopardPorts_x11_pango/pango/work/pango-1.48.9
> /opt/local/var/macports/build/_Users_multix_code_LeopardPorts_x11_pango/pango/work/build
>
>
> is 10.5 meson too old? can I somehow use a macports one? Maybe it is
> similar to the typical nm issue.
>
>
  • [no subject] Ken Cunningham

Reply via email to