-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build Error with gtk-0.13.0.0 #39
Comments
Thank you for the report. Somebody needs to fix TS, to make it compatible with gtk-0.13.0.0. For now, as a workaround, please set "gtk >= 0.12.1 && < 0.13" in threadscope.cabal. |
thanks it works |
Thanks but where is the threadscope.cabal file I need to update? I am on a Mac running 10.9 with ghc 7.8.3 (latest Haskell platform). |
You need to clone (or download) the source for Then run the following in the ThreadScope folder: cabal sandbox init
cabal build
cabal install --user |
When TS is updated, it would be wise to restrict the versions for everything that isn't restricted already according to PVP (just restrict the API-breaking part). P.S. Is this likely to be fixed soon? is there anyone assigned yet? |
Yes, it would be nice to see this fixed On Tue, Sep 16, 2014 at 3:27 PM, MasterMastic notifications@github.com
|
I've updated TS to gtk-0.13.0.0. Please test. If no problems emerge and if the maintainers don't veto, I will make a new release. Please, feel free to submit pull requests re package versioning and any others that you'd like to include in the release. The second part of the fix is hacky, because the code needs to work with gtk < 0.13, too. The bug gtk2hs/gtk2hs#46 doesn't help either. If this gtk2hs bug bites you, manually install new versions of the required packages (e.g., text), or stick to gtk < 0.13. I've defaulted to String, where possible. This is usually less efficient, but for now, compatibility with the other parts of the TS codebase was the more important concern. |
It's building & working perfectly for me 👍. |
@MasterMastic: thank you for the report. Could you specify which version of GHC you have and which version of gtk is used for the compilation (if you run cabal configure -v2, it should mention the version)? |
Sure: And other information that may be relevant: |
Thank you! Anybody with GHC < 7.8? |
It compiles for me successfully with GHC 7.6.3 and gtk-0.13 (no Haskell Platform). But I get segfaults with GHC 7.4.2 (gkt-0.12 was picked by cabal, that wasn't a clean package DB slate and I had some extra GHC patches, so I'm not sure what's going on). Could somebody perhaps verify? Dependencies of the gtk package were fixed upstream some time after we tested with gtk-0.13 above, so in theory TS with gtk-0.13 should work just fine now, regardless of the package DB state. Edit: Testing with gtk-0.12 and any other GHC may do (7.4 is very old, after all). Edit2: Clarified my very unclear earlier description. |
so maintainers vetoed a new release? The problem still exists with latest Thanks On Tue, Sep 16, 2014 at 6:36 PM, Mikolaj Konarski notifications@github.com
|
I'm sorry about my originally confusing report of testing with older GHCs. The gist is I'd be more comfortable if somebody tested the current master branch of TS with ghc-0.12.x before we release. Then I'm fine with a release, but note that I'm not a maintainer, Simon Marlow is. @simonmar: please veto the release, if you think we should wait for fixes to some other issues or test some more. |
OK, I've tested on my own, with GHC 7.6.3, no previous package DB and gtk-0.12.5.7 and it runs fine. Package candidate released: http://hackage.haskell.org/package/threadscope-0.2.5/candidate Please test. |
Version 0.2.5 published. Closing. Thank you for all your help. |
Hi Mikolaj
I'm haskell newbee, I build threadscope by cabal and it failed.
''''
GUI/ProgressView.hs:92:15:
Could not deduce (System.Glib.UTFString.GlibString string0)
arising from a use of ‘labelNew’
from the context (WindowClass win)
bound by the type signature for
new :: WindowClass win => win -> IO () -> IO ProgressView
at GUI/ProgressView.hs:79:8-57
The type variable ‘string0’ is ambiguous
Note: there are several potential instances:
instance System.Glib.UTFString.GlibString
text-1.1.1.3:Data.Text.Internal.Text
-- Defined in ‘System.Glib.UTFString’
instance System.Glib.UTFString.GlibString [Char]
-- Defined in ‘System.Glib.UTFString’
In a stmt of a 'do' block: progText <- labelNew Nothing
In the expression:
do { win <- windowNew;
set win [containerBorderWidth := 10, windowTitle := "", ....];
progText <- labelNew Nothing;
set progText [miscXalign := 0, labelUseMarkup := True];
.... }
In an equation for ‘new’:
new parent cancelAction
= do { win <- windowNew;
set win [containerBorderWidth := 10, ....];
progText <- labelNew Nothing;
.... }
''''
The text was updated successfully, but these errors were encountered: