Hi Alin,
I see that the AppVeyor builds are failing due to some issue with the
signtool options (and some warnings that might need to be addressed).
Can you have a look? Here is a sample output:
C:\Program Files (x86)\Windows
Kits\10\bin\10.0.22000.0\x86\signtool.exe sign /ph /sha1
"25C1E579759C692A3BAE65AA567BE4A4C443CFD9"
libtool: compile: build-aux/cccl -DHAVE_CONFIG_H -I. -I ./include/windows -I
./datapath-windows/include -Ic:/PTHREADS-BUILT//include -O2 -I ./include -I
./include -I ./lib -I ./lib -IC:/OpenSSL-Win64/include -Wstrict-prototypes
-Wall -Wextra -Wno-sign-compare -Wpointer-arith -Wformat -Wformat-security
-Wswitch-enum -Wunused-parameter -Wbad-function-cast -Wcast-align
-Wstrict-prototypes -Wold-style-definition -Wmissing-prototypes
-Wmissing-field-initializers -Wthread-safety -fno-strict-aliasing -Wswitch-bool
-Wlogical-not-parentheses -Wsizeof-array-argument -Wbool-compare
-Wshift-negative-value -Wduplicated-cond -Qunused-arguments -Wshadow
-Wmultistatement-macros -Wcast-align=strict -Wno-null-pointer-arithmetic
-Warray-bounds-pointer-arithmetic -g -c lib/conntrack-other.c
3>SIGNTASK : SignTool error : No file digest algorithm specified. Please
specify the digest algorithm with the /fd flag. Using /fd SHA256 is recommended
and more secure than SHA1. Calling signtool with /fd sha1 is equivalent to the
previous behavior. In order to select the hash algorithm used in the signing
certificate's signature, use the /fd certHash option.
[c:\openvswitch_compile\datapath-windows\ovsext\ovsext.vcxproj]
You can see an example failure at:
https://ci.appveyor.com/project/blp/ovs/builds/41038081/job/h8ay65w6d638vs2v
Thanks,
Aaron
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
