That way, uudecode will write the decoded output there, rather than to a
file named "empty" that gets left around. That also means we don't need
to redirect the output of uudecode to /dev/null, so don't do that.
Doing it at make time means you don't have to re-run the configure
script if you add uudecode to your system, and doing it by uudecoding a
uuencoded empty file means we don't depend on uudecode supporting
"--help".
commit 0a029bab08
Author: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Date: Sat Nov 14 20:51:44 2009 -0500
updated print-flags test case to have new TCP flags
to print-capXX.out, prior to removing print-XX.out (again - see previous
commits; it collides with print-xx.out on systems with case-insensitive
file systems).
commit 0a029bab08
Author: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Date: Sat Nov 14 20:51:44 2009 -0500
updated print-flags test case to have new TCP flags
to print-capXX.out, prior to removing print-XX.out (again - see previous
commits; it collides with print-xx.out on systems with case-insensitive
file systems).
revision 1.5
date: 2007-08-29 12:04:17 +0000; author: mcr; state: Exp; lines: +10 -10
test cases and output for IKEv2 and -X options.
from print-XX.out, prior to removal of print-XX.out (having both
print-xx.out and print-XX.out doesn't work on OSes with case-insensitive
file systems, such as most file systems on Windows and several file
systems on OS X).
revision 1.5
date: 2007-08-29 12:04:17 +0000; author: mcr; state: Exp; lines: +7 -91
test cases and output for IKEv2 and -X options.
from print-X.out, prior to removal of print-X.out (having both
print-x.out and print-X.out doesn't work on OSes with case-insensitive
file systems, such as most file systems on Windows and several file
systems on OS X).
revision 1.3
date: 2005/10/02 22:24:33; author: mcr; state: Exp; lines: +10 -10
branches: 1.3.2;
updated test case output
for print-X.out and print-XX.out to print-capX.out and print-capXX.out,
and re-remove print-X.out and print-XX.out, so that they don't collide
with "print-x.out" and "print-xx.out" on systems with case-insensitive
file systems (not only are modern Windows file systems case-insensitive
but case-preserving, so, by default, is HFS+ on OS X, so you can even
have case-insensitivity on UN*X systems).
"print-capXX.out", so that they don't collide with "print-x.out" and
"print-xx.out" on systems with case-insensitive file systems (not only
are modern Windows file systems case-insensitive but case-preserving,
so, by default, is HFS+ on OS X, so you can even have case-insensitivity
on UN*X systems).
