Un-comment "AC_CONFIG_SUBDIRS()", so that it'll run "configure" in the
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Tue, 17 Nov 1998 02:02:46 +0000 (02:02 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Tue, 17 Nov 1998 02:02:46 +0000 (02:02 +0000)
commita11f7e185d7f16cf3bf8bc47e1b24991c5a365b1
treea79f5ee27c36e71e5c58808cde6c14bd91a0b8d1
parente33b0e2dbfe38fb7e6dad6f896bd832c921d746b
Un-comment "AC_CONFIG_SUBDIRS()", so that it'll run "configure" in the
"wiretap" subdirectory, and thus leave a "config.status" file around so
that one of the "auto{make,configure,header}" guys doesn't complain when
rebuilding stuff that it can't open "config.status".  (The
"automake"-generated Makefile will recurse into "wiretap", and, at least
if you're doing builds from a tree freshly checked out from CVS, "XXX"
files will probably have been checked out before "XXX.in", so "make"
will try to reconstruct the "XXX" files from the "XXX.in" files.)

That also obviates the need to make "wiretap/Makefile" here.

We can also re-delete "wiretap/Makefile" from CVS - the problem that
caused me to bring it back wasn't caused by its absence, it was caused
by the above.  As "Makefile"s generated by "configure" scripts depend on
the particular system on which you ran "configure", there's no One True
Makefile so "Makefile" should'n't be under CVS.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@95 f5534014-38df-0310-8fa8-9805f1628bb7
configure.in
wiretap/Makefile [deleted file]