[sr #110273] New test suite failures of 2.69b on OpenBSD 6.5

[Bruno Haible]

Follow-up Comment #6, sr #110273 (project autoconf):

> There's no 'gmake' on my OpenBSD 6.7 platform

It's part of the add-on packages. Here's my recipe to fetch it and a couple of
other programs:

# Install some packages.
# List is at https://ftp.hostserver.de/pub/OpenBSD/6.7/packages/amd64/
# See https://www.openbsd.org/faq/faq15.html#PkgMgmt
Edit ~/.profile to define PKG_PATH:
PKG_PATH=https://ftp.hostserver.de/pub/OpenBSD/6.7/packages/`uname -m`/
export PKG_PATH
Logout.

# pkg_add bzip2
# pkg_add gtar
# pkg_add bash
# pkg_add gmake
# pkg_add vim, pick no_x11 variant
# pkg_add emacs, pick no_x11 variant


> GNU Make sets MAKEFLAGS=w in the environment, and presumably this confuses
OpenBSD Make.

Indeed: The GNU make behaviour is explained in the thread starting at
https://lists.gnu.org/archive/html/help-make/2016-03/msg00009.html . Whereas
the OpenBSD make's interpretation of MAKEFLAGS is documented in
https://man.openbsd.org/make .

So, really, inside of GNU make invocations on OpenBSD, one should avoid
invoking 'make'.

> One possibility is that you need to be consistent about which 'make' you're
using, e.g., './configure MAKE=gmake'.

No, this does not help because tests/autotest.at lines 1938 and 1999 invokes
precisely 'make', even it the environment variable MAKE is set. How about
writing ${MAKE-make} instead?


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/support/?110273>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/