On 18/08/2019 19:49, Michael Richardson wrote:
> We build with gcc and clang on travis, with options that do not always match
> what contributors get by default.
>
> I've added "./buildem" which goes through the set of -m32/-m64 and clang, gcc
> to build them all using build directories.
> It
TESTonce is written in Perl in order to do a bit of manipulation that I found
too tedious to do in shell.
TESTrun.sh is written in shell, and contains a bunch of work arounds (.passed
and .failed files) to deal how shell creates sub-shells. This would be
trivial to do properly in Perl.
I think
On Aug 18, 2019, at 11:07 AM, Michael Richardson wrote:
> I think that Perl is now ubiquitous enough on Windows
We already require that Flex and Bison for Windows be installed for a libpcap
build; requiring that Perl for Windows be installed is probably not an
excessive requirement.
If "make
We build with gcc and clang on travis, with options that do not always match
what contributors get by default.
I've added "./buildem" which goes through the set of -m32/-m64 and clang, gcc
to build them all using build directories.
It runs "make check", which has been fixed to work in build
On Aug 18, 2019, at 7:03 PM, Michael Richardson wrote:
> Guy Harris wrote:
>> If "make check" required *only* Perl, not a Bourne-compatible shell,
>> that might also make running "make check" on Windows easier.
>
> That's probably a good enough reason.
Although there'd be more work required -
Guy Harris wrote:
> If "make check" required *only* Perl, not a Bourne-compatible shell,
> that might also make running "make check" on Windows easier.
That's probably a good enough reason.
___
tcpdump-workers mailing list