On Apr 8, 2025, at 7:13 AM, Mahesh V <maheshvenkateshwa...@gmail.com> wrote:
> 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) That's a good question. I do not know the answer, as I was not involved in producing the flex binary. Perhaps you should talk to the person who checked the binary into the repository. This is not a libpcap issue; all we could do is to have the configure script try to run flex without the command-line arguments and, if that fails, report that flex doesn't work, tell the person trying to build libpcap that they need to somehow arrange to have a flex that works, and fail. _______________________________________________ tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
