Skip to content

ghc-options (and maybe other things) passed in the wrong order in a program-options section #9290

Open
@jberryman

Description

@jberryman

related to #8900

I noticed this with the following on 9.6.3 and cabal 3.10.1.0, but same behavior with ghc-8.10.7 and cabal-3.6.2.0 (at least it isn't new I guess):

program-options
  ghc-options: -Wall
  ghc-options: -Werror 
  -- we'd expect this to override above. It does not; we need to swap the lines:
  ghc-options: -Wwarn 

The actual context was attempting to use -fno-info-table-map-with-fallback + -fno-info-table-map-with-stack

I was curious if cpp-options were similarly passed out of order, but that's not a supported field. Actually I guess this whole section is basically undocumented still…

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions