cabal new-build state detection/write ordering issues
Open
cabal-install: v2-build system
type: bug
- Dominant language
- Haskell
- Stars
- 1.7k
- Forks
- 750
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 28
Description
When killing cabal new-build it seems it can get in a state where it belies a file is built, but not all required versions of it are written to disk. For example:
```
Building library for reflex-0.5..
gcc: error: /home/davean/projects/reflex-test/dist-newstyle/build/x86_64-linux/ghc-8.4.2/reflex-0.5/build/Data/Map/Misc.dyn_o: No such file or directory
`gcc' failed in phase `Linker'. (Exit code: 1)
```
It seems what it uses to detect a file being built should be the last component written.
Contributor guide
Assessment
This issue has not been assessed yet.