Skip to content

Consider making MLK_CONFIG_NO_SUPERCOP implicit when MLK_CONFIG_MULTILEVEL_BUILD setΒ #1472

@mkannwischer

Description

@mkannwischer

Defining the SUPERCOP API (crypto_kem_enc etc.) when multiple parameter sets are built does not make sense.
The documentation even states:

 *              NOTE: You must set this for a multi-level build as the SUPERCOP
 *              naming does not disambiguate between the parameter sets.

Now that we have MLK_CONFIG_MULTILEVEL_BUILD, we might as well set this implicitly.
We forgot to set it in

- which led to problems with pq-code-package/mldsa-native#869.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions