Re: [tcpdump-workers] AC_LBL_FIXINCLUDES does not make it into configure

2023-01-18 Thread Guy Harris via tcpdump-workers
--- Begin Message --- On Jan 18, 2023, at 3:32 PM, Denis Ovsienko via tcpdump-workers wrote: > As it turns out, there is another unused macro (AC_LBL_HAVE_RUN_PATH), > tcpslice became the first to lose this luggage. Unused in libpcap back to 0.4 and tcpdump back to 3.4, so it may be another one

Re: [tcpdump-workers] AC_LBL_FIXINCLUDES does not make it into configure

2023-01-18 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Wed, 18 Jan 2023 09:22:28 -0500 Michael Richardson wrote: > I haven't heard a clear argument as to what autoconf/configure gets > us today over cmake, and maintaining both seems a huge waste of > energy. There's a comment buried in one of the build files: a release tarba

Re: [tcpdump-workers] AC_LBL_FIXINCLUDES does not make it into configure

2023-01-18 Thread Guy Harris via tcpdump-workers
--- Begin Message --- On Jan 18, 2023, at 1:07 AM, Denis Ovsienko wrote: > Thank you for explaining the context Guy, it is very educational. A significant part of what's in autoconf, and a significant part of what's in at least some configure scripts, dates back to old UN*Xes. ISO C and POSIX

Re: [tcpdump-workers] AC_LBL_FIXINCLUDES does not make it into configure

2023-01-18 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Tue, 17 Jan 2023 18:35:58 -0800 Guy Harris wrote: > If you're curious what AC_LBL_FIXINCLUDES is for, and why most > platforms don't need it, continue reading. Thank you for explaining the context Guy, it is very educational. Is AC_LBL_UNION_WAIT of a similar origin? N