<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl/util/echo.pl, branch OpenSSL_1_1_1j</title>
<subtitle>TLS/SSL and crypto library.</subtitle>
<id>http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_1_1j</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/openssl/atom?h=OpenSSL_1_1_1j'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/'/>
<updated>2018-07-11T12:49:02Z</updated>
<entry>
<title>Windows: fix echo for nmake</title>
<updated>2018-07-11T12:49:02Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2018-07-10T12:12:33Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=9abce88b4b0055d6238a838aa00360152e185f02'/>
<id>urn:sha1:9abce88b4b0055d6238a838aa00360152e185f02</id>
<content type='text'>
It seems that nmake first tries to run executables on its own, and
only pass commands to cmd if that fails.  That means it's possible to
have nmake run something like 'echo.exe' when the builtin 'echo'
command was expected, which might give us unexpected results.

To get around this, we create our own echoing script and call it
explicitly from the nmake makefile.

Fixes #6670

Reviewed-by: Andy Polyakov &lt;appro@openssl.org&gt;
Reviewed-by: Bernd Edlinger &lt;bernd.edlinger@hotmail.de&gt;
(Merged from https://github.com/openssl/openssl/pull/6686)
</content>
</entry>
</feed>
