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

perlPackages.Tk: fix build with clang 16 #253730

Merged
merged 1 commit into from
Sep 9, 2023

Conversation

reckenrode
Copy link
Contributor

Description of changes

The jpeg configure script fails to detect clang as a functioning C compiler because it uses a test with a main that returns an implicit int, which results in an error with clang 16.

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.

The jpeg `configure` script fails to detect clang as a functioning C
compiler because it uses a test with a `main` that returns an implicit
`int`, which results in an error with clang 16.
@stigtsp
Copy link
Member

stigtsp commented Sep 7, 2023

@ofborg build perlPackages.Tk

@dasJ dasJ merged commit 01986f4 into NixOS:master Sep 9, 2023
11 checks passed
@stigtsp
Copy link
Member

stigtsp commented Sep 14, 2023

More changes have been proposed upstream:

@reckenrode
Copy link
Contributor Author

More changes have been proposed upstream:

Once those are merged, I assume the nixpkgs changes can be dropped. However, I wonder if nixpkgs should be using the nixpkgs libjpeg instead of the vendored one.

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.

3 participants