Everything seems to work fine, but when I then try to download and compile the dependencies (make dep), I invariably get an error message:
Connecting to github.com (github.com)|140.82.121.4|:443… connected.ERROR: The certificate of ‘github.com’ is not trusted.ERROR: The certificate of ‘github.com’ doesn’t have a known issuer.make[1]: *** [Makefile:89: glew-2.1.0] Error 5make: *** [Makefile:109: dep] Error 2
Does anyone have any suggestions that would help me, as a beginner, solve this problem?
It might just be an ephemeral error with GitHub that will go away in a few hours.
As with any problem on a computer, you should mention what operating system and version you’re on. If you’re on a Mac, mention if it’s x86 or Apple Silicon. If you didn’t install git as part of setting up VCV Rack build, you might check if your git is up to date.
In my experience, some antivirus programs inject their own certificate midway and can lead to that error, you could try disabling the antivirus only while those wget parts finish (Kaskpersky, for example, did that).
It can also happen if you have a very old browser version, or very old (unsupported) OS version, or very old version of tools like MSYS2. Because then their root certificate stores won’t be updated, which means that when the service (e.g. github) changes their certificate it won’t be recoqnized by your browser/computer/tool and then you get this error/warning.
This is unlikely to be the problem, but another possible cause of certificate errors is having the wrong date set (and I mean very wrong, not just a couple of minutes).
Here I am again, with a rather negative assessment. I reinstalled the latest version of MSYS2, tried cloning Rack again, first closing my antivirus. I tried adding --no-check-certificate to wget.
I also checked the clock for an automatic update.
The error persists. It’s quite frustrating and hopeless…
Can you please write in detail the exact tool you are using to do the clone, and if it’s on the command line, the exact commands you executed to get the source and build it? Thanks.
It sounds like the clone and git-submodule commands actually work fine, but it’s the make dep stage that fails, when it comes to building glew?
First of all, thank you for your consideration of my problem.
But if I made any mistakes, please be kind: I’m just a beginner!
As suggested by Paul Dempsey in an earlier post, rather than using the SDK, I chose to clone Rack and compile it from source.
And this is where the trouble begins, with the certificate error messages. I tried modifying the dep Makefile with:
wget --no-check-certificate -c “https://…”
Then
make clean and again: make dep
I followed the procedure scrupulously.
But the “make dep” command still sends me the same notification:
Resolving github.com (github.com)… 140.82.121.3
Connecting to github.com (github.com)|140.82.121.3|:443… connected.
ERROR: The certificate of ‘github.com’ is not trusted.
ERROR: The certificate of ‘github.com’ doesn’t have a known issuer.
make[1]: *** [Makefile:89: glew-2.2.0] Error 5
make[1]: Leaving directory ‘/c/msys64/home/chior/Rack/dep’
make: *** [Makefile:112: dep] Error 2
If you have followed the above list to the letter, then if you have any anti-virus/security-software installed, apart from the builtin Windows Defender, disable/uninstall it completely and try again.
Thank you, thank you so much for your help!
I deleted Rack, completely uninstalled my antivirus, and then restarted the process from the beginning.
And… hallelujah!!! It finally works: I have “my” VCV Rack clone on the PC.
In the end, this sneaky antivirus thing almost made us lose our minds.
I think this is something that will now have to be written in bold and underlined.
And now, it’s my turn to get my hands dirty.
What a joy!
Thanks again.
(But don’t think I’ll stop asking for your help… On the contrary !)
On Windows, there is no need for a 3rd party antivirus. Windows Defender does the job just fine. (Others will just take an opportunity here for more gratuitous Windows hate, which I’ve heard enough of for several lifetimes, but it’s a fact of life, so sigh).
Absolutely, I took @LarsBjerregaard s advice years ago and uninstalled the 3rd party Antivirus and I have never regretted it. A bit nervous at first, but everything installs easier now and I don’t have have pointless scans running in the background. So thank you!
Happy you succeed.