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

ber_metaocaml: n107 -> n111 #173816

Merged
merged 1 commit into from May 26, 2022
Merged

ber_metaocaml: n107 -> n111 #173816

merged 1 commit into from May 26, 2022

Conversation

ghost
Copy link

@ghost ghost commented May 20, 2022

Description of changes

The configure script has changed and no longer seems to provide a way
to specify the location of the x11 libraries or headers. Therefore
these configure options have been dropped.

Things done
  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
  • 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/)
  • Fits CONTRIBUTING.md.

[ "-x11lib" x11lib
"-x11include" x11inc
"-flambda"
[ "--enable-flambda"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this flambda option guarded by the useX11 condition? It seems unrelated…

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The formatting is now also weird. This could easily be in one line.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The formatting is now also weird. This could easily be in one line.

Fixed.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this flambda option guarded by the useX11 condition? It seems unrelated…

I'm afraid I have no idea. I was hesitant to make a functionality change in a version-bumping PR, but if you prefer I would be happy to remove the --enable-flambda.

Copy link
Author

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

x

The configure script has changed and no longer seems to provide a way
to specify the location of the x11 libraries or headers.  Therefore
these configure options have been dropped.
@vbgl vbgl merged commit b3fe9c3 into NixOS:master May 26, 2022
@ghost ghost deleted the pr/ber-metaocaml-upgrade-to-111 branch May 26, 2022 20:25
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