build fail with ghc-9.0.1

[mimi1vx]

[  242s] [59 of 61] Compiling Language.Fixpoint.Solver ( src/Language/Fixpoint/Solver.hs, dist/build/Language/Fixpoint/Solver.o, dist/build/Language/Fixpoint/Solver.dyn_o )
[  242s] 
[  242s] src/Language/Fixpoint/Solver.hs:193:31: error:
[  242s]     A pragma is not allowed in this position: {-# SCC "sanitize" #-}
[  242s]     |
[  242s] 193 |   let si1   = either die id $ {-# SCC "sanitize" #-} sanitize cfg $!! si0
[  242s]     |                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[  242s] error: Bad exit status from /var/tmp/rpm-tmp.7BJJL5 (%build)
[  242s] 
[  242s] 

[ranjitjhala]

Wow! Are you using it as a plugin or building liquid-fixpoint separately? In the latter case can you let us know how you’re building?

…

On Thu, Mar 11, 2021 at 5:13 AM Ondřej Súkup ***@***.***> wrote: [ 242s] [59 of 61] Compiling Language.Fixpoint.Solver ( src/Language/Fixpoint/Solver.hs, dist/build/Language/Fixpoint/Solver.o, dist/build/Language/Fixpoint/Solver.dyn_o ) [ 242s] [ 242s] src/Language/Fixpoint/Solver.hs:193:31: error: [ 242s] A pragma is not allowed in this position: {-# SCC "sanitize" #-} [ 242s] | [ 242s] 193 | let si1 = either die id $ {-# SCC "sanitize" #-} sanitize cfg $!! si0 [ 242s] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [ 242s] error: Bad exit status from /var/tmp/rpm-tmp.7BJJL5 (%build) [ 242s] [ 242s] — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <https://urldefense.com/v3/__https://github.com/ucsd-progsys/liquid-fixpoint/issues/467__;!!Mih3wA!Ss7SjYM5LWqX6-qAFcJiDHg7iYe9LV60sYHTVmfPkCNwTyC-yY9dLWLuXl3rPmm7$>, or unsubscribe <https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AAMS4OFACE6PTCXF3UVIPELTDC6WHANCNFSM4ZAIFGUA__;!!Mih3wA!Ss7SjYM5LWqX6-qAFcJiDHg7iYe9LV60sYHTVmfPkCNwTyC-yY9dLWLuXhI_I72f$> .

[mimi1vx]

building separately -> full log https://build.opensuse.org/package/live_build_log/devel:languages:haskell:ghc-9.0.x/ghc-liquid-fixpoint/openSUSE_Tumbleweed/x86_64

[mimi1vx]

@ranjitjhala see https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0176-scc-parsing.rst

[ranjitjhala]

Oops thanks for bumping this I will fix it today!

…

On Tue, Mar 23, 2021 at 7:34 AM Ondřej Súkup ***@***.***> wrote: @ranjitjhala <https://urldefense.com/v3/__https://github.com/ranjitjhala__;!!Mih3wA!Qk1v59oaIx_P4BqY8Xk4Uvedp0E59WsJgAieQaeqwJJ60G4etEYD0WOSIkTTAOqZ$> see https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0176-scc-parsing.rst <https://urldefense.com/v3/__https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0176-scc-parsing.rst__;!!Mih3wA!Qk1v59oaIx_P4BqY8Xk4Uvedp0E59WsJgAieQaeqwJJ60G4etEYD0WOSIndEeS2n$> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://urldefense.com/v3/__https://github.com/ucsd-progsys/liquid-fixpoint/issues/467*issuecomment-804952836__;Iw!!Mih3wA!Qk1v59oaIx_P4BqY8Xk4Uvedp0E59WsJgAieQaeqwJJ60G4etEYD0WOSIjiMpkMm$>, or unsubscribe <https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AAMS4OC4ECCFP5NF6N6QTMTTFCRF7ANCNFSM4ZAIFGUA__;!!Mih3wA!Qk1v59oaIx_P4BqY8Xk4Uvedp0E59WsJgAieQaeqwJJ60G4etEYD0WOSIp833z1V$> .

[ranjitjhala]

This _should_ be fixed in the latest `develop` branch -- can you let me know? Thanks!

…

On Tue, Mar 23, 2021 at 7:35 AM Ranjit Jhala ***@***.***> wrote: Oops thanks for bumping this I will fix it today! On Tue, Mar 23, 2021 at 7:34 AM Ondřej Súkup ***@***.***> wrote: > @ranjitjhala > <https://urldefense.com/v3/__https://github.com/ranjitjhala__;!!Mih3wA!Qk1v59oaIx_P4BqY8Xk4Uvedp0E59WsJgAieQaeqwJJ60G4etEYD0WOSIkTTAOqZ$> > see > https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0176-scc-parsing.rst > <https://urldefense.com/v3/__https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0176-scc-parsing.rst__;!!Mih3wA!Qk1v59oaIx_P4BqY8Xk4Uvedp0E59WsJgAieQaeqwJJ60G4etEYD0WOSIndEeS2n$> > > — > You are receiving this because you were mentioned. > > > Reply to this email directly, view it on GitHub > <https://urldefense.com/v3/__https://github.com/ucsd-progsys/liquid-fixpoint/issues/467*issuecomment-804952836__;Iw!!Mih3wA!Qk1v59oaIx_P4BqY8Xk4Uvedp0E59WsJgAieQaeqwJJ60G4etEYD0WOSIjiMpkMm$>, > or unsubscribe > <https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AAMS4OC4ECCFP5NF6N6QTMTTFCRF7ANCNFSM4ZAIFGUA__;!!Mih3wA!Qk1v59oaIx_P4BqY8Xk4Uvedp0E59WsJgAieQaeqwJJ60G4etEYD0WOSIp833z1V$> > . >

[mimi1vx]

sorry for late reply, develop branch build on my system fine , please release new version on hackage :D

[curiousleo]

Since May 9th, there have been two Hackage releases of liquid-fixpoint:

• https://hackage.haskell.org/package/liquid-fixpoint-8.10.7 on 2021-11-03
• https://hackage.haskell.org/package/liquid-fixpoint-0.8.10.7 on 2021-11-05

So it looks like the fixes have been released and this issue can be closed.