Opened 3 years ago
Closed 3 years ago
#63766 closed defect (duplicate)
fragroute: error: conflicting types for 'pcap_open'
Reported by: | YKPCLN | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.1 |
Keywords: | Cc: | ||
Port: | fragroute |
Description (last modified by reneeotten (Renee Otten))
Error Command : Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_fragroute/fragroute/work/fragroute-1.2" && /usr/bin/make -j4 -w all
I got some errors like below when I run that command manually.
In file included from pcaputil.c:27: ./pcaputil.h:12:9: error: conflicting types for 'pcap_open' pcap_t *pcap_open(char *device); ^ /opt/local/include/pcap/pcap.h:1084:18: note: previous declaration is here PCAP_API pcap_t *pcap_open(const char *source, int snaplen, int flags, ^ pcaputil.c:32:1: error: conflicting types for 'pcap_open' pcap_open(char *device) ^ /opt/local/include/pcap/pcap.h:1084:18: note: previous declaration is here PCAP_API pcap_t *pcap_open(const char *source, int snaplen, int flags, ^ pcaputil.c:38:17: warning: 'pcap_lookupdev' is deprecated: use 'pcap_findalldevs' and use the first device [-Wdeprecated-declarations]
Thanks all for your helps...
Change History (3)
comment:1 Changed 3 years ago by reneeotten (Renee Otten)
Description: | modified (diff) |
---|---|
Keywords: | #fragroute # removed |
Milestone: | MacPorts Future |
Summary: | FragRoute Build Error CHILDSTATUS 54454 2 → fragroute: build fails |
comment:2 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Summary: | fragroute: build fails → fragroute: error: conflicting types for 'pcap_open' |
---|
Duplicate of #58549.
comment:3 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
please attach the
main.log
file as mentioned in the error message from MacPorts to this ticket. Also please note that there is no maintainer for this port, so if you find/know a fix for this please consider submitting a PR.