Closed Totoro83 closed 4 years ago
Uh, really weird, could you tried, just in case, to delete C:\sr\snapshots\7dcfb02b
directory to make stack regenerate it?
I tried to remove all of stack, removing all C:\sr entirely, and reinstall it. Nothing changed
Hi again, i am afraid i am not able to reproduce in my windows 10 or in azure ci
To help debug the issue we can force a fresh build of unix-time-0.4.7
:
C:\sr\snapshots
to make stack use a new one (but to let us recover it after the test)stack build unix-time-0.4.7 --stack-yaml .\stack-8.6.5.yaml -v
inside the hie project root dir
stack build hoogle --stack-yaml .\stack-8.6.5.yaml -v
to check if the error is reproduced if the first build finished succesfullyFrom the unix-time build log we can see in the configure step:
2020-04-25 15:28:22.781802: [info] unix-time > checking for timegm... no
2020-04-25 15:28:23.760802: [info] unix-time > checking for _mkgmtime... yes
So the package should not use a preexisting timegm
(it seems it does nos exist in win envs).
Ok, I tried to build unix-time like you suggested, and it worked, so I tried to rebuild hie and it worked. I don't really know why this worked, but I suppose it could be considered closed.
I'm trying to install hie with stack 2.1.3, powershell 7 and windows 10, but I have a problem building the hoogle dependence:
I'm using git commit tagged as 1.3 (but I tried the master one too) and win32 long paths are enabled.