- Previous thread: The FreeBSD Diary: 2009-05-30
- Next thread: Current unassigned ports problem reports
- Threads sorted by date: freebsd 200905
Hi Burce,
At first, I'm sorry replay late. I've test build libpcap without ports
and using same tar ball. The error message still output.
SLT2# make
gcc -O2 -I. -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -c
./pcap-null.c
./pcap-null.c:43: error: conflicting types for 'pcap_activate'
./pcap/pcap.h:266: note: previous declaration of 'pcap_activate' was here
*** Error code 1
Stop in /usr/ports/distfiles/libpcap-1.0.0.
SLT2#
Thank you!
-Leo
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
At first, I'm sorry replay late. I've test build libpcap without ports
and using same tar ball. The error message still output.
SLT2# make
gcc -O2 -I. -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -c
./pcap-null.c
./pcap-null.c:43: error: conflicting types for 'pcap_activate'
./pcap/pcap.h:266: note: previous declaration of 'pcap_activate' was here
*** Error code 1
Stop in /usr/ports/distfiles/libpcap-1.0.0.
SLT2#
Thank you!
-Leo
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Leo wrote:
> Hi Burce,
> At first, I'm sorry replay late. I've test build libpcap without ports
> and using same tar ball. The error message still output.
>
> SLT2# make
> gcc -O2 -I. -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -c
> ./pcap-null.c
> ./pcap-null.c:43: error: conflicting types for 'pcap_activate'
> ./pcap/pcap.h:266: note: previous declaration of 'pcap_activate' was here
> *** Error code 1
Hi,
I can't think what might be causing this for you... Do you have other
pcap libraries installed on the system? Perhaps a define is incorrect.
Are you trying this on a 7.2 or a HEAD system? I believe 7.2, so that
should rule out changes in HEAD.
Do you have BPF headers present on the system? Have you checked the
output of config.log? Do you have a bpf device in your kernel?
-- I think that might be it. The fix might be to specify
--with-pcap=bpf in CONFIGURE_ARGS in the port.
I just built the port on an i386 system tracking RELENG_7 sources, and
couldn't reproduce this problem, although I have bpf in kernel there.
thanks,
BMS
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
> Hi Burce,
> At first, I'm sorry replay late. I've test build libpcap without ports
> and using same tar ball. The error message still output.
>
> SLT2# make
> gcc -O2 -I. -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -c
> ./pcap-null.c
> ./pcap-null.c:43: error: conflicting types for 'pcap_activate'
> ./pcap/pcap.h:266: note: previous declaration of 'pcap_activate' was here
> *** Error code 1
Hi,
I can't think what might be causing this for you... Do you have other
pcap libraries installed on the system? Perhaps a define is incorrect.
Are you trying this on a 7.2 or a HEAD system? I believe 7.2, so that
should rule out changes in HEAD.
Do you have BPF headers present on the system? Have you checked the
output of config.log? Do you have a bpf device in your kernel?
-- I think that might be it. The fix might be to specify
--with-pcap=bpf in CONFIGURE_ARGS in the port.
I just built the port on an i386 system tracking RELENG_7 sources, and
couldn't reproduce this problem, although I have bpf in kernel there.
thanks,
BMS
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Bruce Simpson wrote:
> Leo wrote:
>> Hi Burce,
>> At first, I'm sorry replay late. I've test build libpcap without
>> ports and using same tar ball. The error message still output.
>>
>> SLT2# make
>> gcc -O2 -I. -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -c
>> ./pcap-null.c
>> ./pcap-null.c:43: error: conflicting types for 'pcap_activate'
>> ./pcap/pcap.h:266: note: previous declaration of 'pcap_activate' was
>> here
>> *** Error code 1
>
> Hi,
>
> I can't think what might be causing this for you... Do you have other
> pcap libraries installed on the system? Perhaps a define is incorrect.
>
> Are you trying this on a 7.2 or a HEAD system? I believe 7.2, so that
> should rule out changes in HEAD.
>
> Do you have BPF headers present on the system? Have you checked the
> output of config.log? Do you have a bpf device in your kernel?
> -- I think that might be it. The fix might be to specify
> --with-pcap=bpf in CONFIGURE_ARGS in the port.
>
> I just built the port on an i386 system tracking RELENG_7 sources, and
> couldn't reproduce this problem, although I have bpf in kernel there.
>
> thanks,
> BMS
>
Hi Bruce,
I don't have other pcap lib installed on this box. Previously installed
a libpcap 0.9 on this box , But I've deleted this version. On my box,
not enable BPF. Let me try if enable the feature.
-Leo
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
> Leo wrote:
>> Hi Burce,
>> At first, I'm sorry replay late. I've test build libpcap without
>> ports and using same tar ball. The error message still output.
>>
>> SLT2# make
>> gcc -O2 -I. -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -c
>> ./pcap-null.c
>> ./pcap-null.c:43: error: conflicting types for 'pcap_activate'
>> ./pcap/pcap.h:266: note: previous declaration of 'pcap_activate' was
>> here
>> *** Error code 1
>
> Hi,
>
> I can't think what might be causing this for you... Do you have other
> pcap libraries installed on the system? Perhaps a define is incorrect.
>
> Are you trying this on a 7.2 or a HEAD system? I believe 7.2, so that
> should rule out changes in HEAD.
>
> Do you have BPF headers present on the system? Have you checked the
> output of config.log? Do you have a bpf device in your kernel?
> -- I think that might be it. The fix might be to specify
> --with-pcap=bpf in CONFIGURE_ARGS in the port.
>
> I just built the port on an i386 system tracking RELENG_7 sources, and
> couldn't reproduce this problem, although I have bpf in kernel there.
>
> thanks,
> BMS
>
Hi Bruce,
I don't have other pcap lib installed on this box. Previously installed
a libpcap 0.9 on this box , But I've deleted this version. On my box,
not enable BPF. Let me try if enable the feature.
-Leo
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Leo wrote:
>
> I don't have other pcap lib installed on this box. Previously
> installed a libpcap 0.9 on this box , But I've deleted this version.
> On my box, not enable BPF. Let me try if enable the feature.
That's probably what it is. Can you try the following:
* give pcap configure --with-pcap=bpf WITHOUT having bpf in your kernel
config.
* try enabling bpf in kernel config and building the port as usual.
Most likely libpcap's new configure script is detecting the lack of
/dev/bpf* and assuming there is no packet capture support in the system.
This needs to be fixed for cross compiling to be possible. If you could
try at least the first fix then this is the answer.
thanks,
BMS
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>
> I don't have other pcap lib installed on this box. Previously
> installed a libpcap 0.9 on this box , But I've deleted this version.
> On my box, not enable BPF. Let me try if enable the feature.
That's probably what it is. Can you try the following:
* give pcap configure --with-pcap=bpf WITHOUT having bpf in your kernel
config.
* try enabling bpf in kernel config and building the port as usual.
Most likely libpcap's new configure script is detecting the lack of
/dev/bpf* and assuming there is no packet capture support in the system.
This needs to be fixed for cross compiling to be possible. If you could
try at least the first fix then this is the answer.
thanks,
BMS
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Bruce Simpson wrote:
> Leo wrote:
>>
>> I don't have other pcap lib installed on this box. Previously
>> installed a libpcap 0.9 on this box , But I've deleted this version.
>> On my box, not enable BPF. Let me try if enable the feature.
>
> That's probably what it is. Can you try the following:
> * give pcap configure --with-pcap=bpf WITHOUT having bpf in your
> kernel config.
> * try enabling bpf in kernel config and building the port as usual.
>
> Most likely libpcap's new configure script is detecting the lack of
> /dev/bpf* and assuming there is no packet capture support in the
> system. This needs to be fixed for cross compiling to be possible. If
> you could try at least the first fix then this is the answer.
>
> thanks,
> BMS
>
>
Hi Bruce,
I've tried 2 method on my box. that you previously mentioned. Both of
these 2 method can build successfully! Thank your for your help!!
Best Regards!
-Leo
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
> Leo wrote:
>>
>> I don't have other pcap lib installed on this box. Previously
>> installed a libpcap 0.9 on this box , But I've deleted this version.
>> On my box, not enable BPF. Let me try if enable the feature.
>
> That's probably what it is. Can you try the following:
> * give pcap configure --with-pcap=bpf WITHOUT having bpf in your
> kernel config.
> * try enabling bpf in kernel config and building the port as usual.
>
> Most likely libpcap's new configure script is detecting the lack of
> /dev/bpf* and assuming there is no packet capture support in the
> system. This needs to be fixed for cross compiling to be possible. If
> you could try at least the first fix then this is the answer.
>
> thanks,
> BMS
>
>
Hi Bruce,
I've tried 2 method on my box. that you previously mentioned. Both of
these 2 method can build successfully! Thank your for your help!!
Best Regards!
-Leo
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Related Threads
- [PATCH] pci/intr_remapping: allocate irq_iommu on node - kernel
- ANN: RDF2RDFa :Turning RDF/XML into Snippets for Copy-and-Paste - web
- ConsumerEventSource and wildcards. Different behaviours between Topics and Queues - activemq
- [PATCH]: Valid pointer modes for Alpha/VMS - gcc
- Mejor desconectarlo? - openbsd
- jaunty » karmic - ubuntu
- pexpect on QNX platform - python
- [Committed] S/390: Fix jump prediction for long loops on z10 - gcc
- Quick Test - postfix
- [HACKERS] Bug in visibility hint bit - pgsql
- Important Customer Notification - netbsd
- [PATCH] cifs.upcall: do a brute-force search for KRB5 credcache - samba