On Mon, Feb 26, 2018 at 02:58:48PM -0600, William A Rowe Jr wrote:
> Any objections to
>
> --- build/mkdir.sh (revision 1825390)
> +++ build/mkdir.sh (working copy)
> @@ -38,7 +38,6 @@
> continue ;;
> esac
> if test ! -d "$pathcomp"; then
> -echo
Here is the stderr vpath build result of the current 2.4.x snapshot on
Ubuntu 16.04-LTS, to illustrate my concerns;
mkdir modules
mkdir modules/aaa
mkdir modules/arch
mkdir modules/arch/win32
mkdir modules/cache
mkdir modules/core
mkdir modules/database
mkdir modules/debugging
mkdir modules/echo
No comment?
Note that you won't see these artifacts on a same-tree build, but
will be confronted with a slew of them on any new vpath unix build.
On Mon, Feb 26, 2018 at 2:58 PM, William A Rowe Jr wrote:
> Any objections to
>
> --- build/mkdir.sh (revision 1825390)
> +++
Any objections to
--- build/mkdir.sh (revision 1825390)
+++ build/mkdir.sh (working copy)
@@ -38,7 +38,6 @@
continue ;;
esac
if test ! -d "$pathcomp"; then
-echo "mkdir $pathcomp" 1>&2
mkdir "$pathcomp" || errstatus=$?
fi