Created attachment 146234 [details] b.p.m.shell.patch Mk/bsd.port.mk defines CONFIGURE_SHELL and MAKE_SHELL but doesn't use them. This patch fixes that. No port currently uses these variables so this should be a no-op. I'd like to set CONFIGURE_SHELL=${LOCALBASE}/bin/bash in games/crossfire-server/Makefile, because it runs configure with bash and that means the libtool script it generates also has to run with bash and for that to happen CONFIG_SHELL needs to be set to bash.
approved
A commit references this bug: Author: tijl Date: Tue Aug 26 07:40:57 UTC 2014 New revision: 366194 URL: http://svnweb.freebsd.org/changeset/ports/366194 Log: Use CONFIGURE_SHELL and MAKE_SHELL to define SHELL and CONFIG_SHELL PR: 192981 Approved by: portmgr (antoine) Changes: head/Mk/bsd.port.mk
Really, devel/gcc-arm-embedded was affected by this change, as it propagates CONFIGURE_ENV and MAKE_ENV to sub-make :)
Would adding CONFIGURE_SHELL and MAKE_SHELL to VAR_TO_SUBMAKE fix it?
I use custom submake configuration (as I need special processing of some variables), I add it to my harness. But it was hard to find why gmake complains about "-c" command :)