----- Original Message ----- > From: "Paul Boca" <pb...@cloudbasesolutions.com> > To: "Lance Richardson" <lrich...@redhat.com> > Cc: dev@openvswitch.org, "Alin Serdean" <aserd...@cloudbasesolutions.com>, > "Ben Pfaff" <b...@ovn.org> > Sent: Friday, June 10, 2016 4:16:15 AM > Subject: RE: [ovs-dev] [PATCH] tests: fix issue in use of > OVS_APP_EXIT_AND_WAIT > > Hi Lance! > > You need pthread from here: > ftp://sourceware.org/pub/pthreads-win32/pthreads-w32-2-9-1-release.zip > *Extract "pthreads-w32-2-9-1-release.zip\Pre-built.2" to "C:/pthread" and > on configure use `--with-pthread="C:/pthread"` > > For `--with-openssl` you will need openssl installed. > > That should do it. If not please post your linker errors. > > Regards, > Paul > Hi Paul,
I had made it past that point. The message I was seeing was in a popup, something like "entry point xxxx not found in kernel.dll", where "xxxx" appeared to be a time-related function name. Some googling found that this symbol (sorry I don't recall the exact name) was only available in win8 and newer. So I bit the bullet and upgraded to win10 late yesterday, now the tests execute but there are display brightness issues making it difficult the results. (At least I can still boot into Linux on that machine :-)) It would probably help if someone could take a look at my comments to Alin's remarks in: http://openvswitch.org/pipermail/dev/2016-June/072338.html As I mentioned there, I don't see how adding parameters to suppress stderr/stdout output for an AT_CHECK invocation can possibly affect whether a command that is executed after the AT_CHECK has passed winds up in the ovsdb-server log. Thanks, Lance _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
