-
Notifications
You must be signed in to change notification settings - Fork 37
Building on windows is broken. #697
Comments
Hmm. Odd. That appveyor build went fine for last PR that got merged: #691 Maybe that was before some GHC patch broke everything (again) ? |
For the record, the first error message comes from my work on #564 (which resulted in ghc commit ghc/ghc@5d76846). It'd be nice to get the output of the same command with For the second one, it looks like |
Trace output
|
That's an odd one. No more details? Did you run |
@alpmestan Do you mean |
--verbose and --trace do the same thing no? Judging from hadrian's |
@AndreasPK In the first case ( I'll try to reproduce the failure with @alpmestan Ah, indeed, I didn't know about |
I've run configure manually above Some more dumps from build.sh/build.bat (are both supported on windows?)
I have no idea where the C:\test\pyn.stack-work\install... path comes from tbh. |
Deleting the " C:\test\pyn.." path made the build.sh script run through. Still not sure why that got picked up to begin with though. It's definitely not in PATH. |
@AndreasPK No. On Windows we only support (Sorry, I can't be more helpful. This week is very busy.) |
I reproduced the Happy-related failure on my machine:
Just like in @AndreasPK's case, the path |
The problem seems to be not with Hadrian, but rather with the Happy installation. If I reinstall Happy, the build continues correctly. Here is I think what happened in @AndreasPK's case: he installed Happy before trying Hadrian, and during the installation Happy put its In my case, Happy was installed in the Hadrian's I don't really know whether we can do anything about this in Hadrian. It seems to me that the |
@AndreasPK Do you need any further help with using Hadrian on Windows? |
For the moment I went back to make :/ Currently build.bat still doesn't work (see log above) only build.sh does after "fixing" the happy issue. So there is no officially supported way to run the build. I can work around that by using build.sh but given that it's not supported I'm not keen on going that way. I wonder why build.sh is not supported if we require an msys installation anyway. Having differing default workflows for windows/linux does seem like it will only lead to issues down the road. There is also #696 which for me is on it's own enough of a pain point to keep using make for now. |
@AndreasPK I couldn't reproduce your
We do not require an MSYS installation (see the AppVeyor build script, for example). Hadrian can be used on Windows without installing MSYS manually -- this is handled by Stack. Have you tried |
I see. I must have misinterpreted something then and it's good to know! I did try it from powershell and from within an msys environment though.
I have not. I've started a build now but I can already say it's affected by #696 as I forgot to pass -j initially. edit: After running clean the cabal.bat version works. |
@AndreasPK Thanks for giving the Cabal script a try! I agree that #696 is annoying. As a workaround I sometimes terminate Hadrian in the Task manager, which is awkward, but seems to work. The |
Yes it's what I did. But at that point I have to ask myself why not just stay on make for now.
|
So I got the same build.bat error with a clean check out. A question about the shell requirements:
From the quickstart page:
Is this just plain wrong or are users supposed to do something like stack exec mintty and run hadrian from there? (Although not sure if this is the right place to discuss this). |
Do you get the same error if you run the command in question
Yes, I think the QuickStart page is wrong in this respect. Let me CC @alpmestan who wrote it -- is there any reason for requiring the MinGW shell when developing GHC on Windows? Even with Make I think we can now build GHC in other Windows shells.
Don't worry, it's perfectly fine to discuss any Hadrian-related questions here. |
I simply borrowed this bit from the guide for the make build system. Please feel free to edit the page and make all the necessary corrections. Since I'm not a Windows user, any Windows-specific details will be best taken care of by either/both of you. :-) |
@alpmestan Thanks! :) Yes, I'll do some edits for Windows-specific bits. |
I believe this has been fixed. |
Both build.sh and build.bat are broken for seemingly different reasons.
The text was updated successfully, but these errors were encountered: