The Setup.hs file seems to assume that a configure file is present in the package.
It uses main = defaultMainWithHooks autoconfUserHooks which is not consistent with the build-type: Simple option of the Win32.cabal file (according to cabal's documentation).
Looking at the appveyor.yml file, it seems that this configure file is present in some contexts, but I do not know which ones.
And because the cabal build-type is Simple, I wonder if this file may be optional, in which case the Setup.hs file should maybe use main = defaultMain by default.
This would make it possible to run runghc Setup.hs configure (which is what we usually do in the rules_haskell ruleset for Bazel).
Current Behavior
Trying to configure the package with runghc Setup.hs configure fails with the following error.
Setup.hs: configure script not found.
Steps to Reproduce (for bugs)
- git clone https://github.com/haskell/win32.git
- cd win32
- runghc Setup.hs configure
Your Environment
- Win32: 2.13.2.0
- runghc: 8.10.7
- Os: NixOS
Github action failure
Here is also an example of this failure in a github action with the following environment:
- Win32: 2.6.1.0
- runghc: 8.10.4
- Os: windows-latest github image.
The
Setup.hsfile seems to assume that aconfigurefile is present in the package.It uses
main = defaultMainWithHooks autoconfUserHookswhich is not consistent with thebuild-type: Simpleoption of theWin32.cabalfile (according to cabal's documentation).Looking at the appveyor.yml file, it seems that this
configurefile is present in some contexts, but I do not know which ones.And because the cabal
build-typeisSimple, I wonder if this file may be optional, in which case theSetup.hsfile should maybe usemain = defaultMainby default.This would make it possible to run
runghc Setup.hs configure(which is what we usually do in therules_haskellruleset for Bazel).Current Behavior
Trying to configure the package with
runghc Setup.hs configurefails with the following error.Steps to Reproduce (for bugs)
Your Environment
Github action failure
Here is also an example of this failure in a github action with the following environment: