Date: Mon, 9 Nov 2015 18:18:58 -0800 From: "Simon J. Gerraty" <sjg@juniper.net> To: Bryan Drewery <bdrewery@freebsd.org> Cc: Garrett Cooper <yaneurabeya@gmail.com>, =?UTF-8?B?Sm9zw6kgUMOpcmV6?= <fbl@aoek.com>, <freebsd-current@freebsd.org>, <sjg@juniper.net> Subject: Re: Failing buildword due to execution permission (with fix) Message-ID: <27265.1447121938@chaos> In-Reply-To: <5641510E.4020602@FreeBSD.org> References: <d2efef40a9e28bec03742c49ec5e4682@mail.yourbox.net> <233C431B-1675-4A55-A46E-B1B858056A09@gmail.com> <564136A0.4080406@FreeBSD.org> <5655EBD2-5EC5-425E-82B9-F7FF30312F02@gmail.com> <564147FF.2050107@FreeBSD.org> <45AD4F5D-DABD-47ED-99FA-A40FFFF3CC7E@gmail.com> <5641510E.4020602@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> include/Makefile:MK_OSRELDATE_SH= ${.CURDIR}/mk-osreldate.sh
> >> include/Makefile: sh ${MK_OSRELDATE_SH}
>
> I actually wrote up a patch recently to use ${SH} in all places of 'sh'
> and '/bin/sh', and noted on SHELL?= that was not useful to use, but did
> not commit it (yet).
We (junos) use HOST_SH I think for this, since if building on a non-native
host, /bin/sh cannot be relied on.
FreeBSD sys.mk already has
__MAKE_SHELL?=/bin/sh
so I guess you could use that.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27265.1447121938>