@@ -807,7 +807,8 @@ check_function_exists(pcap_dump_ftell64 HAVE_PCAP_DUMP_FTELL64)
807
807
# to use when linking.)
808
808
#
809
809
# This means that check_function_exists() will think that
810
- # the remote-capture APIs are present, including pcap_open().
810
+ # the remote-capture APIs are present, including pcap_open()
811
+ # and pcap_findalldevs_ex().
811
812
#
812
813
# However, they are *not* present in macOS Ventura and earlier,
813
814
# which means that building on Ventura with Xcode 15 produces
@@ -827,14 +828,14 @@ check_function_exists(pcap_dump_ftell64 HAVE_PCAP_DUMP_FTELL64)
827
828
# Given all that, and given that the versions of the
828
829
# remote-capture APIs in Sonoma are stubs that always fail,
829
830
# there doesn't seem to be any point in checking for pcap_open()
830
- # if we're linking against the Apple libpcap.
831
+ # and pcap_findalldevs_ex() if we're linking against the Apple libpcap.
831
832
#
832
833
# However, if we're *not* linking against the Apple libpcap,
833
834
# we should check for it, so that we can use it if it's present.
834
835
#
835
- # So we check for pcap_open if 1) this isn't macOS or 2) the
836
- # the libpcap we found is not a system library, meaning that
837
- # its path begins neither with /usr/lib (meaning it's a system
836
+ # So we check for pcap_open() and pcap_findalldevs_ex() if 1) this isn't
837
+ # macOS or 2) the the libpcap we found is not a system library, meaning
838
+ # that its path begins neither with /usr/lib (meaning it's a system
838
839
# dylib) nor /Application/Xcode.app (meaning it's a file in
839
840
# the Xcode SDK).
840
841
#
0 commit comments