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

"stack setup --verbose" should also cause verbose output of GHC configure process if possible #3716

Closed
mgsloan opened this issue Dec 28, 2017 · 2 comments

Comments

@mgsloan
Copy link
Contributor

@mgsloan mgsloan commented Dec 28, 2017

See #3712 (comment)

It's too bad stack setup --verbose doesn't also cause the GHC configure step to show all output.

@krisis
Copy link

@krisis krisis commented Jan 2, 2018

I can work on this issue if no one is looking into it already.

krisis pushed a commit to krisis/stack that referenced this issue Jan 2, 2018
If -v global flag is passed to stack-setup subcommand we log the GHC
configure output.
Ref: commercialhaskell#3716
krisis pushed a commit to krisis/stack that referenced this issue Jan 3, 2018
If -v global flag is passed to stack-setup subcommand we log the GHC
configure output.
Ref: commercialhaskell#3716
krisis pushed a commit to krisis/stack that referenced this issue Jan 3, 2018
If -v global flag is passed to stack-setup subcommand we log the GHC
configure output.
Ref: commercialhaskell#3716
@krisis krisis mentioned this issue Jan 3, 2018
0 of 2 tasks complete
krisis pushed a commit to krisis/stack that referenced this issue Jan 4, 2018
If -v global flag is passed to stack-setup subcommand we log the GHC
configure output.
Ref: commercialhaskell#3716
krisis pushed a commit to krisis/stack that referenced this issue Jan 5, 2018
If -v global flag is passed to stack-setup subcommand we log the GHC
configure output.
Ref: commercialhaskell#3716
@snoyberg
Copy link
Contributor

@snoyberg snoyberg commented Jan 7, 2018

Implemented via #3740, thanks!

@snoyberg snoyberg closed this Jan 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants