Re: [tcpdump-workers] [tcpdump] After setjmp/longjmp update
--- Begin Message --- On 18/12/2020 21:36, Francois-Xavier Le Bail via tcpdump-workers wrote: > The post setjmp/longjmp updates take more time than expected. About 30% of > the work is done. > To avoid keeping too long the other updates in the master branch, we plan to > release soon a 4.99.0 > version. 5.0.0 will be the released later when all the "pre-longjmp" logic > will be removed. > In this transitional step the only visible effect should be that the -x/-X > options will not always > show the link-layer header in truncation cases. Hello, Releases done: libpcap version 1.10.0 tcpdump version 4.99.0 https://www.tcpdump.org/index.html#latest-releases --- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] tcpdump build doc for Windows
--- Begin Message --- Hello list. tcpdump source tree has a short file named "Readme.Win32", which was mostly updated on 8 Aug 2019, and a longer file named "doc/README.Win32.md", which was mostly updated on 5 Feb 2020. These seem to provide somewhat different instructions, perhaps it would be a good time to review that. -- Denis Ovsienko --- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] tcpdump build doc for Windows
--- Begin Message --- On Jan 3, 2021, at 12:15 PM, Denis Ovsienko via tcpdump-workers wrote: > tcpdump source tree has a short file named "Readme.Win32", which was > mostly updated on 8 Aug 2019, and a longer file named > "doc/README.Win32.md", which was mostly updated on 5 Feb 2020. These > seem to provide somewhat different instructions, perhaps it would be a > good time to review that. They're both reasonably up-to-date (they both mention Npcap and the use of CMake), but the latter is more detailed. I'll check whether the first document says anything that's not mentioned in the second, and try to merge that into the second one. Then we can probably get rid of the first one. The top level README.md should probably point to doc/README.Win32.md (or README.Windows.md, given that 1) Windows can also be 64-bit and 2) 16-bit Windows is pretty much dead, so people are unlikely to get confused and say "OK, how do I build this 16-bit?", the answer to which is "we don't even support that on UN*X...".--- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] tcpdump build doc for Windows
--- Begin Message --- On Sun, 3 Jan 2021 14:23:40 -0800 Guy Harris wrote: [...] > They're both reasonably up-to-date (they both mention Npcap and the > use of CMake), but the latter is more detailed. > > I'll check whether the first document says anything that's not > mentioned in the second, and try to merge that into the second one. > Then we can probably get rid of the first one. Thank you. > The top level README.md should probably point to doc/README.Win32.md > (or README.Windows.md, given that 1) Windows can also be 64-bit and > 2) 16-bit Windows is pretty much dead, so people are unlikely to get > confused and say "OK, how do I build this 16-bit?", the answer to > which is "we don't even support that on UN*X...". I never thought about it, now that you pointed it out the bit width indeed looks out of place. -- Denis Ovsienko --- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
