s part of CMake may already do
> that.)
The current master branch produces a much cleaner output for "make -s"
with XL C, thank you!
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdum
arguments parsing space are not handled the same way as warnings that
come from the C language compilation space.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/
ers.
--
Denis Ovsienko
./missing/getopt_long.c: In function 'permute_args':
./missing/getopt_long.c:163:5: error: cast discards '__attribute__((const))'
qualifier from pointer target type [-Werror=cast-qual]
./missing/getopt_long.c:165:5: error: cast discards '__attribute__((const))'
qualifier f
upgraded from
2.69 to 2.71.
Cheers.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
t be a good time to migrate to a current version
of autoconf (2.69 seems to be a popular choice).
--
Denis Ovsienko
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
which can also handle DHCP and the serial port console),
or maybe even a non-PC device if that floats your boat.
--
Denis Ovsienko
e are all trivial bugfixes.
--
Denis Ovsienko
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
--- Begin Message ---
On Mon, 5 Apr 2021 10:42:39 +0100
Denis Ovsienko via tcpdump-workers
wrote:
> Hello list.
>
> I hope you have a great day. Please find below a brief overview of
> some current continuous integration matters.
Please find below a few recent developments si
s specific to USB 3 or some
specific workload your board is trying to run.
--
Denis Ovsienko
/place-name-props/-/raw/master/examples/export.pdf
--
Denis Ovsienko
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
his
exact revision ID (b03114). Network transfer speeds look normal. That
said, it looks like "revision 1.4" recently started to mean more than
one hardware configuration:
https://lists.freebsd.org/pipermail/freebsd-arm/2021-April/023669.html
--
Denis Ovsienko
as been using multiple window UI for many years, and the
users figure the GUI out just fine.
So a multiple window GUI makes a sound use case and it would be nice
to keep it reasonably accessible.
--
Denis Ovsienko
___
grass-dev mailing list
gr
itself almost
immediately, but takes 10 minutes of real time to get into shape. So a
solution within the Buildbot space might be better long-term.
--
Denis Ovsienko
___
users mailing list
users@buildbot.net
https://lists.buildbot.net/mailman/listinfo/users
Would that be a better solution?
--
Denis Ovsienko
___
users mailing list
users@buildbot.net
https://lists.buildbot.net/mailman/listinfo/users
emon
--idle-timeout 60", so as soon as the worker has no new work for a
minute, it exits and the Jenkins build concludes.
Do you think this would be a useful addition? If somebody implements
anything along these lines, I would be glad to test the new feature.
--
Denis Ovsienko
_
runs out of
RAM.
For the time being I have worked around the problem by adding a swap
partition. If anybody is willing to look into the issue, let me know
what other information you need.
--
Denis Ovsienko
issues should manifest. It would be great if someone
could look into these issues, identify the reasons for failure and tell
what can be fixed easily.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers
--- Begin Message ---
On Wed, 24 Mar 2021 00:52:00 +0100
Harald Welte wrote:
> Hi Denis,
>
> On Tue, Mar 23, 2021 at 12:35:06AM +0000, Denis Ovsienko via
> tcpdump-workers wrote:
> > That's great, three worker types are ready to go anytime soon, just
> > decide which
--- Begin Message ---
On Mon, 22 Mar 2021 19:00:31 +0100
Harald Welte wrote:
> Dear Denis,
>
> On Sun, Mar 21, 2021 at 11:08:44PM +0000, Denis Ovsienko via
> tcpdump-workers wrote:
> > Thank you for the offer. For the operating systems specifics please
> >
elf.
Let me know which ARM workers look feasible to you. If you can host
PowerPC workers instead or in addition to that, it would help too.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdu
to host any of the following buildbot workers
long-term?
* linux-aarch64 (currently on a RPI4B running in 64-bit mode)
* linux-armv7l (currently on a RPI4B running in 32-bit mode)
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcp
--- Begin Message ---
On Thu, 4 Mar 2021 00:42:23 -0800
Guy Harris wrote:
> On Mar 3, 2021, at 2:30 PM, Denis Ovsienko via tcpdump-workers
> wrote:
>
> > A partial replacement for that service is ci.tcpdump.org, which is a
> > buildbot instance doing Linux AArch64 buil
--- Begin Message ---
On Fri, 12 Feb 2021 16:18:10 +
Denis Ovsienko via tcpdump-workers
wrote:
[...]
> The Travis CI subscription will cease in early March (unless there is
> a sponsor willing to pay 82.80 USD per month). At this time the
> impact of that would be the following:
>
nother layer of software on top of these two, so a student
can finally get their thesis done.
--
Denis Ovsienko
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
. That said, if you have suggestions in addition or
instead of that, please make them on the list to be considered.
Thanks.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https
it is not the case.
Thus, as far as I can figure it out, if GRASS developers at some point
establish that C17 gives GRASS particular significant technical
advantages, it should be fine to declare C17 the house standard if (and
only if) your currently active platforms reliably support C17.
t.
I had requested a renewable OSS allowance on 29 January, got the
template response and confirmed the details. Let's see where it goes.
The account is at 3790/1 credits as of today, in other words, three
more builds of libpcap or at most one tcpdump build, if/when the latter
migrates.
--
ion is imminent. If anybody
has useful input to make, please do not delay.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
--- Begin Message ---
On Wed, 9 Sep 2020 17:07:25 +0100
Denis Ovsienko via tcpdump-workers
wrote:
> Here are my steps to reproduce:
>
> libpcap$ ./configure --enable-remote --prefix=/tmp/libpcap
> libpcap$ make
> libpcap$ make install
> tcpdumpbuild$ cmake
--- Begin Message ---
On Thu, 21 Jan 2021 08:15:33 +0100
Dagobert Michelsen wrote:
> Hi folks,
>
> Am 21.01.2021 um 04:24 schrieb Denis Ovsienko via tcpdump-workers
> :
> >>s390x (a/k/a z/Architecture, i.e. S/3x0-64) - a big-endian
> >> platform, so we ca
icate whether to
> fault or allow unaligned accesses, and I haven't checked whether
> Linux enables them or not);
>
> s390x (a/k/a z/Architecture, i.e. S/3x0-64) - a big-endian
> platform, so we can do some testing of operation on big-endian
> machines.
>
> I don't
|yes |no | 1741 | yes
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
oo old, instead of failing the build outright?
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
te now. That said, a
weekly/fortnightly status update on the list could be a useful addition.
Cheers.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
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
ns, 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
nate someone, so if there is a formal requirement for me to be on a
list of contributors, please add me there. Thank you.
--
Denis Ovsienko
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
think and if you need additional information.
--
Denis Ovsienko
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
n details. Could you
figure out which keywords and which parameters this problem seems to
need and post that to the list first?
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
you mean to introduce a function like pcap_error(), which the
developers would be able to interrogate if they need in use cases like
this? Then existing functions could be slowly updated as needed to store
the fault details somewhere for that function.
--
Denis Ovsienko
--- En
--- Begin Message ---
On Fri, 25 Sep 2020 03:04:21 +0100
Denis Ovsienko via tcpdump-workers
wrote:
[...]
> == Summary: the method seems to work well, there is a clean reference
> implementation, it should be easy to apply to other printers that
> implement similar encodings,
ps://grass.osgeo.org/contribute/development/
(which is https://github.com/OSGeo/grass/), or maybe something else.
--
Denis Ovsienko
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
--- Begin Message ---
On Thu, 17 Sep 2020 15:15:25 +0100
Denis Ovsienko via tcpdump-workers
wrote:
> On Sat, 5 Sep 2020 18:20:42 +0200
> Francois-Xavier Le Bail via tcpdump-workers
> wrote:
>
> > 2) Process all the truncated cases with:
> > ndo->ndo_ll_h
print */ }
[...]
The switch block should also have a default case, which ideally should
never happen, but if it somehow happens, it should either fail the
current packet safe or just call ndo_error().
--
Denis Ovsienko
--- End Message ---
')
[...]
It could be simpler and more reliable to reset or to ignore
ndo->ndo_ll_hdr_len in pretty_print_packet() after "returning" from
setjmp for the second time (longjmp() can happen in many different
places, but there is only one setjmp()).
--
invalid cases (bad
> length, etc.) */
That could be another way of doing the same thing. In some programs that
could be the best or the only way to tell the reason for returning in a
thread-safe manner, but in this case struct netdissect_options makes it
really easy.
--
Denis Ovsienko
--- En
d if that other reason requires a
different handling in pretty_print_packet(), then that would be a
straightforward way to do that, yes.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
master branch now has a change along these lines. Whilst preparing
changes to a couple decoders based on that (still work in progress), I
managed to make some observations, will post as soon as it all looks
good and makes sense.
--
Denis Ovsien
.)
or
-x ... (In this version of tcpdump this flag always works as the -xx
flag below.)
Would this help?
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
lows a human to make a mistake, mistakes
will happen, if not in one implementation then in another. So it would
make sense to look into this with attention if the goal is to produce a
good design.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-worker
--- Begin Message ---
On Thu, 27 Aug 2020 12:58:10 +0100
Denis Ovsienko via tcpdump-workers
wrote:
> Hello list.
>
> tcpslice master branch now installs the binary into bindir instead of
> sbindir, see [1]. Guy had suggested to make the same change in
> tcpdump.
[...]
The a
roup/tcpdump/jobs/724717360
2: https://travis-ci.org/github/the-tcpdump-group/tcpdump/jobs/721706654
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
--- Begin Message ---
On Mon, 7 Sep 2020 17:26:28 +0200
Francois-Xavier Le Bail wrote:
> On 07/09/2020 16:43, Denis Ovsienko via tcpdump-workers wrote:
> > On Sat, 5 Sep 2020 18:20:42 +0200
> > Thank you for posting a detailed explanation and making the first
> > round of
0f0f
> 0x0040: 0f0f 0016 88
I confirm the patch changes the hex output exactly as described.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
)
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
for as long as it compiles?
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
t should probably define ND_MIN() and ND_MAX() instead.
Alright, that's done now.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
--- Begin Message ---
> That's where other "some of what this manual page says doesn't apply
> to older versions of libpcap" items go, so it'd make sense.
Alright, that's done now, thanks!
--
Denis Ovsienko
--- End Message ---
___
of cnt.)
Would it make sense to move this paragraph to a BACKWARD COMPATIBILITY
section and to tell which specific version started to recognise 0 as a
valid value?
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump
--- Begin Message ---
On Wed, 19 Aug 2020 00:51:11 +0100
Denis Ovsienko via tcpdump-workers
wrote:
[...]
> Also, the current Travis CI build matrix expands to 108 (!) jobs, so
> if you are making a trivial commit (such as in the man pages or the
> documentation), please remember to sk
or the
documentation), please remember to skip the CI build with [skip ci] as
described here:
https://docs.travis-ci.com/user/customizing-the-build/#skipping-a-build
The service is free for us to use, but it is not free for somebody else
to provide.
--
Denis Ovsienko
--- End Message
id grounds to stop within 24 hours, tcpslice 1.3 by
The Tcpdump Group will be out.
Thank you.
1: https://github.com/the-tcpdump-group/tcpslice/blob/master/CHANGES
2: https://github.com/the-tcpdump-group/tcpslice/issues/7
--
Denis Ovsienko
--- E
[...]
I have prepared changes that include headers from /usr/include/netinet
instead and am going to commit it tomorrow after proof-reading and
confirming it builds on different systems.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mai
the two functions are
similar. Would it be the right thing to do?
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
; branch so it does not mislead
whoever is looking into this history next.
Cheers.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
; branch so it does not mislead
whoever is looking into this history next.
Cheers.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
the two functions are
similar. Would it be the right thing to do?
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
of the error. AFAIK the cipher
name finally can be anything that OpenSSL recognises as such.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
, and to say it in a LICENSE file for clarity?
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
--- Begin Message ---
On Wed, 29 Jan 2020 10:59:14 +0100
Francois-Xavier Le Bail wrote:
> On 28/01/2020 23:17, Denis Ovsienko via tcpdump-workers wrote:
> > The new dependency makes it more difficult to run tests and will
> > break package builds downstream (thus penalising pe
=> '-e',
},
'isakmp4' => {
'pcap' => 'isakmp4500.pcap',
'text' => 'isakmp4.out',
'args' => "-E \"file ${testsdir}/esp-secrets.txt\"",
'when' => $can_test_openssl,
},
);
Does it make sen
eone looking at it?
Both the report and the CVE allocation are duplicate. The reporter decided to
jump ahead. The problem will be fixed.
--
Denis Ovsienko
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
-by: Denis Ovsienko
---
Documentation/gitweb.conf.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/gitweb.conf.txt b/Documentation/gitweb.conf.txt
index c0a326e38..83b4388c2 100644
--- a/Documentation/gitweb.conf.txt
+++ b/Documentation/gitweb.conf.txt
@@ -207,8
R
Myricom SNF library directory, if not DIR/lib
Do you think the same would work best for cross-compiling with bluetooth
support?
On a related note, since libpcap now uses both configure and cmake, the change
to the options should be made in a similar way in bo
.
--
Denis Ovsienko
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
e to remove --enable-smb/--disable-smb (enable possibly-buggy SMB
> printer) code ?
To me the flag mainly serves as a reminder to merge tcpdump pull request #518.
--
Denis Ovsienko
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
ors (forgetting...).
>
> Could we do things differently ?
With things done this way it looks like this issue could happen, although it
would result in incorrect labeling, not incorrect behaviour.
A possible solution could be some stack structure and a macro to call the next
function, which m
hdr = (const struct ieee80211_radiotap_header
> *)p;
> +len =
> EXTRACT_LE_16BITS(>it_len);
> +
> + hdrlen = ieee802_11_radio_print(ndo, p, h->len,
> h->caplen);
> + if (nd
ure each time they need a different mask
length.
I agree in some cases it is best to mask the endpoints right at the capture
time, but do you see the use case for offline masking (as in "tcpdump -r
infile.pcap -w outfile.pcap ")?
--
Denis Ovsienko
ts_date_hmsfrac_print() as well, if time_flag isn't
> LOCAL_TIME?
Looks like so.
--
Denis Ovsienko
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
s about this matter. I
have already explained the problem on the list, several times over, and I have
raised exactly the points I was going to raise. If Barbara or anybody else has
anything to add, please do it on the list under your name, like I do.
On Mon, 06 Aug 2018 09:51:36 +0100 John Hawkinson wrote
> Denis Ovsienko wrote on Mon, 6 Aug 2018
> at 09:42:16 +0100 in
> <1650e66b5ad.12b3ab99e15597.8336631397456496...@ovsienko.info>:
>
> > When a network protocol has a timestamp and
On Sun, 05 Aug 2018 18:21:47 +0100 John Hawkinson wrote
> Denis Ovsienko wrote on Sun, 5 Aug 2018
> at 17:05:20 +0100 in
> <1650ad5fd29.b5d2798f311917.536858429581803...@ovsienko.info>:
>
> > It works in an interactive session; but as
On Sun, 05 Aug 2018 14:12:31 +0100 Francois-Xavier Le Bail
wrote
> On 05/08/2018 14:46, Denis Ovsienko wrote:
> > On Sat, 04 Aug 2018 08:41:10 +0100 Francois-Xavier Le Bail
> > wrote
> > > On 04/08/2018 09:03, Guy Harris wrote:
> >
just change it to use gmtime() rather than localtime().
>
> I think an user prefer have the local time.
--
Denis Ovsienko
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
ng) -- it just copies the error in the
registry allocation.
I do not see a good way to accept both encodings for this attribute, given the
way each encoding is defined. Are you aware of any other code that has copied
this error, especially in the network devices firmware?
--
Deni
On Fri, 13 Jul 2018 08:40:47 +0100 Denis Ovsienko
wrote
> On Thu, 12 Jul 2018 20:38:08 +0100 Guy Harris
> wrote
> > On Jul 12, 2018, at 11:33 AM, Petr Vorel wrote:
> >
> > > +#ifdef PCAP_SUPPORT_SLL_V2
> &g
On Mon, 30 Jul 2018 02:08:51 +0100 Guy Harris wrote
> On Jul 29, 2018, at 5:48 AM, Denis Ovsienko wrote:
>
> > Building (configure+gcc) tcpdump master branch with libpcap 0.6.1 yields
> > the following compiler warnings, some of which are as
Let's see if my message makes it through the filters this time...
Forwarded message
From : Denis Ovsienko
To : "tcpdump-workers"
Date : Tue, 24 Jul 2018 14:07:58 +0100
Subject : about bits and frequencies
Forwarded message
&g
_builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
^~~~
__bos (__s), __fmt, __va_arg_pack ());
~~~~~
--
Denis Ovsienko
___
tcpdump-wor
On Wed, 18 Jul 2018 17:45:43 +0100 Denis Ovsienko
wrote
[...]
> Is there anybody on this list (or anybody you could forward this to), who
> could interpret the code flow in print-rx.c and address the fall-through
> warnings (break from the case or mark up as a gen
e
number portability, the only way to guarantee DNS zone portability would be
through a law or government regulation. Most ISPs are just in a different
business.
--
Denis Ovsienko
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
On Wed, 25 Jul 2018 09:11:23 +0100 Guy Harris wrote
> On Jul 25, 2018, at 12:57 AM, Denis Ovsienko wrote:
>
> > Roughly a half of the libpcap man pages text uses the values -1 and -2 to
> > discuss the return value of particular libpcap functions, the oth
consistently in all man pages?
--
Denis Ovsienko
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
provisions are there, but I
did not see them, in that case please disregard the comment.
Feel free to use this input to improve the document, if it gives you any new
ideas.
--
Denis Ovsienko
___
homenet mailing list
homenet@ietf.org
https
use cmake to build any software, so this is my interpretation, feel
free to correct.
Perhaps if someone had written down, in plain English, which specific steps it
takes to compile tcpdump/libpcap, it would be easier to see if it can be done
with a simple shell script.
--
Denis Ovsienko
touch .devel" before "./configure" will enable all warnings for the tcpdump
build and yield current line numbers (the bug report is 1 year old). I am not
sure which version of GCC started to report those issues, version 7.3.0
definitely does it.
--
Denis Ovsienko
_
contribute a quality patch to make the code up to date, but that sounds too
good to be true, I know.
Thank you.
--
Denis Ovsienko
___
OpenAFS-devel mailing list
OpenAFS-devel@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-devel
On Fri, 13 Jul 2018 08:40:47 +0100 Denis Ovsienko
wrote
> On Thu, 12 Jul 2018 20:38:08 +0100 Guy Harris
> wrote
> > On Jul 12, 2018, at 11:33 AM, Petr Vorel wrote:
> >
> > > +#ifdef PCAP_SUPPORT_SLL_V2
> &g
length, as
Guy mentioned a couple days ago.
> Should we add that the padding is done with '\0' bytes ?
As far as encodings typically go, if the padding bytes are always discarded, it
does not make difference. But it will not hurt to say the customary "MBZ".
--
Denis Ovsienko
___
101 - 200 of 348 matches
Mail list logo
