Skip to content

Unbreak the build on AppVeyor. #3184

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

Merged
merged 1 commit into from
Feb 24, 2016
Merged

Conversation

23Skidoo
Copy link
Member

Take 2.

@grayjay
Copy link
Collaborator

grayjay commented Feb 24, 2016

@23Skidoo Thanks for uploading the binary. I'm trying to update my previous branch that downloaded GHC and cabal separately: https://github.com/grayjay/cabal/tree/appveyor-newer-ghc-and-cabal

@23Skidoo
Copy link
Member Author

Apparently when you run 7z x cabal.tar.gz it unpacks only the cabal.tar file. Uploaded a zip archive instead.

@grayjay
Copy link
Collaborator

grayjay commented Feb 24, 2016

Now it's failing to download the packages: https://ci.appveyor.com/project/grayjay/cabal/build/1.0.73

@23Skidoo 23Skidoo force-pushed the appveyor-fix branch 4 times, most recently from 181769b to 1cf4a3e Compare February 24, 2016 01:02
@23Skidoo
Copy link
Member Author

@grayjay Maybe the problem is that AppVeyor requires a 64-bit binary? The one I uploaded is 32-bit, but the one that comes with Haskell Platform is 64-bit (since it's from HaskellPlatform-2014.2.0.0-x86_64-setup.exe).

@23Skidoo
Copy link
Member Author

Something funky is going on:

ansi-terminal-0.6.2.3 failed while downloading the package. The exception was:
DeleteFile
"C:\\Users\\appveyor\\AppData\\Roaming\\cabal\\packages\\hackage.haskell.org\\ansi-terminal\\0.6.2.3\\curl-headers2812.txt":
permission denied (The process cannot access the file because it is being used
by another process.)

@grayjay
Copy link
Collaborator

grayjay commented Feb 24, 2016

I don't know. I looked back at the other builds that I tried, and I think that all of the cabal binaries that failed to download the index were 32-bit.

@23Skidoo
Copy link
Member Author

OK, I'll build a 64-bit binary then.

@23Skidoo
Copy link
Member Author

The 64-bit binary seems to be able to download packages. Yay!

@grayjay
Copy link
Collaborator

grayjay commented Feb 24, 2016

Great!

@23Skidoo
Copy link
Member Author

So now it fails when trying to configure network:

cabal: Entering directory 'C:\Users\appveyor\AppData\Local\Temp\1\cabal-tmp-2404\network-2.6.2.1'
Configuring network-2.6.2.1...
configure: WARNING: unrecognized options: --with-compiler
checking build system type... x86_64-pc-msys
checking host system type... x86_64-pc-msys
checking for gcc... C:\Program Files\Haskell Platform\2014.2.0.0\mingw\bin\gcc.exe
checking whether the C compiler works... no
configure: error: in `/tmp/cabal-tmp-2404/network-2.6.2.1':
configure: error: C compiler cannot create executables
See `config.log' for more details
cabal: Leaving directory 'C:\Users\appveyor\AppData\Local\Temp\1\cabal-tmp-2404\network-2.6.2.1'
Failed to install network-2.6.2.1

@grayjay
Copy link
Collaborator

grayjay commented Feb 24, 2016

network works with GHC 7.10.3: https://ci.appveyor.com/project/grayjay/cabal

@23Skidoo
Copy link
Member Author

Thanks, changed the script to use GHC 7.10.3 from Chocolatey.

@23Skidoo
Copy link
Member Author

And it finally passed!

23Skidoo added a commit that referenced this pull request Feb 24, 2016
Unbreak the build on AppVeyor.
@23Skidoo 23Skidoo merged commit 7f59397 into haskell:master Feb 24, 2016
@23Skidoo 23Skidoo deleted the appveyor-fix branch February 24, 2016 03:40
@grayjay
Copy link
Collaborator

grayjay commented Feb 24, 2016

I can reproduce the network configure error locally with cabal-install-1.24.0.0, but not cabal-install-1.22.6.0. I think it can't handle the spaces in the path to gcc.

@23Skidoo
Copy link
Member Author

That's #1634. So it's still broken? Maybe we need to add a workaround.

@23Skidoo
Copy link
Member Author

Filed an issue: #3185.

@grayjay
Copy link
Collaborator

grayjay commented Feb 24, 2016

Thanks. It looks like 1.22 was able to configure network because it used --with-gcc instead of CC. The configure script ignored --with-gcc and found gcc on the path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants