[tcpdump-workers] CPPFLAGS in C-only context
--- Begin Message --- Hello all. There is one other thing in Autoconf files of tcpslice and tcpdump that jumped out at me: savedcppflags="$CPPFLAGS" CPPFLAGS="$CPPFLAGS $V_INCLS" AC_CHECK_HEADERS(pcap/pcap-inttypes.h) AC_CHECK_FUNCS(pcap_lib_version) CPPFLAGS="$savedcppflags" It looks like either in a C project context CPPFLAGS works in a non-obvious way, or is a no-op. -- Denis Ovsienko --- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] CPPFLAGS in C-only context
--- Begin Message --- On Mon, 23 Jan 2023 22:16:24 + Denis Ovsienko via tcpdump-workers wrote: > It looks like either in a C project context CPPFLAGS works in a > non-obvious way, or is a no-op. ...or, rather, is the C preprocessor flags variable (just as "./configure --help" says it), and C++ compiler flags variable has always been CXXFLAGS. -- Denis Ovsienko --- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] CPPFLAGS in C-only context
--- Begin Message --- On Jan 28, 2023, at 2:01 PM, Denis Ovsienko via tcpdump-workers wrote: > On Mon, 23 Jan 2023 22:16:24 + > Denis Ovsienko via tcpdump-workers > wrote: > >> It looks like either in a C project context CPPFLAGS works in a >> non-obvious way, or is a no-op. > > ...or, rather, is the C preprocessor flags variable (just as > "./configure --help" says it), and C++ compiler flags variable has > always been CXXFLAGS. Unfortunately, "+" is not a letter in the Roman alphabet, so C++ causes some naming problems.--- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers