I dont have that information.
Question remains, why does flex choose m4 binary that is compiled into it
and not from the PATH (env variable)
which m4 and which flex (both exist in the same path)
On Mon, Apr 7, 2025 at 11:34 PM Guy Harris wrote:
> On Apr 7, 2025, at 2:11 AM, Mahesh V
>
Flex is not getting built. We have the binary checked in to our repository.
"which flex" gives the same path : tools/arm-5.3-uclibc-1.0.12/usr/bin/flex
On Mon, Apr 7, 2025 at 2:19 PM Guy Harris wrote:
> On Apr 6, 2025, at 11:19 PM, Mahesh V
> wrote:
>
> > configur
Forwarded message --
> From: Denis Ovsienko
> To: tcpdump-workers@lists.tcpdump.org
> Cc:
> Bcc:
> Date: Mon, 7 Apr 2025 09:09:57 +0100
> Subject: [tcpdump-workers] Re: tcpdump and pcapng with comments
> On Mon, 7 Apr 2025 11:49:49 +0530
> Mahesh V wrote:
>
> > m
t 2:28 PM, Michael Richardson wrote:
>
> > Mahesh V wrote:
> >> I added some code (modified) tcpdump to write the pcapng file.
> >> while configuring/compiling the source code I get this error
> >> This is a cross compilation for ARM platform
> >
> >
Just to clarify, I am building libpcap (where I have added the code)
tcpdump compilation is fine but obviously gives symbol error because
libpcap is bot yet built.
thanks
On Sun, Apr 6, 2025 at 2:41 PM Mahesh V
wrote:
> Hi Folks
>
> I added some code (modified) tcpdump to write the pc
Hi Folks
I added some code (modified) tcpdump to write the pcapng file.
while configuring/compiling the source code I get this error
This is a cross compilation for ARM platform
configure: error: *flex is insufficient to compile libpcap.*
libpcap requires Flex 2.5.31 or later, or a compatible ve
socket to tcpdump in user space)
3) read it later on. (I believe this functionality is available today or
alternatively even wireshark would be ok to do this for me)
Is this functionality available today or do we need to build it?
thanks in advance
On Fri, Apr 4, 2025 at 10:41 PM Mahesh V
wrote
