Opened 4 years ago
Closed 8 months ago
#61220 closed defect (fixed)
ghc @8.10.1: error renaming ".../testsuite": no such file or directory
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | essandess (Steve Smith) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.3 |
Keywords: | Cc: | ||
Port: | ghc |
Description
Building ghc failed for reasons specific to my system. I fixed the problem and tried continuing the ghc build, but then it failed for a different reason:
Error: Failed to build ghc: error renaming "/opt/local/var/macports/build/_Users_rschmidt_macports_macports-ports-ryandesign-fork_lang_ghc/ghc/work/ghc-8.10.1/testsuite": no such file or directory
This is happening because the ghc portfile contains this block:
pre-build { # test: move extracted testsuite directory to src xinstall -m 0755 -d ${srcpath}/${distname} move ${test.dir} ${srcpath}/${distname}/testsuite test.dir ${srcpath}/${distname}/testsuite }
Logically, this block can only succeed the first time it is executed and will fail if the build phase is interrupted for any reason and later resumed, which is something that the port should allow to happen.
Can this block be changed to a post-extract block? That way, assuming it succeeds, the extract phase will be marked completed and the block won't be run again.
There is no use to setting test.dir in this block, since this block is not for the test phase. There is a later test.dir setting in the portfile anyway; hopefully that is the correct one.
Change History (4)
comment:1 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Summary: | ghc: error renaming ".../testsuite": no such file or directory → ghc @8.10.1: error renaming ".../testsuite": no such file or directory |
---|
comment:2 Changed 4 years ago by essandess (Steve Smith)
comment:3 Changed 4 years ago by essandess (Steve Smith)
comment:4 Changed 8 months ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Replying to ryandesign:
In fact no, the test.dir set globally is not correct, which is what causes #61221.