-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make cold
on Windows: dune error
#5601
Comments
From the logs, you installed some packages on your fresh cygwin install. Was it just autoconf, make, mingw64-x86_64-gcc-g++, mingw64-i686-gcc-g++, and patch, or other ones ? Also you say that you updated your %path, did you run make cold from cygwin or from cmd ? |
/cc @a2line |
Hi. The shell are still open on that machine so I can paste what I did exactly. We already had a batch for building GeneWeb on Windows, I only added autoconf and mingw64-i686-gcc-g++ here, and launched this on a CMD with administrator rights to install Cygwin:
the command
Then I used cygwin console and got what I pasted on first message here. Note that I've just tried with command prompt and it doesn't work well at all:
|
related to #5522 |
I was not able to reproduce. From a fresh Cygwin, I installed the same packages, and launched the same command. And it succeed. |
Ok. I used the installer of Cygwin and saw in the list of packet that mingw64-i686-gcc-g++ was not installed at all (I can't explain why…). I also added mingw64-i686-gcc-core and it's now building. I'll probably retry from scratch to understand better. It doesn't need to add the path to i686 dlls |
Glad to hear! |
Issue originates from ocaml-opam/opam-repository-mingw#10
Hi. I'm glad to try Opam 2.2.0-alpha for Windows because I hope it will simplify the build of Geneweb on that platform. After installing a fresh cygwin64 + upgrading %path, the
make cold
ends with:Full log here https://gist.github.com/a2line/a2b951b9018a402280ac244f461c8bf5
I tried
make cold CONFIGURE_ARGS=--with-private-runtime
for the same results. Any idea?The text was updated successfully, but these errors were encountered: