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

theft: 0.4.4 -> 0.4.5, fix pkg-config file #63186

Merged
merged 1 commit into from Jun 16, 2019

Conversation

thoughtpolice
Copy link
Member

The libtheft.pc file was using prefix=/usr/local for its own relative
-L/-l/-I parameters for GCC, giving incorrect results. (This is really
more of an upstream bug.)

This also adds myself to the maintainer list, and enables builds on
non-Linux platforms.

Signed-off-by: Austin Seipp as@fastly.com

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

The libtheft.pc file was using prefix=/usr/local for its own relative
-L/-l/-I parameters for GCC, giving incorrect results. (This is really
more of an upstream bug.)

This also adds myself to the maintainer list, and enables builds on
non-Linux platforms.

Signed-off-by: Austin Seipp <as@fastly.com>
@thoughtpolice thoughtpolice self-assigned this Jun 16, 2019
@thoughtpolice
Copy link
Member Author

@GrahamcOfBorg build theft

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.

None yet

1 participant