|author||Joey Hess||2020-02-20 14:14:40 -0400|
|committer||Joey Hess||2020-02-20 14:14:40 -0400|
Diffstat (limited to 'doc')
1 files changed, 30 insertions, 0 deletions
diff --git a/doc/forum/Bootstrapping_with_Cabal_on_Archlinux_fails/comment_2_ee81823a34396b98cda15282019dcafc._comment b/doc/forum/Bootstrapping_with_Cabal_on_Archlinux_fails/comment_2_ee81823a34396b98cda15282019dcafc._comment
new file mode 100644
@@ -0,0 +1,30 @@
+ subject="""comment 2"""
+Seems odd that the way Arch has installed ghc would
+make `cabal install` fail without additional options being added very time.
+That does not strike me as a good decision if it's the case. I guess that
+the -dynamic should only be set on Arch, since only it has inflicted this
+problem on itself.
+Would appreciate a patch with the ghc 8.8 fixes.
+I would not be surprised if cabal new-build does not provide any good way
+to find out where the executable was put, because after all cabal build
+doesn't either (just it's easier to guess there). Cabal expects a workflow
+where that's followed by cabal install, or cabal run.
+This might be one way: `cabal new-install --symlink-bindir=.`
+But with my older version of cabal, that seems to not actually work,
+indeed I can't get it to install the binaries anywhere. Maybe it does
+work with the newer cabal where new-install is the default.
+Needing to detect whether new-build was used or not is an added
+Best way I've found:
+ find dist-newstyle/ -executable -type f |grep 'propellor$'