You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EDIT: I am pretty sure that this is a regession between Cabal-3.10.1.0 and Cabal-3.10.3.0 because my example builds if I force Stack to build using GHC 9.6.5 but with Cabal-3.10.1.0, using:
A difference between the two builds above is that, in the linking step, Cabal calls GHC 9.6.5 with additional arguments not present in the GHC 9.6.4 example:
I don't think so - looks to me like a regression introduced into Cabal, not GHC. EDIT: unless you mean something to warn the GHC developers that there is this problem with that version of Cabal?
I have a simple package
foo
with Cabal file:With GHC 9.6.4/
Cabal-3.10.1.0
it builds fine:With GHC 9.6.5/
Cabal-3.10.3.0
the build fails in the linker:Is this a regression introduced in
Cabal-3.10.3.0
?I wondered if it was related to:The ghc-options are not passed to the linker #9589(EDIT: I now think that's unrelated)EDIT: I am pretty sure that this is a regession between
Cabal-3.10.1.0
andCabal-3.10.3.0
because my example builds if I force Stack to build using GHC 9.6.5 but withCabal-3.10.1.0
, using:EDIT2: Using the same method, it appears to me to be a regression introduced between
Cabal-3.10.2.1
andCabal-3.10.3.0
.(EDIT 3: The good news is this is not a problem for GHC 9.10.0.20240426/Cabal-3.12.0.0.)
The text was updated successfully, but these errors were encountered: