Skip to content

arch-native defaults to True which is dangerous #308

Closed
@TerrorJack

Description

@TerrorJack

It's appreciated that the caveat of arch-native (creating non-portable binary due to -march=native) is documented and visible on the hackage page. But IMHO this is still dangerous, because downstream project authors may not audit all their dependency upgrades, and this looks incredibly likely to sneak into downstream build plans and making downstream CI pipelines produce binaries that crash at runtime on machines with CPUs older than GH action runners.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions