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

unknown type OQS_SIG in sig_stfl.h included in oqs.h #1815

Closed
lingxinh-aws opened this issue Jun 7, 2024 · 3 comments
Closed

unknown type OQS_SIG in sig_stfl.h included in oqs.h #1815

lingxinh-aws opened this issue Jun 7, 2024 · 3 comments
Labels
bug Something isn't working; high priority to fix

Comments

@lingxinh-aws
Copy link

Describe the bug
"#include <oqs/sig_stfl.h>" was added in oqs.h in 971773a. It caused an error of "unknown type name 'OQS_SIG' " when compiling oqs-provider/oqsprov/oqs_sig.c, which includessig.h, which includes oqs.h. Then, OQS_SIG is referred in sig_stfl.h, but it is defined after #include <oqs/oqs.h> in the body of sig.h, so compilation failed.

To Reproduce
Steps to reproduce the behavior:

  1. Git clone the oqs-provider
  2. Run: cd oqs-provider
  3. Run: scripts/fullbuild.sh

Expected behavior
OpenSSL, liboqs and oqs-provider are all successfully built.

Screenshots
sig_stfl_h_error

Environment (please complete the following information):

  • OS [ Amazon Linux 2 ]
  • OpenSSL version [3.3.0-dev]
  • Compiler version used [gcc 7.3.1]
  • Build variables used ["-DCMAKE_BUILD_TYPE=Debug"]
  • liboqs version [main branch]

Additional context
Add any other context about the problem here.

@baentsch
Copy link
Member

Thanks for this report. Problem permeates through the complete OQS stack, see open-quantum-safe/oqs-provider#427 and open-quantum-safe/oqs-demos#281 . Possible work-around discussed here. A better solution of course is needed, see comment here: downstream-triggering CI should have caught this; still wonder why it didn't (ideas @SWilson4 ?)

@baentsch baentsch added the bug Something isn't working; high priority to fix label Jun 10, 2024
@SWilson4
Copy link
Member

SWilson4 commented Jun 11, 2024

Thanks for this report. Problem permeates through the complete OQS stack, see open-quantum-safe/oqs-provider#427 and open-quantum-safe/oqs-demos#281 . Possible work-around discussed here. A better solution of course is needed, see comment here: downstream-triggering CI should have caught this; still wonder why it didn't (ideas @SWilson4 ?)

I believe that it would have, but I think we (I really, as I was the one who merged the PR) simply missed manually triggering the downstream tests before merge. The trigger was broken during the final stages of the review, but I believe it was fixed before merge, so the tests should have been run (manually).

@SWilson4
Copy link
Member

Resolved by #1820.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working; high priority to fix
Projects
None yet
Development

No branches or pull requests

3 participants