q8fuel
(q8fuel)
September 15, 2024, 6:51am
1
hi,
i’m trying to build Rack on a Windows 10 machine (not so “new”).
follow the usual steps on the manual, but at some points, it always got to me this:
l.o crypto/x509v3/v3err.o crypto/x86_64cpuid.o
${LDCMD:-gcc} -m64 -g -O3 -fPIC -march=nehalem -g -O3 -fPIC -march=nehalem -L. -g -O3 -fPIC -march=nehalem \
-o test/rsa_complex.exe test/rsa_complex.o \
-lws2_32 -lgdi32 -lcrypt32
C:\msys64\mingw64\bin\ar.exe: creating libcrypto.a
C:\msys64\mingw64\bin\ar.exe: crypto/cast/c_cfb64.o: No such file or directory
make[3]: *** [Makefile:760: libcrypto.a] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/c/repos/Rack/dep/openssl-1.1.1k'
make[2]: *** [Makefile:188: all] Error 2
make[2]: Leaving directory '/c/repos/Rack/dep/openssl-1.1.1k'
make[1]: *** [Makefile:128: lib/libssl.a] Error 2
make[1]: Leaving directory '/c/repos/Rack/dep'
make: *** [Makefile:112: dep] Error 2
i really don’t get why, never had problem with building. Tried to clean the whole suite, reinstall, and such. same.
did you ever catch the same problem? how would I fix it? thanks
I think it’s a known issue with updated msys2 tools.
See these posts for a fix.
This I wrote in the discord thingie; but I think this is a better place to keep it: easier to reference and find.
"One so-so comedy sequel later… I managed to build Rack with openssl 3.3.1 and curl 8.9.1!
Both dependencies spew warnings about the stuff rack disables; but build fine.
Openssl “installs” to lib64, so files need to be moved to lib. This can be done via the makefile: either moving them; adding the directory via LDFLAGS, or maybe some openssl build option; but I didn’t check; I mov…
Addendum to the above:
I made a repo with a branch with the fixes metioned:
Linux and Apple compatibility is not guaranteed or tested, and support for my fixes is… essentially non-existent: they work for me and let me build Rack so… now you know.
no need to write support@vcvrack, they are aware.
2 Likes
q8fuel
(q8fuel)
September 15, 2024, 6:52pm
3
sorry, but didnt get a solution from your post (wont build official release from a fork; nothing personal, but its out of my scope of interess).
should I use a different msys version? which one?
Squinky
September 15, 2024, 9:40pm
4
yeah, the official version does not build with the current tools. If you want you can wait for VCV for fix it, which can sometimes take them a very long time. Or you can find an older post from @Bloodbat that tells how to roll back the version of gcc that’s in msys2.
1 Like
q8fuel
(q8fuel)
September 16, 2024, 6:40am
5
i see. so basically I need to:
download latest msys (current msys2-x86_64-20240727.exe from here )
setup packages with pacman using Rack develop tutorial, excluding mingw-w64-x86_64-gcc
install manually mingw-w64-x86_64-gcc-13.2.0-6-any.pkg.tar.zst and mingw-w64-x86_64-gcc-libs-13.2.0-6-any.pkg.tar.zst, as specified here
correct?
q8fuel
(q8fuel)
September 16, 2024, 6:48pm
7
got it, and compiled! thanks for your huge helps
2 Likes