Re: [tcpdump-workers] {clang, gcc} X {i386, x86_64} building, and docker/travis
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 runs "make check", which has been fixed to work in build directories. From my experience, it's not the same to build with 1) compiler for arch i386 (e.g. debian packages xxx:i386) than with 2) compiler for arch amd64 with -m32 option. Some problem are only seen with 1). -- Francois-Xavier ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] TESTrun.sh and TESTonce -> combining into single perl driver?
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 that Perl is now ubiquitous enough on Windows that we could just use one program to drive it all? OpenSSL uses the Perl unit test framework; I'm not sure I'd want to go that far, but I'd consider it. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works|IoT architect [ ] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails[ ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] TESTrun.sh and TESTonce -> combining into single perl driver?
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 check" required *only* Perl, not a Bourne-compatible shell, that might also make running "make check" on Windows easier. ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] {clang, gcc} X {i386, x86_64} building, and docker/travis
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 directories. I think that I will added -Werror to the list, as I see some errors. I'd like to get coverage of more versions of gcc, and maybe this calls for a docker/LXC container to do this. This would also solve the problem of what travis uses does not reflect what we have on our different desktops. I don't really want to impose docker/etc. on people just want to build stuff. I didn't find a ppa that would work on debian stable/xenial that would have gcc 8 and 9, but maybe I didn't look hard enough. (I guess I am spoilt by places like postgresql that maintain new versions for stable OS installs. Of course, gcc being such a critical build component, this is harder). If I change the .travis build to do docker, I will add it as another part of the matrix. I guess doing it as a Dockerfile *build* will be easier as that will let the current directory be pushed into the docker image for compilation. I am looking for sources for reasonable, minimal, but not too lacking in libfoobar support docker images for: debian-stable debian-testing ubuntu-lts ubuntu-19.xx fedora centos7 Will travis cache these reasonably, or is this going to be a four hour disaster? -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works|IoT architect [ ] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails[ ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] TESTrun.sh and TESTonce -> combining into single perl driver?
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 - TESTonce depends on having cat, diff, and sed, and crypto.sh depends on grep, for example. ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] TESTrun.sh and TESTonce -> combining into single perl driver?
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 tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
