haskell plugin module err on startup - Intel Mac (pre M1)

[doom-neovim]

haskell plugin module err on startup - Intel Mac (pre M1)

[molleweide]

guys!!!! problem solved.

you had to symlink to gcc-11

ln -sf /usr/local/bin/gcc-11 /usr/local/bin/gcc

They updated the readme for tree sitter haskell.

[molleweide]

No stress!!

[kaii-zen]

macOS? If yes, I got past that by adding require('nvim-treesitter.install').compilers = { 'gcc' } to lua/doom/modules/config/doom-treesitter.lua (though I think anywhere would do, as long as it's early enough). clang defaults to c++11 while the Haskell tree-sitter parser relies on some c++14 features. something like that.

[kaii-zen]

Not exactly... there are 2 commonly used C/C++ compilers. Generally speaking, Linux-sphere uses gcc and macOS uses clang. In addition, the C++ language spec has different "versions". At least the clang that comes with macOS defaults to version 11 of the spec. Current gcc defaults to version 17 of the spec. Haskell treesitter depends on some features available in version 14 of the spec (and onwards). Also it looks like Apple symlinks gcc to clang which just adds to the confusion. macOS does not come with gcc (it used to tho). Hope that helps.

[NTBBloodbath]

Hey, that's really weird because it works for me, can you please provide some information of your system? e.g. treesitter binary version

I'll not be able to help too much right now because I'm not at home :(

[NTBBloodbath]

Hi, have you managed to fix this? If you don't have the treesitter CLI then you can try installing it and trying again

[molleweide]

Hi, have you managed to fix this? If you don't have the treesitter CLI then you can try installing it and trying again

Yo! No not yet. but i haven't really been working on it either. i have been learning other doom stuff.

macOS? If yes, I got past that by adding require('nvim-treesitter.install').compilers = { 'gcc' } to lua/doom/modules/config/doom-treesitter.lua (though I think anywhere would do, as long as it's early enough). clang defaults to c++11 while the Haskell tree-sitter parser relies on some c++14 features. something like that.

I will try this!!

[molleweide]

yo it didn't work :(
I am looking into the issue more now!

[kaii-zen]

yo it didn't work :(
I am looking into the issue more now!

Did you brew install gcc first? I should've probably mentioned it.

[molleweide]

ooh i just saw you replied again.

so this is what i have done:

1. l have read this: tree-sitter/tree-sitter-haskell#34
2. checked treesitter version
3. and installed gcc with brew now
   i also tried with clang bc somebody said recommended to try just incase.

still doesn't work. I will keep searching. I also asked about the error in the linked issue.

[molleweide]

wait a minute. doesn't this mean i am using wrong version of gcc. or how do i make sure that the brew provided gcc is used?? I have been googling a bit and it seems really hard to update clang++, no??

╰ gcc -v
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/c++/4.2.1
Apple clang version 12.0.0 (clang-1200.0.32.29)
Target: x86_64-apple-darwin19.6.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

[molleweide]

Yeah thanks man! The c world is quite new to me.

[molleweide]

Hi guys,

I just got my new macbook air m1 silicone and it seems that I get the exact same
error when starting neovim after having setup all of my configs.

I will report back if I figure out why.