Re: AC_LBL_FIXINCLUDES does not make it into configure

[Denis Ovsienko via tcpdump-workers <tcpdump-workers () lists tcpdump org>]

> --- Begin Message ---
>
>
> From: Denis Ovsienko <denis () ovsienko info>
>
> Date: Thu, 19 Jan 2023 23:20:23 +0000
>
> On Wed, 18 Jan 2023 15:53:21 -0800
> Guy Harris <gharris () sonic net> wrote:
>
> > On Jan 18, 2023, at 3:32 PM, Denis Ovsienko via tcpdump-workers
> > <tcpdump-workers () lists tcpdump org> 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 used in some LBL projects but not libpcap or tcpdump.
>
> So, libpcap and tcpdump have lost a few unused macros as well.  I did
> NOT touch the following unused AC_DEFUNs in tcpdump aclocal.m4:
>
> * AC_LBL_CHECK_64BIT_FORMAT -- this used to define the PRI[doux]64
>   conversion specifiers before C99 became required/presumed.  I wonder
>   if this presumption is subject to the same problem as the sizeof
>   length modifier: the compiler might be C99, but the libc may be not.
>   If trying to compensate for this [again] would be a waste of effort
>   and the best move would be to delete the macro, at least the build
>   system could verify that all the required printf() features are in
>   place -- in fact, a single piece of C code could exercise as many
>   printf() features as required in one go and fail if at least one of
>   those failed.  Or would it be over-engineering?
>
> * AC_LBL_SSLEAY -- is there anything useful to take from here?
>
> -- 
>     Denis Ovsienko
>
> --- End Message ---
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers