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

opensp: fix build with clang 16 #240645

Merged
merged 1 commit into from
Jun 30, 2023
Merged

Conversation

reckenrode
Copy link
Contributor

Description of changes

There are two issues preventing a build with clang 16:

  • The configure scripts are too old and generate invalid config.h. This is fixed by using autoreconfHook with clang.
  • Use of the register storage class specifier, which is not allowed in C++17 (the default when building with clang 16). This is fixed by removing that usage.
Things done
  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 23.11 Release Notes (or backporting 23.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

There are two issues preventing a build with clang 16:
* The configure scripts are too old and generate invalid `config.h`.
  This is fixed by using `autoreconfHook` with clang.
* Use of the `register` storage class specifier, which is not allowed in
  C++17 (the default when building with clang 16). This is fixed by
  removing that usage.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants