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

brial: init at 1.2.3 #38794

Merged
merged 1 commit into from May 8, 2018
Merged

brial: init at 1.2.3 #38794

merged 1 commit into from May 8, 2018

Conversation

timokau
Copy link
Member

@timokau timokau commented Apr 11, 2018

Motivation for this change

This depends on #38762, do not merge before that

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-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 nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

homepage = https://github.com/BRiAl/BRiAl;
description = "Legacy version of PolyBoRi maintained by sagemath developers";
longDescription = ''
M4RIE is a library for fast arithmetic with dense matrices over small finite fields of even characteristic. It uses the M4RI library, implementing the same operations over the finite field F2.
Copy link
Member

Choose a reason for hiding this comment

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

wrong longDescription

@timokau timokau force-pushed the brial-init branch 2 times, most recently from caa0267 to b9a1987 Compare April 13, 2018 20:46
@timokau
Copy link
Member Author

timokau commented Apr 13, 2018

I just tried to nox-review this and it failed, don't merge.

@timokau
Copy link
Member Author

timokau commented Apr 13, 2018

Resolved. I had to disable the boost test framework, since thats not packaged.

src = fetchFromGitHub {
owner = "BRiAl";
repo = "BRiAl";
rev = "${version}";
Copy link
Member

Choose a reason for hiding this comment

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

rev = version

description = "Legacy version of PolyBoRi maintained by sagemath developers";
license = with licenses; [ gpl2 ];
maintainers = with maintainers; [ timokau ];
platforms = platforms.all;
Copy link
Member

Choose a reason for hiding this comment

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

Tested?

meta = with stdenv.lib; {
homepage = https://github.com/BRiAl/BRiAl;
description = "Legacy version of PolyBoRi maintained by sagemath developers";
license = with licenses; [ gpl2 ];
Copy link
Member

Choose a reason for hiding this comment

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

];

meta = with stdenv.lib; {
homepage = https://github.com/BRiAl/BRiAl;
Copy link
Member

Choose a reason for hiding this comment

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

inherit (src.meta) homepage

Copy link
Member Author

Choose a reason for hiding this comment

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

I think that is less clear than explicitly stating it. Its just more or less a coincidence that those two are the same.

@timokau timokau force-pushed the brial-init branch 2 times, most recently from 490eebf to 18a5281 Compare April 14, 2018 08:32
@dotlambda
Copy link
Member

@GrahamcOfBorg build brial

@GrahamcOfBorg
Copy link

Success on x86_64-linux (full log)

Attempted: brial

Partial log (click to expand)

make[1]: Leaving directory '/build/source/tests'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/im0yrp3msyl4bnvalfwbhlhi48zik1dm-brial-1.2.3
shrinking /nix/store/im0yrp3msyl4bnvalfwbhlhi48zik1dm-brial-1.2.3/lib/libbrial.so.3.0.1
shrinking /nix/store/im0yrp3msyl4bnvalfwbhlhi48zik1dm-brial-1.2.3/lib/libbrial_groebner.so.3.0.1
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/im0yrp3msyl4bnvalfwbhlhi48zik1dm-brial-1.2.3/lib 
patching script interpreter paths in /nix/store/im0yrp3msyl4bnvalfwbhlhi48zik1dm-brial-1.2.3
checking for references to /build in /nix/store/im0yrp3msyl4bnvalfwbhlhi48zik1dm-brial-1.2.3...
/nix/store/im0yrp3msyl4bnvalfwbhlhi48zik1dm-brial-1.2.3

@GrahamcOfBorg
Copy link

Success on aarch64-linux (full log)

Attempted: brial

Partial log (click to expand)

make[1]: Leaving directory '/build/source/tests'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/g86mkdsfdcn72niwy2fb6p9f0rycsnpz-brial-1.2.3
shrinking /nix/store/g86mkdsfdcn72niwy2fb6p9f0rycsnpz-brial-1.2.3/lib/libbrial_groebner.so.3.0.1
shrinking /nix/store/g86mkdsfdcn72niwy2fb6p9f0rycsnpz-brial-1.2.3/lib/libbrial.so.3.0.1
strip is /nix/store/j7d4mr0ikv974ig7yzhknpsq288js4bs-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/g86mkdsfdcn72niwy2fb6p9f0rycsnpz-brial-1.2.3/lib
patching script interpreter paths in /nix/store/g86mkdsfdcn72niwy2fb6p9f0rycsnpz-brial-1.2.3
checking for references to /build in /nix/store/g86mkdsfdcn72niwy2fb6p9f0rycsnpz-brial-1.2.3...
/nix/store/g86mkdsfdcn72niwy2fb6p9f0rycsnpz-brial-1.2.3

@dotlambda
Copy link
Member

There are tests in https://github.com/BRiAl/BRiAl/tree/master/tests. I'm not sure whether it makes sense to run these.

@dotlambda
Copy link
Member

Since this is the "legacy version of PolyBoRi maintained by sagemath developers", it should be put in the overlay.

@dotlambda dotlambda closed this Apr 14, 2018
@dotlambda dotlambda reopened this Apr 14, 2018
@timokau
Copy link
Member Author

timokau commented Apr 15, 2018

The tagline is wrong / confusing: brial is the new one, polybori is legacy. The github short description is "Successor to PolyBoRi".

];

configureFlags = [
"--with-boost-unit-test-framework=no" # boost-test is not packaged
Copy link
Member

Choose a reason for hiding this comment

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

Testing would probably reduce the necessary maintenance effort. So if it isn't too difficult, I'd suggest packaging boost-test and adding doCheck = true.

Copy link
Member Author

Choose a reason for hiding this comment

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

I've done that (boost init commit is now included in this PR).

Copy link
Member

Choose a reason for hiding this comment

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

Thanks a lot!

@timokau
Copy link
Member Author

timokau commented Apr 15, 2018

Again, not ready for merge (I only tested the build non-sandboxed with boost-test before pushing, doesn't build when sandboxed).

meta = with stdenv.lib; {
homepage = http://boost.org/libs/test;
description = "Boost.org test module";
license = {
Copy link
Member

Choose a reason for hiding this comment

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

There is licenses.boost.

@timokau timokau changed the title brial: init at 1.2.3 [WIP] brial: init at 1.2.3 Apr 15, 2018
@timokau
Copy link
Member Author

timokau commented Apr 15, 2018

I'm having issues with boost-test. First I thought just copying would be enough (since the boost docs indicate sometiimes it is and boost-process is packaged that way). Unfortunately its not.

The build fails here:

Scanning dependencies of target doc-example53
[ 72%] Building CXX object CMakeFiles/doc-example53.dir/tmp/nix-build-boost-test-1.66.0.drv-0/source/doc/examples/example53.run-fail.cpp.o
[ 72%] Linking CXX executable static-library-custom-init-test
/nix/store/27x7pinqdsl9f3rpbm8bsszd9fhwq266-glibc-2.27/lib/crt1.o: In function `_start':
/build/glibc-2.27/csu/../sysdeps/x86_64/start.S:104: undefined reference to `main'
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/static-library-custom-init-test.dir/build.make:96: static-library-custom-init-test] Error 1
make[1]: *** [CMakeFiles/Makefile2:5806: CMakeFiles/static-library-custom-init-test.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 72%] Linking CXX executable doc-example52
[ 72%] Built target doc-example52
[ 73%] Linking CXX executable doc-example51
[ 73%] Built target doc-example51
[ 74%] Linking CXX executable doc-example53
[ 74%] Built target doc-example53
make: *** [Makefile:95: all] Error 2
builder for '/nix/store/r9x5zbg7g01zlb1yzgqxksac7f9x83pg-boost-test-1.66.0.drv' failed with exit code 2

I don't know much about cmake or boost. Do you have an idea what the error might be? I pushed the update to boost-test (still not mergeable).

@timokau
Copy link
Member Author

timokau commented Apr 22, 2018

@peti @wkennington (maintainers of boost): Do you have an idea what causes the build failure? Do you think its a good idea to package boost-test?

@timokau timokau mentioned this pull request May 4, 2018
8 tasks
@timokau timokau force-pushed the brial-init branch 2 times, most recently from 5eacbfa to d7ca96a Compare May 6, 2018 13:06
@timokau timokau changed the title [WIP] brial: init at 1.2.3 brial: init at 1.2.3 May 6, 2018
@timokau
Copy link
Member Author

timokau commented May 6, 2018

Since I don't know how to proceed and apparently nobody else does either I reverted the boost-test change.

};

configureFlags = [
"--with-boost-unit-test-framework=no"
Copy link
Member

Choose a reason for hiding this comment

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

You might want to add

# FIXME: package boost-test and enable doCheck

here and then it's good to go.

@timokau
Copy link
Member Author

timokau commented May 7, 2018

Done

@dotlambda dotlambda merged commit 6e6005c into NixOS:master May 8, 2018
@timokau timokau deleted the brial-init branch May 8, 2018 11:01
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

4 participants