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.

Sign up for GitHub

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

Jump to bottom

Cabal warns about using deprecated profiling flag #2350

Closed
hesiod opened this issue Jul 7, 2016 · 1 comment
Closed

Cabal warns about using deprecated profiling flag #2350

hesiod opened this issue Jul 7, 2016 · 1 comment
Labels
awaiting pull request component: output (UI/UX)
Milestone
P2: Should

Comments

@hesiod
Copy link
Contributor

hesiod commented Jul 7, 2016

Upon running stack --profile on an executable, cabal warns about using the deprecated --enable-executable-profiling flag:

Warning: The flag --enable-executable-profiling is deprecated. Please use
--enable-profiling instead.

The related code seems to be here.

Using latest stack (1.1.2).
@sjakobi
Copy link
Member

sjakobi commented Jul 14, 2016

Thanks for the report!

Care to make a PR? You can find the cabal version in envConfigCabalVersion.

@sjakobi sjakobi added this to the P2: Should milestone Jul 14, 2016
@hesiod hesiod mentioned this issue Jul 15, 2016
Merged
hesiod added a commit to hesiod/stack that referenced this issue Jul 16, 2016
@hesiod
Update Changelog for commercialhaskell#2350/commercialhaskell#2377
bd5a9e3
@sjakobi sjakobi mentioned this issue Jul 18, 2016
Closed
sjakobi added a commit that referenced this issue Jul 18, 2016
@sjakobi
Merge pull request #2377 from hesiod/patch-deprecated-profiling-flag
80dc47e 
Fix cabal warning about use of a deprecated profiling flag (Fixes #2350)
@sjakobi sjakobi mentioned this issue Feb 22, 2017
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
awaiting pull request component: output (UI/UX)
Projects
None yet
Milestone
P2: Should
Development

No branches or pull requests
2 participants
@hesiod @sjakobi