the version 1.13 as shipped on latest portsnap update fails to compile with the following error from portmaster:
# portmaster -gdb security/barnyard2
cc -DHAVE_CONFIG_H -I. -I../.. -I.. -I ../sfutil -DSUP_IP6 -I/usr/local/include -I/usr/local/include -DBROCCOLI -O2 -pipe -fstack-protector -fno-strict-aliasing -m64 -Wall -c -o spo_alert_fwsam.o spo_alert_fwsam.c
spo_alert_fwsam.c:118:13: error: cannot combine with previous 'int' declaration specifier
typedef int SOCKET;
The build system is a FreeBSD 11.2-RELEASE.
(In reply to Patrice from comment #0)
Are you using the default options or did you select more; Using poudriere and default port options I didn't get this.
If you selected more options, which ones were they
thanks for your reply. We played with config options, and found out that it fails with the described error only when activating BRO option. We unticking this one, the port builds successfully.
We are not using poudriere but portmaster to compile ports.
Created attachment 197464 [details]
I am not really sure if it is right, but try this.
Comment on attachment 197464 [details]
thank you for your try, but it fails to compile because SOCKET is not defined.
Created attachment 197821 [details]
This should work with PORT_PCAP on or off.
Comment on attachment 197821 [details]
the attached patch works when option BRO is activated, but fails when it is turned off.
Created attachment 197830 [details]
Created attachment 197831 [details]
Tried to patch out all warnings (some tautological comparisons and other). I am not sure if everythings is right. Please check it.
Comment on attachment 197831 [details]
Compiles without BRO option, fails with it.
Compiles fine on my system with port or poudriere.
Please tell me the error message.
Well, we failed to apply the complete patch on previous try. By testing it again, we confirm it compiles correctly now with or without BRO option.
Thank you for your work,
A commit references this bug:
Date: Tue Jan 22 14:57:30 UTC 2019
New revision: 490954
security/barnyard2: fix compile with ooption BRO
Submitted by: email@example.com