Skip to content
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

ThreadScope does not build #122

Open
svenssonjoel opened this issue Mar 21, 2022 · 4 comments
Open

ThreadScope does not build #122

svenssonjoel opened this issue Mar 21, 2022 · 4 comments

Comments

@svenssonjoel
Copy link

The attempt to build was made on Ubuntu 21.10 using stack and the current state of ThreadScope master branch. commit d70f45e

cairo      > configure
cairo      > [1 of 2] Compiling Main             ( /tmp/stack-a013ee6ff927ebc3/cairo-0.13.8.1/Setup.hs, /tmp/stack-a013ee6ff927ebc3/cairo-0.13.8.1/.stack-work/dist/x86_64-linux-tinfo6/Cabal-3.0.1.0/setup/Main.o )
cairo      > [2 of 2] Compiling StackSetupShim   ( /home/pfp/.stack/setup-exe-src/setup-shim-mPHDZzAJ.hs, /tmp/stack-a013ee6ff927ebc3/cairo-0.13.8.1/.stack-work/dist/x86_64-linux-tinfo6/Cabal-3.0.1.0/setup/StackSetupShim.o )
cairo      > Linking /tmp/stack-a013ee6ff927ebc3/cairo-0.13.8.1/.stack-work/dist/x86_64-linux-tinfo6/Cabal-3.0.1.0/setup/setup ...
cairo      > Configuring cairo-0.13.8.1...
cairo      > build
glib       > configure
cairo      > Preprocessing library for cairo-0.13.8.1..
cairo      > setup: Error in C header file.
cairo      > 
cairo      > cairo-gtk2hs.i:1: (column 1) [FATAL] 
cairo      >   >>> Lexical error!
cairo      >   The character '#' does not fit here.
cairo      > 
glib       > [1 of 2] Compiling Main             ( /tmp/stack-a013ee6ff927ebc3/glib-0.13.8.1/Setup.hs, /tmp/stack-a013ee6ff927ebc3/glib-0.13.8.1/.stack-work/dist/x86_64-linux-tinfo6/Cabal-3.0.1.0/setup/Main.o )
glib       > [2 of 2] Compiling StackSetupShim   ( /home/pfp/.stack/setup-exe-src/setup-shim-mPHDZzAJ.hs, /tmp/stack-a013ee6ff927ebc3/glib-0.13.8.1/.stack-work/dist/x86_64-linux-tinfo6/Cabal-3.0.1.0/setup/StackSetupShim.o )
glib       > Linking /tmp/stack-a013ee6ff927ebc3/glib-0.13.8.1/.stack-work/dist/x86_64-linux-tinfo6/Cabal-3.0.1.0/setup/setup ...
glib       > Configuring glib-0.13.8.1...
glib       > build
glib       > Preprocessing library for glib-0.13.8.1..
glib       > setup: Error in C header file.
glib       >      
glib       > glib-object.i:1: (column 1) [FATAL] 
glib       >   >>> Lexical error!
glib       >   The character '#' does not fit here.
glib       >      
Progress 2/6      

--  While building package glib-0.13.8.1 (scroll up to its section to see the error) using:
      /tmp/stack-a013ee6ff927ebc3/glib-0.13.8.1/.stack-work/dist/x86_64-linux-tinfo6/Cabal-3.0.1.0/setup/setup --builddir=.stack-work/dist/x86_64-linux-tinfo6/Cabal-3.0.1.0 build --ghc-options " -fdiagnostics-color=always"
    Process exited with code: ExitFailure 1


--  While building package cairo-0.13.8.1 (scroll up to its section to see the error) using:
      /tmp/stack-a013ee6ff927ebc3/cairo-0.13.8.1/.stack-work/dist/x86_64-linux-tinfo6/Cabal-3.0.1.0/setup/setup --builddir=.stack-work/dist/x86_64-linux-tinfo6/Cabal-3.0.1.0 build --ghc-options " -fdiagnostics-color=always"
    Process exited with code: ExitFailure 1
@maoe
Copy link
Member

maoe commented Mar 24, 2022

gtk2hs/gtk2hs#163 looks relevant. Could you try LANG=C stack build as suggested here?

@RichardWarfield
Copy link

Same error encountered, and LANG=C stack build did not resolve it. What did fix it was bumping the gtk2hs-buildtools version in stack.yaml to 0.13.8.3.

@maoe
Copy link
Member

maoe commented Jul 13, 2022

@RichardWarfield Thanks for your comment. The issue isn't reproducible on any of my machines (Linux and macOS). Would you mind making a PR for your fix?

@OlaoluwaM
Copy link

For those who use Fedora, you'll also need to install the gtk2-devel package to get things to build successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants