Fails to install Haskell tools because it's using the wrong compiler

[mouse07410]

MacOS Mojave 10.14.2, IntelliJ IDEA 2018.3.3, GHC-8.6.3 (rebuilt - see below)

21:56	Executing `/usr/local/bin/stack --system-ghc -j1 --stack-root /Users/uri/Library/Caches/com.github.rikvdkleij.intellij-haskell/lts-12 --resolver lts-12 --compiler ghc-8.4.4 --local-bin-path /Users/uri/Library/Caches/com.github.rikvdkleij.intellij-haskell/lts-12/bin install hoogle` failed: /usr/local/bin/stack --system-ghc -j1 --stack-root /Users/uri/Library/Caches/com.github.rikvdkleij.intellij-haskell/lts-12 --resolver lts-12 --compiler ghc-8.4.4 --local-bin-path /Users/uri/Library/Caches/com.github.rikvdkleij.intellij-haskell/lts-12/bin install hoogle:   
			Selected resolver: lts-12.26
			appar-0.1.7: download
			appar-0.1.7: configure
			appar-0.1.7: build
			appar-0.1.7: copy/register
			async-2.2.1: download
			async-2.2.1: configure
			async-2.2.1: build
			async-2.2.1: copy/register
			auto-update-0.1.4: download
			auto-update-0.1.4: configure
			auto-update-0.1.4: build
			auto-update-0.1.4: copy/register
			base-orphans-0.7: download
			base-orphans-0.7: configure
			base-orphans-0.7: build
			base-orphans-0.7: copy/registe... (show balloon)

My systems have Macports installed. That makes it impossible to link static Haskell executables, because Macports introduced its own copy of libiconv.dylib that mangles function names - which in turn makes it impossible to link anything with libHSbase.a (see https://trac.macports.org/ticket/57821).

Here's what the failure looks like:

Executing `/usr/local/bin/stack --system-ghc -j1 --stack-root /Users/uri/Library/Caches/com.github.rikvdkleij.intellij-haskell/lts-12 --resolver lts-12 --compiler ghc-8.4.4 --local-bin-path /Users/uri/Library/Caches/com.github.rikvdkleij.intellij-haskell/lts-12/bin install hoogle` failed: 
/usr/local/bin/stack --system-ghc -j1 --stack-root /Users/uri/Library/Caches/com.github.rikvdkleij.intellij-haskell/lts-12 --resolver lts-12 --compiler ghc-8.4.4 --local-bin-path /Users/uri/Library/Caches/com.github.rikvdkleij.intellij-haskell/lts-12/bin install hoogle:
 Selected resolver: lts-12.26 hoogle-5.0.17.3:
 configure hoogle-5.0.17.3: build -- 
While building package hoogle-5.0.17.3 using: /Users/uri/Library/Caches/com.github.rikvdkleij.intellij-haskell/lts-12/setup-exe-cache/x86_64-osx/Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.4 --builddir=.stack-work/dist/x86_64-osx/Cabal-2.2.0.1 build --ghc-options " -ddump-hi -ddump-to-file" Process exited with code: ExitFailure 1 
Logs have been written to: /Users/uri/Library/Caches/com.github.rikvdkleij.intellij-haskell/lts-12/global-project/.stack-work/logs/hoogle-5.0.17.3.log 
Configuring hoogle-5.0.17.3... clang: warning: argument unused during compilation: '-nopie' [-Wunused-command-line-argument] Preprocessing library for hoogle-5.0.17.3.. Building library for hoogle-5.0.17.3.. [ 1 of 28] Compiling General.IString ( src/General/IString.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/General/IString.o ) [ 2 of 28] Compiling General.Str ( src/General/Str.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/General/Str.o ) [ 3 of 28] Compiling General.Conduit ( src/General/Conduit.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/General/Conduit.o ) [ 4 of 28] Compiling General.Template ( src/General/Template.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/General/Template.o ) [ 5 of 28] Compiling General.Util ( src/General/Util.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/General/Util.o ) [ 6 of 28] Compiling General.Timing ( src/General/Timing.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/General/Timing.o ) [ 7 of 28] Compiling General.Log ( src/General/Log.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/General/Log.o ) [ 8 of 28] Compiling Input.Download ( src/Input/Download.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Input/Download.o ) [ 9 of 28] Compiling Input.Item ( src/Input/Item.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Input/Item.o ) [10 of 28] Compiling Input.Haddock ( src/Input/Haddock.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Input/Haddock.o ) [11 of 28] Compiling Input.Set ( src/Input/Set.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Input/Set.o ) [12 of 28] Compiling Paths_hoogle ( .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/autogen/Paths_hoogle.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Paths_hoogle.o ) [13 of 28] Compiling Input.Settings ( src/Input/Settings.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Input/Settings.o ) [14 of 28] Compiling Input.Reorder ( src/Input/Reorder.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Input/Reorder.o ) [15 of 28] Compiling Input.Cabal ( src/Input/Cabal.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Input/Cabal.o ) [16 of 28] Compiling General.Store ( src/General/Store.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/General/Store.o ) [17 of 28] Compiling Output.Types ( src/Output/Types.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Output/Types.o ) [18 of 28] Compiling Output.Names ( src/Output/Names.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Output/Names.o ) [19 of 28] Compiling Output.Items ( src/Output/Items.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Output/Items.o ) [20 of 28] Compiling Action.CmdLine ( src/Action/CmdLine.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Action/CmdLine.o ) [21 of 28] Compiling General.Web ( src/General/Web.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/General/Web.o ) [22 of 28] Compiling Query ( src/Query.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Query.o ) [23 of 28] Compiling Output.Tags ( src/Output/Tags.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Output/Tags.o ) [24 of 28] Compiling Action.Generate ( src/Action/Generate.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Action/Generate.o ) [25 of 28] Compiling Action.Search ( src/Action/Search.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Action/Search.o ) [26 of 28] Compiling Action.Server ( src/Action/Server.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Action/Server.o ) /private/var/folders/pd/mxn5kp_55jg23x7jjd10gtwm0000gn/T/stack66588/hoogle-5.0.17.3/src/Action/Server.hs:193:49: warning: [-Wdeprecations] In the use of ‘for’ (imported from Data.List.Extra): Deprecated: "Use flip map directly, since this function clashes with Data.Traversable.for" | 193 | showFroms local haddock xs = intercalate ", " $ for pkgs $ \p -> | ^^^ [27 of 28] Compiling Action.Test ( src/Action/Test.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Action/Test.o ) [28 of 28] Compiling Hoogle ( src/Hoogle.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Hoogle.o ) clang: warning: argument unused during compilation: '-nopie' [-Wunused-command-line-argument] clang: warning: argument unused during compilation: '-nopie' [-Wunused-command-line-argument] Preprocessing executable 'hoogle' for hoogle-5.0.17.3.. Building executable 'hoogle' for hoogle-5.0.17.3.. [1 of 1] Compiling Main ( src/Main.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/hoogle/hoogle-tmp/Main.o ) Linking .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/hoogle/hoogle ... clang: warning: argument unused during compilation: '-nopie' [-Wunused-command-line-argument] clang: warning: argument unused during compilation: '-nopie' [-Wunused-command-line-argument] Undefined symbols for architecture x86_64: "_iconv", referenced from: _hs_iconv in libHSbase-4.11.1.0.a(iconv.o) (maybe you meant: _base_GHCziIOziEncodingziIconv_iconvEncoding6_info, _base_GHCziIOziEncodingziIconv_iconvEncoding3_closure , _hs_iconv_open , _base_GHCziIOziEncodingziIconv_iconvEncoding10_bytes , _base_GHCziIOziEncodingziIconv_iconvEncoding15_info , _base_GHCziIOziEncodingziIconv_iconvEncoding1_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding11_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding13_info , _base_GHCziIOziEncodingziIconv_iconvEncoding_info , _base_GHCziIOziEncodingziIconv_iconvEncoding4_closure , _hs_iconv_close , _base_GHCziIOziEncodingziIconv_iconvEncoding2_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding8_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding12_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding1_info , _base_GHCziIOziEncodingziIconv_iconvEncoding4_info , _base_GHCziIOziEncodingziIconv_iconvEncoding7_info , _base_GHCziIOziEncodingziIconv_iconvEncoding6_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding9_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding9_info , _base_GHCziIOziEncodingziIconv_iconvEncoding12_info , _base_GHCziIOziEncodingziIconv_iconvEncoding11_info , _hs_iconv , _base_GHCziIOziEncodingziIconv_iconvEncoding7_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding13_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding8_info , _base_GHCziIOziEncodingziIconv_iconvEncoding2_info , _base_GHCziIOziEncodingziIconv_iconvEncoding14_bytes , _base_GHCziIOziEncodingziIconv_iconvEncoding15_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding5_closure ) "_iconv_open", referenced from: _hs_iconv_open in libHSbase-4.11.1.0.a(iconv.o) (maybe you meant: _hs_iconv_open) "_iconv_close", referenced from: _hs_iconv_close in libHSbase-4.11.1.0.a(iconv.o) (maybe you meant: _hs_iconv_close) "_locale_charset", referenced from: _localeEncoding in libHSbase-4.11.1.0.a(PrelIOUtils.o) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) `clang' failed in phase `Linker'. (Exit code: 1)

And here's the log file it refers to:
hoogle-log.txt

There are two solutions:

1. The one I prefer - I rebuilt GHC from sources (and put it into /opt/local/bin that precedes /usr/local/bin on the PATH), so it is linked against Macports, so it's libHSbase.a is happy with Macports-provided libiconv.dylib.
2. Pass ghc-option /usr/lib/libiconv.dylib to each and every invocation of GHC.

My ~/.cabal/config.platform and ~/.stack/config.yaml require system-ghc, but apparently this plugin doesn't honor it, and when it downloads a "standard" resolver with its own GHC - that GHC fails the link phase on libiconv.dylib.

What I'd like to see in this plugin:

• Ability to set/force my (system) GHC, rather than use what's in an old resolver.
• Ability to pass parameters to GHC, stack, etc.

[rikvdkleij]

It's not what you think it is...

That message is from that the plugin is using Stack to install the Haskell tools like hlint in an IntelliJ sandbox. Has nothing to do with your project. That LTS version is fixed to prevent API compatibility issues with Haskell tools.

Your issue is:
commercialhaskell/stack#825

[mouse07410]

It's not what you think it is...

Unfortunately, yes it is. Believe me, I've researched this issue when it hit me way before I started my attempts to use your plugin. And the solution I had to pick (because I cannot allow /usr/lib to precede /opt/local/lib on the search path, and because attempts to put the Apple-provided libiconv.dylib that libHSbase.a from GHC in the Haskell Platform expects into a special directory and put that directory first on the library search path did not work) was to make GHC that doesn't mind Macports. And everything worked - until your plugin started to enforce its view on what compiler/etc. should be used by forcing LTS.

That message is from that the plugin is using Stack to install the Haskell tools like hlint in an IntelliJ sandbox

Yes, and the problem is with the way your plugin is doing it.

That LTS version is fixed to prevent API compatibility issues with Haskell tools

Please give the user the possibility to "unfix" it. For example, my LTS is 13.2, and I'm forcing my compiler (and things that I need to work - work fine with it):

resolver: lts-13.2

system-ghc: true
skip-ghc-check: true

Your issue is: commercialhaskell/stack#825

Yes, that's the root cause - the question is how to work around it. Your plugin prevents the workaround - unnecessarily, I think.

I am asking again - since your plugin, as you said in your README, depends mainly on Stack and Intero, and I have both of these working fine - please add the feature to use intero, hlint, hoogle, etc. that are already installed. For example:

$ type hlint
hlint is /Users/uri/Library/Haskell/bin/hlint
$ hlint --version
HLint v2.1.12, (C) Neil Mitchell 2006-2018
$ type intero
intero is /Users/uri/Library/Haskell/bin/intero
$ intero --version
Intero 0.1.35
$ type hindent
hindent is /Users/uri/.local/bin/hindent
$ hindent --version
hindent 5.2.7
$ type stack
stack is /usr/local/bin/stack
$ stack --version
Version 1.9.3, Git revision 40cf7b37526b86d1676da82167ea8758a854953b (6211 commits) x86_64 hpack-0.31.1
$ type stylish-haskell
stylish-haskell is /Users/uri/.local/bin/stylish-haskell
$ stylish-haskell --version
stylish-haskell 0.9.2.0
$ 

To demonstrate that everything (else) is working on my setup:

$ cabal install hoogle
Warning: The install command is a part of the legacy v1 style of cabal usage.

Please switch to using either the new project style and the new-install
command or the legacy v1-install alias as new-style projects will become the
default in the next version of cabal-install. Please file a bug if you cannot
replicate a working v1- use case with the new-style commands.

For more information, see: https://wiki.haskell.org/Cabal/NewBuild

Resolving dependencies...
Downloading  appar-0.1.7
Downloading  auto-update-0.1.4
Downloaded   auto-update-0.1.4
Downloading  basement-0.0.8
Starting     auto-update-0.1.4
Downloaded   basement-0.0.8
Downloading  blaze-builder-0.4.1.0
Downloaded   appar-0.1.7
Starting     appar-0.1.7
Starting     basement-0.0.8
Downloaded   blaze-builder-0.4.1.0
Starting     blaze-builder-0.4.1.0
Building     auto-update-0.1.4
Building     basement-0.0.8
Building     appar-0.1.7
Building     blaze-builder-0.4.1.0
Completed    auto-update-0.1.4
Downloading  bsb-http-chunked-0.0.0.4
Downloaded   bsb-http-chunked-0.0.0.4
Starting     bsb-http-chunked-0.0.0.4
Completed    appar-0.1.7
Downloading  byteable-0.1.1
Downloaded   byteable-0.1.1
Starting     byteable-0.1.1
Building     bsb-http-chunked-0.0.0.4
Building     byteable-0.1.1
Completed    byteable-0.1.1
Downloading  byteorder-1.0.4
Downloaded   byteorder-1.0.4
Starting     byteorder-1.0.4
Completed    bsb-http-chunked-0.0.0.4
Downloading  case-insensitive-1.2.0.11
Downloaded   case-insensitive-1.2.0.11
Starting     case-insensitive-1.2.0.11
Building     byteorder-1.0.4
Building     case-insensitive-1.2.0.11
Completed    blaze-builder-0.4.1.0
Downloading  cereal-0.5.7.0
Downloaded   cereal-0.5.7.0
Starting     cereal-0.5.7.0
Building     cereal-0.5.7.0
Completed    byteorder-1.0.4
Downloading  cookie-0.4.4
Downloaded   cookie-0.4.4
Starting     cookie-0.4.4
Building     cookie-0.4.4
Completed    case-insensitive-1.2.0.11
Downloading  easy-file-0.2.2
Downloaded   easy-file-0.2.2
Starting     easy-file-0.2.2
Building     easy-file-0.2.2
Completed    cookie-0.4.4
Downloading  fmlist-0.9.2
Downloaded   fmlist-0.9.2
Starting     fmlist-0.9.2
Building     fmlist-0.9.2
Completed    easy-file-0.2.2
Downloading  generic-deriving-1.12.2
Downloaded   generic-deriving-1.12.2
Starting     generic-deriving-1.12.2
Building     generic-deriving-1.12.2
Completed    fmlist-0.9.2
Downloading  hourglass-0.2.12
Downloaded   hourglass-0.2.12
Starting     hourglass-0.2.12
Building     hourglass-0.2.12
Completed    cereal-0.5.7.0
Downloading  http-date-0.0.8
Downloaded   http-date-0.0.8
Starting     http-date-0.0.8
Building     http-date-0.0.8
Completed    hourglass-0.2.12
Downloading  js-flot-0.8.3
Downloaded   js-flot-0.8.3
Starting     js-flot-0.8.3
Completed    http-date-0.0.8
Downloading  js-jquery-3.3.1
Downloaded   js-jquery-3.3.1
Starting     js-jquery-3.3.1
Building     js-flot-0.8.3
Building     js-jquery-3.3.1
Completed    js-jquery-3.3.1
Downloading  mime-types-0.1.0.9
Downloaded   mime-types-0.1.0.9
Starting     mime-types-0.1.0.9
Completed    js-flot-0.8.3
Downloading  mmap-0.5.9
Downloaded   mmap-0.5.9
Starting     mmap-0.5.9
Building     mime-types-0.1.0.9
Building     mmap-0.5.9
Completed    mmap-0.5.9
Downloading  network-byte-order-0.0.0.0
Downloaded   network-byte-order-0.0.0.0
Starting     network-byte-order-0.0.0.0
Building     network-byte-order-0.0.0.0
Completed    network-byte-order-0.0.0.0
Downloading  network-uri-2.6.1.0
Downloaded   network-uri-2.6.1.0
Starting     network-uri-2.6.1.0
Building     network-uri-2.6.1.0
Completed    mime-types-0.1.0.9
Downloading  psqueues-0.2.7.0
Downloaded   psqueues-0.2.7.0
Starting     psqueues-0.2.7.0
Building     psqueues-0.2.7.0
Completed    generic-deriving-1.12.2
Downloading  simple-sendfile-0.2.27
Downloaded   simple-sendfile-0.2.27
Starting     simple-sendfile-0.2.27
Building     simple-sendfile-0.2.27
Completed    network-uri-2.6.1.0
Downloading  tar-0.5.1.0
Downloaded   tar-0.5.1.0
Starting     tar-0.5.1.0
Building     tar-0.5.1.0
Completed    simple-sendfile-0.2.27
Downloading  typed-process-0.2.3.0
Downloaded   typed-process-0.2.3.0
Starting     typed-process-0.2.3.0
Building     typed-process-0.2.3.0
Completed    typed-process-0.2.3.0
Downloading  unix-compat-0.5.1
Downloaded   unix-compat-0.5.1
Starting     unix-compat-0.5.1
Completed    psqueues-0.2.7.0
Downloading  unix-time-0.4.4
Downloaded   unix-time-0.4.4
Starting     unix-time-0.4.4
Building     unix-compat-0.5.1
Completed    basement-0.0.8
Downloading  utf8-string-1.0.1.1
Downloaded   utf8-string-1.0.1.1
Starting     utf8-string-1.0.1.1
Completed    unix-compat-0.5.1
Downloading  utility-ht-0.0.14
Building     utf8-string-1.0.1.1
Downloaded   utility-ht-0.0.14
Starting     utility-ht-0.0.14
Building     utility-ht-0.0.14
Building     unix-time-0.4.4
Completed    tar-0.5.1.0
Downloading  vault-0.3.1.2
Downloaded   vault-0.3.1.2
Starting     vault-0.3.1.2
Building     vault-0.3.1.2
Completed    unix-time-0.4.4
Downloading  word8-0.1.3
Downloaded   word8-0.1.3
Starting     word8-0.1.3
Completed    utf8-string-1.0.1.1
Downloading  zlib-0.6.2
Downloaded   zlib-0.6.2
Starting     zlib-0.6.2
Building     word8-0.1.3
Completed    vault-0.3.1.2
Downloading  iproute-1.7.7
Downloaded   iproute-1.7.7
Starting     iproute-1.7.7
Building     zlib-0.6.2
Building     iproute-1.7.7
Completed    word8-0.1.3
Downloading  http-types-0.12.2
Downloaded   http-types-0.12.2
Starting     http-types-0.12.2
Building     http-types-0.12.2
Completed    utility-ht-0.0.14
Downloading  socks-0.5.6
Downloaded   socks-0.5.6
Starting     socks-0.5.6
Building     socks-0.5.6
Completed    zlib-0.6.2
Downloading  http2-1.6.4
Completed    http-types-0.12.2
Downloading  memory-0.14.18
Downloaded   memory-0.14.18
Starting     memory-0.14.18
Downloaded   http2-1.6.4
Building     memory-0.14.18
Completed    iproute-1.7.7
Downloading  foundation-0.0.21
Downloaded   foundation-0.0.21
Starting     http2-1.6.4
Starting     foundation-0.0.21
Building     foundation-0.0.21
Building     http2-1.6.4
Completed    socks-0.5.6
Downloading  fast-logger-2.4.13
Downloaded   fast-logger-2.4.13
Starting     fast-logger-2.4.13
Building     fast-logger-2.4.13
Completed    fast-logger-2.4.13
Downloading  ListLike-4.6
Downloaded   ListLike-4.6
Starting     ListLike-4.6
Building     ListLike-4.6
Completed    memory-0.14.18
Downloading  storable-record-0.0.4
Downloaded   storable-record-0.0.4
Starting     storable-record-0.0.4
Building     storable-record-0.0.4
Completed    storable-record-0.0.4
Downloading  streaming-commons-0.2.1.0
Downloaded   streaming-commons-0.2.1.0
Starting     streaming-commons-0.2.1.0
Building     streaming-commons-0.2.1.0
Completed    http2-1.6.4
Downloading  wai-3.2.1.2
Downloaded   wai-3.2.1.2
Starting     wai-3.2.1.2
Building     wai-3.2.1.2
Completed    wai-3.2.1.2
Downloading  pem-0.2.4
Downloaded   pem-0.2.4
Starting     pem-0.2.4
Building     pem-0.2.4
Completed    pem-0.2.4
Downloading  cryptonite-0.25
Downloaded   cryptonite-0.25
Starting     cryptonite-0.25
Building     cryptonite-0.25
Completed    streaming-commons-0.2.1.0
Downloading  asn1-types-0.3.2
Downloaded   asn1-types-0.3.2
Starting     asn1-types-0.3.2
Building     asn1-types-0.3.2
Completed    asn1-types-0.3.2
Downloading  storable-tuple-0.0.3.3
Downloaded   storable-tuple-0.0.3.3
Starting     storable-tuple-0.0.3.3
Building     storable-tuple-0.0.3.3
Completed    storable-tuple-0.0.3.3
Downloading  wai-logger-2.3.4
Downloaded   wai-logger-2.3.4
Starting     wai-logger-2.3.4
Building     wai-logger-2.3.4
Completed    wai-logger-2.3.4
Downloading  warp-3.2.25
Downloaded   warp-3.2.25
Starting     warp-3.2.25
Building     warp-3.2.25
Completed    foundation-0.0.21
Downloading  http-client-0.5.14
Downloaded   http-client-0.5.14
Starting     http-client-0.5.14
Building     http-client-0.5.14
Completed    ListLike-4.6
Downloading  conduit-extra-1.3.0
Downloaded   conduit-extra-1.3.0
Starting     conduit-extra-1.3.0
Building     conduit-extra-1.3.0
Completed    warp-3.2.25
Downloading  asn1-encoding-0.9.5
Downloaded   asn1-encoding-0.9.5
Starting     asn1-encoding-0.9.5
Building     asn1-encoding-0.9.5
Completed    conduit-extra-1.3.0
Downloading  process-extras-0.7.4
Downloaded   process-extras-0.7.4
Starting     process-extras-0.7.4
Building     process-extras-0.7.4
Completed    asn1-encoding-0.9.5
Downloading  asn1-parse-0.9.4
Downloaded   asn1-parse-0.9.4
Starting     asn1-parse-0.9.4
Completed    http-client-0.5.14
Building     asn1-parse-0.9.4
Completed    asn1-parse-0.9.4
Completed    process-extras-0.7.4
Completed    cryptonite-0.25
Downloading  x509-1.7.5
Downloaded   x509-1.7.5
Starting     x509-1.7.5
Building     x509-1.7.5
Completed    x509-1.7.5
Downloading  x509-store-1.6.7
Downloaded   x509-store-1.6.7
Starting     x509-store-1.6.7
Building     x509-store-1.6.7
Completed    x509-store-1.6.7
Downloading  x509-validation-1.6.11
Downloading  x509-system-1.6.6
Downloaded   x509-system-1.6.6
Starting     x509-system-1.6.6
Downloaded   x509-validation-1.6.11
Starting     x509-validation-1.6.11
Building     x509-system-1.6.6
Building     x509-validation-1.6.11
Completed    x509-system-1.6.6
Completed    x509-validation-1.6.11
Downloading  tls-1.4.1
Downloaded   tls-1.4.1
Starting     tls-1.4.1
Building     tls-1.4.1
Completed    tls-1.4.1
Downloading  tls-session-manager-0.0.0.2
Downloading  connection-0.2.8
Downloaded   tls-session-manager-0.0.0.2
Starting     tls-session-manager-0.0.0.2
Downloaded   connection-0.2.8
Starting     connection-0.2.8
Building     tls-session-manager-0.0.0.2
Building     connection-0.2.8
Completed    tls-session-manager-0.0.0.2
Downloading  warp-tls-3.2.4.3
Downloaded   warp-tls-3.2.4.3
Starting     warp-tls-3.2.4.3
Building     warp-tls-3.2.4.3
Completed    connection-0.2.8
Downloading  http-client-tls-0.3.5.3
Downloaded   http-client-tls-0.3.5.3
Starting     http-client-tls-0.3.5.3
Building     http-client-tls-0.3.5.3
Completed    warp-tls-3.2.4.3
Completed    http-client-tls-0.3.5.3
Downloading  http-conduit-2.3.4
Downloaded   http-conduit-2.3.4
Starting     http-conduit-2.3.4
Building     http-conduit-2.3.4
Completed    http-conduit-2.3.4
Downloading  hoogle-5.0.17.4
Downloaded   hoogle-5.0.17.4
Starting     hoogle-5.0.17.4
Building     hoogle-5.0.17.4
Completed    hoogle-5.0.17.4
Updating documentation index
/Users/uri/Library/Haskell/share/doc/x86_64-osx-ghc-8.6.3/index.html
Loaded package environment from /Users/uri/.ghc/x86_64-darwin-8.6.3/environments/default

[mouse07410]

Also, please consider allowing user to pass ghc-options: to stack. That could be another workaround, as I described in the Macports ticket I referred to.

[rikvdkleij]

Please give the user the possibility to "unfix" it. For example, my LTS is 13.2, and I'm forcing my compiler (and things that I need to work - work fine with it):

That is in conflict with my solution, see the discussion under this commit for more context:
ndmitchell/hlint@7bb10df

The ~/.stack/stack.yaml is a global settings file. You can use this file to (hopefully) resolve the iconv issue.

I am asking again - since your plugin, as you said in your README, depends mainly on Stack and Intero, and I have both of these working fine - please add the feature to use intero, hlint, hoogle, etc. that are already installed

The README is still for the latest beta I have published to the stable channel of the Jetbrains plugin repo. And here I can write a whole story............

To demonstrate that everything (else) is working on my setup:

Cabal /= Stack.

[rikvdkleij]

Also, please consider allowing user to pass ghc-options: to stack. That could be another workaround, as I described in the Macports ticket I referred to.

Ok, will do that.

[mouse07410]

Cabal /= Stack.

Yeah, but that doesn't invalidate my point - that my setup was sound and solid. Here's the "pure" stack:

$ stack install hlint
data-default-class-0.1.2.0: download
cmdargs-0.10.20: download
clock-0.7.2: download
hscolour-1.24.4: download
data-default-class-0.1.2.0: configure
data-default-class-0.1.2.0: build
clock-0.7.2: configure
data-default-class-0.1.2.0: copy/register
clock-0.7.2: build
hscolour-1.24.4: configure
data-default-instances-containers-0.0.1: download                                                hscolour-1.24.4: build                                                                           cmdargs-0.10.20: configure                                                                       cmdargs-0.10.20: build                                                                           data-default-instances-containers-0.0.1: configure                                               clock-0.7.2: copy/register                                                                       data-default-instances-dlist-0.0.1: download                                                     data-default-instances-containers-0.0.1: build                                                   data-default-instances-dlist-0.0.1: configure                                                    data-default-instances-containers-0.0.1: copy/register                                           data-default-instances-dlist-0.0.1: build                                                       extra-1.6.14: download                                                                           extra-1.6.14: configure                                                                          4
data-default-instances-dlist-0.0.1: copy/register                                                
old-locale-1.0.0.7: download                                                                     
extra-1.6.14: build                                                              
old-locale-1.0.0.7: configure                                                    
old-locale-1.0.0.7: build                                                        
old-locale-1.0.0.7: copy/register                                                
data-default-instances-old-locale-0.0.1: download                                                data-default-instances-old-locale-0.0.1: configure                                               data-default-instances-old-locale-0.0.1: build                                                   data-default-instances-old-locale-0.0.1: copy/register                                           extra-1.6.14: copy/register                                                                      data-default-0.7.1.1: download                                                     
data-default-0.7.1.1: configure                                                    
old-time-1.1.0.3: download                                                             
data-default-0.7.1.1: build                                                            
old-time-1.1.0.3: configure                                                            
data-default-0.7.1.1: copy/register                                                    
polyparse-1.12.1: download                                                             
hscolour-1.24.4: copy/register                                                     
refact-0.3.0.2: download                                                           
cmdargs-0.10.20: copy/register                                                    
uniplate-1.6.12: download                                                          
old-time-1.1.0.3: build                                                            
polyparse-1.12.1: configure                                                        
polyparse-1.12.1: build                                                            
refact-0.3.0.2: configure                                                          
refact-0.3.0.2: build                                                              
uniplate-1.6.12: configure                                                         
uniplate-1.6.12: build                                                             
old-time-1.1.0.3: copy/register                                                    
refact-0.3.0.2: copy/register                                                      
uniplate-1.6.12: copy/register                                   
haskell-src-exts-util-0.2.4: download                        
haskell-src-exts-util-0.2.4: configure                       
polyparse-1.12.1: copy/register                              
haskell-src-exts-util-0.2.4: build                           
cpphs-1.20.8: download                                       
cpphs-1.20.8: configure                                  
cpphs-1.20.8: build                                      
haskell-src-exts-util-0.2.4: copy/register               
cpphs-1.20.8: copy/register                              
hlint-2.1.11: download      
hlint-2.1.11: configure     
hlint-2.1.11: build         
hlint-2.1.11: copy/register 
Completed 17 action(s).     
Copying from /Users/uri/.stack/snapshots/x86_64-osx/lts-13.0/8.6.3/bin/hlint to /Users/uri/.local/bin/hlint

Copied executables to /Users/uri/.local/bin:
- hlint
$ stack --version
Version 1.9.3, Git revision 40cf7b37526b86d1676da82167ea8758a854953b (6211 commits) x86_64 hpack-0.31.1
$ type hlint
hlint is /Users/uri/.local/bin/hlint
$ hlint --version
HLint v2.1.11, (C) Neil Mitchell 2006-2018
$ 

As you can see, works perfectly fine.

For example, my LTS is 13.2, and I'm forcing my compiler (and things that I need to work - work fine with it):

That is in conflict with my solution, see the discussion under this commit for more context...

Thank you for providing the context - very informative. I understand your position better now. I still would like to ask for an option to use system-installed components, if at all possible. Say, make your current approach a default, but offer the possibility to specify the tools explicitly?

The ~/.stack/stack.yaml is a global settings file. You can use this file to (hopefully) resolve the iconv issue.

It did not seem to work before. I will keep experimenting, but I don't have much hope here. :-(

Also, please consider allowing user to pass ghc-options: to stack. That could be another workaround, as I described in the Macports ticket I referred to.

Ok, will do that.

Yes please! This workaround worked for me with GHC itself, and with cabal. Maybe it would work with stack too, in which case a lot of things will be simplified.

[rikvdkleij]

I would like to know what I can change to the stack command which installs the Haskell tools to get it working for you (and in general). The stack install command is ran from the home directory.

Stack is used for:

• Building the project;
• Running ghci/intero;
• Installing the Haskell tools.

Do they all need that extra ghc-options? Or only for installing Haskell tools and what is that ghc-option?

As a workaround you can put the tool binaries in:
~/Library/Caches/com.github.rikvdkleij.intellij-haskell/lts-12/bin

[mouse07410]

I would like to know what I can change to the stack command which installs the Haskell tools to get it working for you (and in general).

First, please know that I really appreciate your willingness to seek solution to the problem I'm experiencing.

Based on my observation, this problem is shared by everybody who uses Macports and has to put Macports libraries first in the search path (for whatever reason).

... Do they all need that extra ghc-options? ...

The problem is that libHSbase.a requires Apple-provided libiconv.dylib. It means that Macports users would need this extra option for anything Haskell-related that links with libHSbase.a -> libiconv.dylib. Therefore, I think the answer to your question is:

• Building the project: yes, it requires that extra option because you cannot know in advance whether it would or would not link with libHSbase.a. Some of my projects did not need that library, but I suspect that in general it is linked against more often than not.
• Running ghci/intero: I suspect the answer is no, because AFAIK there's no linking involved. But I could be wrong - so better make a provision (be ready) to pass that option.
• Installing the Haskell tools: absolutely necessary. As most (all?) of these tools link against libHSbase.a, and so require Apple's libiconv.dylib.

As a workaround you can put the tool binaries in:
~/Library/Caches/com.github.rikvdkleij.intellij-haskell/lts-12/bin

But if I do, won't the plugin try to re-build them?

Another aspect of this problem is - what LTS (and therefore what tools, and particularly, what GHC) would projects created with this plugin use? Any GHC (from any LTS or otherwise) except for the one that's been rebuilt under Macports (like what I did) would require this option. But maybe it's addressed by your first bullet point.

[rikvdkleij]

I have read your comments a couple of times but it's all getting too confusing for me...
First some remarks.

I will not ask why not use brew :-) AFAIK most of mac developers use brew, including me. (I also use Ubuntu, btw)

But if I do, won't the plugin try to re-build them?

No, if the binary is there, no rebuild for that binary. Binaries are hlint, hoogle, hindent and stylish-haskell.

Provide a a way to affect the global .cabal template for a new project, or at least the package.yaml that's created from it.

package.yaml is leading. Stack will generate cabal file from package.yaml. Maybe this is the cause of your issue when you used your test project with IntelliJ. Btw, to import project in IntelliJ you have to select New project from existing sources and then select as External model, Haskell stack.

I had this in my stack.yaml in the project directory:

In the following Update section you also mean the project local stack config file. That's confusing.

To the best of your knowledge, which of the following directories can I delete

I do not understand why you want to delete files. Stack creates in home dir only .stack. I only delete that whole directory when stack behaves weird, so something had worked and suddenly not anymore.

And it is trying to rebuild intero. Is it going to to that for every project???

I do not see that rebuild in the log above that sentence. FYI: intero gets build per project because it has to be build with same GHC version as Haskell project. Once it is build, it does not get rebuild each time project is opened.

But anyways, it looks like most of the issues can be solved by setting ghc options in global stack config, project local stack config or cabal file. The plugin will not be changed to change any of the user it's files.

Also for now the plugin only support Haskell Stack projects. Including the way it's behaving. So Stack projects use GHCs which are installed by Stack otherwise it's getting too complicated to make the plugin solid in general. For example, a user can have multiple Haskell project with each a different Stackage resolver. It is already complicated to get it working on WIndows, Linux, Mac and with with Nix. Besides may other problems...
Eventually I want to replace intero by some other Haskell backend and support for Cabal/Nix projects. But stack is very useful for installing Haskell tools.

I still want to help you but you have to be specific in what I can do for you. When you need ghc-options to be passed to installation of the Haskell tools, no problem. Same for building the project and intero. But solution seems to be in setting those ghc-options in stack and/or cabal config files.
My mac uses brew so I can not reproduce your issues.

[mouse07410]

I have read your comments a couple of times but it's all getting too confusing for me...

It is even more confusing to me. ;-)
Mainly because I don't have a good grip on the ecosystem - some packages are built by cabal, some - by stack, each of these two "groups" has its own rules about what GHC to select. ~/.cabal/config.platform and ~/.stack/config.yaml clearly stated to use system GHC, and ignore the checks - but in some cases (your plugin, for example) that statement was ignored, and another GHC was downloaded and used.

So now I need to figure how to untangle this mess. What I'm leaning to now is removing my modified compiler altogether. If I have to use the "unmodified" (the original) one for anything at all, then presence of two differently-configured GHC compilers is a big problem. Then, I'd have to nuke my current cabal and stack databases, and update them a-new, with the GHC from Haskell Platform. Of course, I'll also need to make sure the configuration for all of these has the appropriate ghc-options: to work-around the libiconv.dylib issue.

I'm still in the process of figuring out the least damaging way of accomplishing the above.

To the best of your knowledge, which of the following directories can I delete

I do not understand why you want to delete files...

Because there are negative consequences of two GHC compilers being used - and I need to eradicate them.

I will not ask why not use brew :-)

There are reasons, besides being reluctant to change everything this machine had since 2011. ;-)

AFAIK most of mac developers use brew, including me. (I also use Ubuntu, btw)

Not really. And the amount of packages that Macports serves is about 3 times greater than what Brew has, AFAIK. But that's not the main factor in my case.

FYI: intero gets build per project because it has to be build with same GHC version as Haskell project...

Ah... I did not realize that. But if several projects are built with the same GHC - would they share the same intero? Or would each project still build its own copy?

But anyways, it looks like most of the issues can be solved by setting ghc options in global stack config, project local stack config or cabal file.

That's what I'm currently experimenting with - trying to find whether there are some config parameters for cabal, stack, and GHC invocations, that would work for all Haskell projects on my machines, regardless of whether they are created/edited by IntelliJ, or manually.

The plugin will not be changed to change any of the user's files

What about files like package.yaml and stack.yaml that get created (presumably by stack) when the project is created with stack new my-project? And who creates my-project.cabal file in this case?

I still want to help you but you have to be specific in what I can do for you.

Believe me, I appreciate this!

When you need ghc-options to be passed to installation of the Haskell tools, no problem. Same for building the project and intero

Excellent, thank you!

I'm certain that if those options are necessary - they'll have to be the same for user projects, Haskell tools, and intero.

Would you consider adding a plugin config parameter that would contain ghc-options to be passed? Rather than, e.g., hard-coding them into the plugin itself?

But solution seems to be in setting those ghc-options in stack and/or cabal config files.

I do not know yet. I think adding the ability for the user to configure the plugin to pass ghc-options would be beneficial, regardless.

My mac uses brew so I can not reproduce your issues.

I'm happy for you - to be able to reproduce this issue regularly is not a pleasure! ;-)

[mouse07410]

Update

I removed my modified compiler, and added the appropriate ghc-options: to ~/.cabal/config.platform and ~/.stack/config.yaml.

My projects seem to build fine, including installing intero. However, this plugin consistently fails to build intero, failing with unresolved names from libiconv:

Executing `/usr/local/bin/stack build intero` failed: /usr/local/bin/stack build intero: ghc-paths-0.1.0.9: configure -- While building package ghc-paths-0.1.0.9 using: /Users/uri/.stack/programs/x86_64-osx/ghc-8.6.3/bin/ghc --make -odir /private/var/folders/pd/mxn5kp_55jg23x7jjd10gtwm0000gn/T/stack14364/ghc-paths-0.1.0.9/.stack-work/dist/x86_64-osx/Cabal-2.4.0.1/setup -hidir /private/var/folders/pd/mxn5kp_55jg23x7jjd10gtwm0000gn/T/stack14364/ghc-paths-0.1.0.9/.stack-work/dist/x86_64-osx/Cabal-2.4.0.1/setup -i -i. -clear-package-db -global-package-db -package-db=/Users/uri/.stack/snapshots/x86_64-osx/lts-13.2/8.6.3/pkgdb -package-db=/Users/uri/src/p-test3/.stack-work/install/x86_64-osx/lts-13.2/8.6.3/pkgdb -hide-all-packages -package-id=Cabal-2.4.1.0-Df4rkGuWEtO4aZs4eesJ3r -package-id=base-4.12.0.0 -package-id=directory-1.3.3.0 -optP-include -optP/private/var/folders/pd/mxn5kp_55jg23x7jjd10gtwm0000gn/T/stack14364/ghc-paths-0.1.0.9/.stack-work/dist/x86_64-osx/Cabal-2.4.0.1/setup/setup_macros.h /private/var/folders/pd/mxn5kp_55jg23x7jjd10gtwm0000gn/T/stack14364/ghc-paths-0.1.0.9/Setup.hs /Users/uri/.stack/setup-exe-src/setup-shim-mPHDZzAJ.hs -main-is StackSetupShim.mainOverride -o /private/var/folders/pd/mxn5kp_55jg23x7jjd10gtwm0000gn/T/stack14364/ghc-paths-0.1.0.9/.stack-work/dist/x86_64-osx/Cabal-2.4.0.1/setup/setup -threaded Process exited with code: ExitFailure 1 Logs have been written to: /Users/uri/src/p-test3/.stack-work/logs/ghc-paths-0.1.0.9.log [1 of 2] Compiling Main ( /private/var/folders/pd/mxn5kp_55jg23x7jjd10gtwm0000gn/T/stack14364/ghc-paths-0.1.0.9/Setup.hs, /private/var/folders/pd/mxn5kp_55jg23x7jjd10gtwm0000gn/T/stack14364/ghc-paths-0.1.0.9/.stack-work/dist/x86_64-osx/Cabal-2.4.0.1/setup/Main.o ) /private/var/folders/pd/mxn5kp_55jg23x7jjd10gtwm0000gn/T/stack14364/ghc-paths-0.1.0.9/Setup.hs:29:18: warning: [-Wdeprecations] In the use of ‘rawSystemProgramStdoutConf’ (imported from Distribution.Simple.Program): Deprecated: "use getDbProgramOutput instead. This symbol will be removed in Cabal-3.0 (est. Mar 2019)." | 29 | libdir_ - rawSystemProgramStdoutConf (fromFlag (configVerbosity flags)) | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [2 of 2] Compiling StackSetupShim ( /Users/uri/.stack/setup-exe-src/setup-shim-mPHDZzAJ.hs, /private/var/folders/pd/mxn5kp_55jg23x7jjd10gtwm0000gn/T/stack14364/ghc-paths-0.1.0.9/.stack-work/dist/x86_64-osx/Cabal-2.4.0.1/setup/StackSetupShim.o ) Linking /private/var/folders/pd/mxn5kp_55jg23x7jjd10gtwm0000gn/T/stack14364/ghc-paths-0.1.0.9/.stack-work/dist/x86_64-osx/Cabal-2.4.0.1/setup/setup ... Undefined symbols for architecture x86_64: "_iconv", referenced from: _hs_iconv in libHSbase-4.12.0.0.a(iconv.o) (maybe you meant: _base_GHCziIOziEncodingziIconv_iconvEncoding_closure, _base_GHCziIOziEncodingziIconv_iconvEncoding1_info , _base_GHCziIOziEncodingziIconv_iconvEncoding3_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding4_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding7_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding15_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding4_info , _base_GHCziIOziEncodingziIconv_iconvEncoding6_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding6_info , _base_GHCziIOziEncodingziIconv_iconvEncoding5_closure , _hs_iconv_open , _base_GHCziIOziEncodingziIconv_iconvEncoding9_info , _base_GHCziIOziEncodingziIconv_iconvEncoding11_info , _base_GHCziIOziEncodingziIconv_iconvEncoding12_info , _base_GHCziIOziEncodingziIconv_iconvEncoding14_bytes , _hs_iconv_close , _base_GHCziIOziEncodingziIconv_iconvEncoding2_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding2_info , _base_GHCziIOziEncodingziIconv_iconvEncoding11_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding15_info , _base_GHCziIOziEncodingziIconv_iconvEncoding_info , _base_GHCziIOziEncodingziIconv_iconvEncoding12_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding8_info , _base_GHCziIOziEncodingziIconv_iconvEncoding7_info , _base_GHCziIOziEncodingziIconv_iconvEncoding1_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding8_closure , _hs_iconv , _base_GHCziIOziEncodingziIconv_iconvEncoding10_bytes , _base_GHCziIOziEncodingziIconv_iconvEncoding13_info , _base_GHCziIOziEncodingziIconv_iconvEncoding13_closure , _base_GHCziIOziEncodingziIconv_iconvEncoding9_closure ) "_iconv_open", referenced from: _hs_iconv_open in libHSbase-4.12.0.0.a(iconv.o) (maybe you meant: _hs_iconv_open) "_iconv_close", referenced from: _hs_iconv_close in libHSbase-4.12.0.0.a(iconv.o) (maybe you meant: _hs_iconv_close) "_locale_charset", referenced from: _localeEncoding in libHSbase-4.12.0.0.a(PrelIOUtils.o) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) `gcc' failed in phase `Linker'. (Exit code: 1)

First, I'd much rather have an option to tell this plugin "please, use this intero instead of trying to rebuild it yourself".
Second, perhaps it fails because the way your plugin invokes stack to build intero, it ignores or doesn't use ~/.stack/config.yaml? Because that's the only reason I can think of why I can build intero, and your plugin cannot...

Update 2

It tries (and fails!) to build a new intero for every project I create - though each and every one of them uses LTS-13.2, and GHC-8.6.3. And system-ghc: true is set in all the *.yaml files.
Could you do something about intero, please?

Update 3

I take some of the above back. The original (unmodified) GHC fails to build intero when invoked from stack. Here's my invocation:

$ DYLD_LIBRARY_PATH=/usr/lib stack --system-ghc -v --extra-lib-dirs /opt/local/lib/liconv install intero 2>&1 | tee ~/src/intero-build.txt

Here's the result:
intero-build.txt
Whatever seems to work for projects themselves, apparently does not work for intero.

[mouse07410]

@rikvdkleij would you consider adding support for cabal projects?

Update

It would help if in the config for IntelliJ-Haskell I could specify flags to pass to stack when invoking it. Could you add this capability?

Also, it looks like it would help if I could force system-ghc: true for all the builds that this plugin initiates. Is it possible?

[mouse07410]

@rikvdkleij would you be able to notify me (e.g., by posting here) when you add the ability to pass flags/parameters to all stack invocations?

[rikvdkleij]

So one set of flags for all stack calls?

[mouse07410]

I am not certain, but it seems that if the plugin would allow the user to enter a string, which could be comprised of multiple arguments/parameters/flags, and pass that string to every stack invocation - it would at least allow for experimenting.

And yes, I'd probably start with just one "string" (one "set of flags"). It's possible that we'd need more - e.g., a set of flags for building projects, and another set of flags for building Haskell tolls, etc. - but at this time I think/hope that it wouldn't be necessary.