Need Help with libcurl build failure on Window 10

I’m trying to build using MSYS2 on Windows 10; but I ran into this problem during the “make dep” stage. I understand the issue and even what the fix should be; since it amounts to applying this patch

What I don’t understand is how to make the solution work in the workflow of the build system. It seems that if I apply the patch and restart “make dep”, the build system overwrites the patched file with the original.

Can someone point me at a resource for how to make something like this work in the MSYS2 build workflow?

See the thread updated msys and rack, now can't build

1 Like

It’s unfortunate that the published build procedure doesn’t work on the most popular OS.

This has been known for a while now but VCV haven’t addressed it. I wonder if they have any plans to improve the situation.

VCV used to use github issues for bug reporting, so you could watch this stuff. I guess now you use this stuff people used to call “e mail” to report bugs. But I have seen on discord that they are at least aware that one can’t build VCV by following the instructions on Windows.

I just reverted my gcc to get around this. Now I just never update anything and I’m good.

Thanks. I missed that in my quick search. However, the upshot is that VCV needs to upgrade their version of curl because the one they are using has security problems. I think I’ll contact support and wait until they do.

Other dependencies are getting long in the tooth. RTMidi is at least a full version behind.

No kidding. Here’s a list of the dependencies that show up in dep/Makefile that are out of date.

jannson 2.12 2.14 openssl 1.1.1 3.4.0 curl 7.79.1 8.11.0 zstd 1.4.5 1.5.6 libarchive 3.4.3 3.7.7 libsamplerate 0.1.9 0.2.2

openssl is a version with a lot of security problems. It’s almost enough to make me stop using Rack.

And that list doesn’t include any of the things they build in tree but haven’t updated.

The only thing the ssl/curl impact is Rack accessing its own servers for updates/checking the plugin DB, so I’m a little less concerned than if it was a service to plugins that would access a wider web.

For my own use, I apply a patch to rtmidi for a bug in it, and also patch Rack’s own rtmidi wrapper to fix a Rack bug (reported a while back, but never fixed).