Date: Tue, 29 Jan 2002 21:25:38 +0900 From: "Akinori MUSHA" <knu@iDaemons.org> To: Ruslan Ermilov <ru@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/security/checkpassword Makefile ports/security/crack Makefile ports/security/cyrus-sasl Makefile ports/security/digest Makefile ports/security/drweb-sendmail Makefile ports/security/gnupg-idea Makefile ports/security/heimdal Makefile ... Message-ID: <861yg9cpj1.wl@archon.local.idaemons.org> In-Reply-To: <20020129141057.A36555@sunbay.com> References: <200201291158.g0TBwq070541@freefall.freebsd.org> <20020129141057.A36555@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At Tue, 29 Jan 2002 14:10:57 +0200,
Ruslan Ermilov wrote:
> On Tue, Jan 29, 2002 at 03:58:52AM -0800, Akinori MUSHA wrote:
> > knu 2002/01/29 03:58:52 PST
> >
> [...]
> > Log:
> > Use ${ECHO_CMD} instead of ${ECHO} where you mean the echo command;
> > the ECHO macro is set to "echo" by default, but it is set to "true" if
> > make(1) is invoked with the -s option while ECHO_CMD is always set to
> > the echo command.
> >
> Why not just use `echo'?
Before asking that of me, someone please explain to me why we have
been using "/bin/echo" until I changed ECHO to just "echo". :)
My answer for the moment is: to save the option to set ECHO_CMD to
/bin/echo for some ports building environment with a shell which has
an incompatible echo command. (no -n support, etc.)
--
/
/__ __ Akinori.org / MUSHA.org
/ ) ) ) ) / FreeBSD.org / Ruby-lang.org
Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp
"Somewhere out of a memory.. of lighted streets on quiet nights.."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?861yg9cpj1.wl>