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

Unrecognized field at the top-level #8221

Closed
cblp opened this issue Jun 15, 2022 · 5 comments
Closed

Unrecognized field at the top-level #8221

cblp opened this issue Jun 15, 2022 · 5 comments
Labels
status: fixed in master The fix or feature is already included on master branch

Comments

@cblp
Copy link
Contributor

cblp commented Jun 15, 2022

Describe the bug

I want to specify ghc-options for all local packages

According to the documentation,

They can be specified at the top-level, in which case they apply only to local package
https://cabal.readthedocs.io/en/3.6/cabal-project.html#package-configuration-options

(Why singular, by the way?)

And I get

Warning: .../cabal.project: Unrecognized
field 'ghc-options' on line 13

To Reproduce
Steps to reproduce the behavior:

-- cabal.project
ghc-options: -Werror

Expected behavior
-Werror applied to all local packages and not applied to dependencies.

System information

  • Operating system: macOS 12.4
  • cabal-install version 3.6.2.0, compiled using version 3.6.2.0 of the Cabal library
  • The Glorious Glasgow Haskell Compilation System, version 8.10.7
@cblp
Copy link
Contributor Author

cblp commented Jun 15, 2022

oh, it's a known bug #3579

@cblp
Copy link
Contributor Author

cblp commented Jun 15, 2022

fixed in master; not fixed in production

@Mikolaj
Copy link
Member

Mikolaj commented Jun 15, 2022

Yes, it looks so. Please install cabal 3.8 pre-release (https://discourse.haskell.org/t/cabal-3-8-pre-released/4631/1) and kindly confirm it's fixed for you. If so, let's close as fixed (we don't wait until fixes are released).

@Mikolaj
Copy link
Member

Mikolaj commented Jun 17, 2022

Optimistically closing as fixed. @cblp: pretty please, make sure to alert us if that's not the case.

@Mikolaj Mikolaj closed this as completed Jun 17, 2022
@Mikolaj Mikolaj added the status: fixed in master The fix or feature is already included on master branch label Jun 17, 2022
@jneira
Copy link
Member

jneira commented Jun 18, 2022

only want to stress you can't use ghc-options directly at top-level but under program-options section

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: fixed in master The fix or feature is already included on master branch
Projects
None yet
Development

No branches or pull requests

3 participants