Home → Problems →

Cannot find path 'C:\OpenSSL-Win64' because it does not exist.

• Edit

Ilya Maximets

12 Sep, 2025 12:28 AM

Starting today our builds started to fail unable to link with OpenSSL using VS 2019 image.
We install our own version deleting the C:\OpenSSL-Win64 first, but somehow this folder doesn't exist anymore. Moreover, after we install our own version of OpenSSL, files are also not there and so the build fails. See an example here: https://ci.appveyor.com/project/igsilya/ovs/build/job/iobwbmss53u7bk4e?fullLog=true#L55

1. Support Staff 1 Posted by Owen McDonnell on 12 Sep, 2025 05:56 AM

   

   Sorry for the inconvenience. We're in the middle of updating Visual Studio 2019 and 2022 images at the moment. The issue you outline has been identified and is currently being fixed. You can use Previous Visual Studio 2019 image in the meantime, but a new image should be available within the next 24-48 hours.

   • Edit

2. Owen McDonnell closed this discussion on 23 Sep, 2025 02:15 PM.

3. Ilya Maximets re-opened this discussion on 29 Sep, 2025 03:56 PM

4. 2 Posted by Ilya Maximets on 29 Sep, 2025 03:56 PM

   

   FWIW, this one is still a problem. It got fixed for a few days after I opened this thread, but then returned. While we can work around the missing OpenSSL installation, there seems to be also some issue with the compiler environment, our ./configure script is unable to find the standard stdio.h and strings.h, while it works just fine on the Previous variant of the image:

   > C:\msys64\msys2_shell.cmd -here -defterm -no-start -use-full-path -c ".ci/windows-build.sh $env:CONFIGURATION 2>&1"
   > + CONFIGURATION=Release
   > + ./boot.sh
   > + ./configure CC=build-aux/cccl 'LD=/c/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/HostX64/x64/link' 'LIBS=-lws2_32 -lShlwapi -liphlpapi -lwbemuuid -lole32 -loleaut32' --prefix=C:/openvswitch/usr --localstatedir=C:/openvswitch/var --sysconfdir=C:/openvswitch/etc --with-pthread=c:/PTHREADS-BUILT/ --enable-ssl --with-openssl=C:/OpenSSL-Win64 --with-vstudiotarget=Release
   > ...
   > checking absolute name of <stdio.h>... ""
   > checking absolute name of <string.h>... ""

   I'm not sure what it happening there. On a good Previous image it looks like this:

   > checking absolute name of <stdio.h>... "C:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.22000.0\\ucrt\\stdio.h"
   > checking absolute name of <string.h>... "C:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.22000.0\\ucrt\\string.h"

   • Edit

5. Support Staff 3 Posted by Owen McDonnell on 29 Sep, 2025 05:17 PM

   

   The only difference i see between Previous Visual Studio 2019 and Visual Studio 2019 is an updated default OpenSSL version (1.1.1w).
   But it sounds like you weren't using the deprecated OpenSSL anyways, so I can't imagine why this would be a problem for you build.

   • Edit

6. 4 Posted by Tobias Brunner on 02 Oct, 2025 07:55 AM

   

   We have the same issue with the Visual Studio 2019 image where the path to OpenSSL 1.1.1 (C:\OpenSSL-v111-Win64\bin) isn't found anymore.

   • Edit

7. Support Staff 5 Posted by Owen McDonnell on 03 Oct, 2025 05:27 PM

   

   Sorry, as OpenSSL 1.0.2 was removed 1.1.1 became default and it now found in C:\OpenSSL-Win32\bin/C:\OpenSSL-Win64\bin

   • Edit

8. 6 Posted by Tobias Brunner on 06 Oct, 2025 08:39 AM

   

   Oh, I see. Thanks for the info.

   • Edit

9. Owen McDonnell closed this discussion on 08 Oct, 2025 03:59 AM.