jay
commented
8 years ago the /dev/null thing looks like it happens because although /dev/null is fine in mingw shell you're using the windows api so it needs NUL instead, probably something like this:
diff --git a/tests/api.c b/tests/api.c
index 36189ef..11d9c1b 100644
--- a/tests/api.c
+++ b/tests/api.c
@@ -58,8 +58,12 @@ static const char* passed = "passed";
static const char* failed = "failed";
#if !defined(NO_FILESYSTEM) && !defined(NO_CERTS)
+#ifdef _WIN32
+static const char* bogusFile = "NUL";
+#else
static const char* bogusFile = "/dev/null";
#endif
+#endif
/*----------------------------------------------------------------------------*
| Setupeven with that fixed unit still fails though,
starting unit tests...
Begin API Tests
wolfSSL_Init(): passed
SUCCESS4
wolfSSL error: tcp connect failed
FAIL: tests/unit.test.exe
dgarske
I had a few problems compiling wolfSSL in mingw32, most warnings as errors that were caused by -Werror. Rather than -Wno-error which would be fine I guess I went through each of them.
The m4/visibility.m4 detection incorrectly detects mingw gcc as supporting
__visibility__likely because there's no function definition to actually test the visibility. If I add one then the visibility test will properly fail, for example:However I'm not sure whether it would cause other warnings that could make the visibility test fail incorrectly on other platforms. For now I can workaround by passing
-Wno-attributestoC_EXTRA_FLAGSbefore configure.Related cyassl/ctaocrypt/visibility.h does not define dllexport or dllimport unless msvc.
I am using configure switch
--enable-alpnbut it requires a safe strtok as defined in wolfcrypt/types.h which mingw does not have. As a workaround I used a public domain version found at http://stackoverflow.com/a/12979321.Both src/asn.c and src/dsa.c have unsigned / signed comparisons. As a workaround I casted both sizeofs to
(int).Unused variable warnings on assert. If a variable is only used for assert there is a warning, like this
The two or three of these I saw looked superfluous so my workaround was passing
-Wno-unused-but-set-variabletoC_EXTRA_FLAGSbefore configure.I had problems running the tests as well:
The testsuite fail wasn't reproducible. In the background for an hour I've run
while true; do testsuite/testsuite.test.exe 2>&1 | grep error; donebut I haven't seen it again. (Edit: after I posted this I sawerror = -308, error state on socketbut that's not the same as record layer length error.)The other two fails are reproducible. in unit.test:
bogusFile is
/dev/nulland it fails because it's able to open it? I didn't look into that one too close.in resume.test port number is 0 and I guess that isn't allowed for mingw
another thing is the ping commands you're using
ping -cbut that's not universal on windows it should be ping -n. In cygwin you may need to test which is appropriate. The ping package that comes with cygwin doesn't use either and doesn't work properly so you could probably get away with something like -n for windows even if cygwin and -c elsewhere, unless someone on windows built ping manually.