Speaking of x.9 changes, if we're going to be doing x.9.2 soon to fix
various problems, should I also make pcap_fopen_offline(), pcap_file(),
pcap_fileno(), pcap_dump_fopen(), and pcap_dump_file() UN*X-only, as per
the discussions about the issues with different flavors of MSVC++'s C
libraries
Michael Richardson wrote:
-BEGIN PGP SIGNED MESSAGE-
"Loris" == Loris Degioanni <[EMAIL PROTECTED]> writes:
Loris> There is an issue compiling 3.9.1 in Windows. The problem is
Loris> that my last patch to win32\prj\windump.dsp (2005/6/4) was
Loris> not propagated to the
-BEGIN PGP SIGNED MESSAGE-
> "Loris" == Loris Degioanni <[EMAIL PROTECTED]> writes:
Loris> There is an issue compiling 3.9.1 in Windows. The problem is
Loris> that my last patch to win32\prj\windump.dsp (2005/6/4) was
Loris> not propagated to the tcpdump_3_9 branch, and th
Guy Harris wrote:
Loris Degioanni wrote:
There is an issue compiling 3.9.1 in Windows. The problem is that my
last patch to win32\prj\windump.dsp (2005/6/4) was not propagated to
the tcpdump_3_9 branch,
Most of us checking in changes were checking them into both branches, so
we might have
Loris Degioanni wrote:
There is an issue compiling 3.9.1 in Windows. The problem is that my
last patch to win32\prj\windump.dsp (2005/6/4) was not propagated to the
tcpdump_3_9 branch,
Most of us checking in changes were checking them into both branches, so
we might have missed a change check
There is an issue compiling 3.9.1 in Windows. The problem is that my
last patch to win32\prj\windump.dsp (2005/6/4) was not propagated to the
tcpdump_3_9 branch, and therefore the CVS snapshot compiles, but 3.9.1
fails in print-dhcp6.c.
If you're planning to do a subrelease to fix the -A flag
