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

fflas-ffpack: Add darwin support #45013

Merged
merged 1 commit into from Aug 19, 2018
Merged

Conversation

jbaum98
Copy link
Contributor

@jbaum98 jbaum98 commented Aug 14, 2018

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 nox --run "nox-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)
  • Fits CONTRIBUTING.md.

@GrahamcOfBorg GrahamcOfBorg added the 6.topic: darwin Running or building packages on Darwin label Aug 14, 2018
@jbaum98 jbaum98 force-pushed the fflas-ffpack_darwin branch 3 times, most recently from 2fc87cc to d07a7e1 Compare August 14, 2018 06:05
@jbaum98 jbaum98 force-pushed the fflas-ffpack_darwin branch 2 times, most recently from c5671e3 to c9164ad Compare August 14, 2018 15:35
@jbaum98
Copy link
Contributor Author

jbaum98 commented Aug 14, 2018

This actually isn't working: it stills fails tests, but they weren't being run before because doCheck was set to false even though doInstallCheck was set to true. Will reopen when I fix it.

@jbaum98 jbaum98 closed this Aug 14, 2018
@jbaum98
Copy link
Contributor Author

jbaum98 commented Aug 14, 2018

The problem seems to be with openblas on darwin. It works with blas. I will also try with atlas.

Is there a known issue with openblas on darwin?

@timokau
Copy link
Member

timokau commented Aug 14, 2018

Not that I know of, what is the error?

Common practice would be to leave the PR open but add a [WIP] prefix to the title.


# doInstallCheck needed for darwin
doInstallCheck = true;
installCheckTarget = "check";
Copy link
Member

Choose a reason for hiding this comment

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

Same as the other tickets, please expand and report upstream. Does the same issue actually affect all 3 packages? I could understand linbox and givaro since they are from the same people, but this seems weird.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No this was my mistake, I saw a segfault and assumed it was the same problem, but it was actually openblas. But then it wasn't running the tests so it was looking like it was working.

nativeBuildInputs = [
autoreconfHook
pkgconfig
] ++ stdenv.lib.optionals doCheck checkInputs;
] ++ stdenv.lib.optionals doInstallCheck checkInputs;

Copy link
Member

Choose a reason for hiding this comment

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

Not sure what github is telling me here. Are you adding whitespace at the start of the line / changing spaces to tabs or something?

@timokau
Copy link
Member

timokau commented Aug 14, 2018

There is this, but they don't say anything about darwin. Might be relevant, might not be.

@timokau
Copy link
Member

timokau commented Aug 14, 2018

Still I'd avoid switching to atlas if possible.

@jbaum98
Copy link
Contributor Author

jbaum98 commented Aug 14, 2018

So I should just use regular blas instead of openblas over atlas?

@jbaum98 jbaum98 reopened this Aug 14, 2018
@jbaum98 jbaum98 changed the title fflas-ffpack: Add darwin support [WIP] fflas-ffpack: Add darwin support Aug 14, 2018
@timokau
Copy link
Member

timokau commented Aug 14, 2018

I don't think there is such a thing as regular blas (might be wrong). blas just defines an interface and openblas and atlas are the two main implementations. It should stay with openblas if possible. openblas seems generally preferred, has more features and is better supported on nix (more optimizations).

What error are you getting?

@jbaum98
Copy link
Contributor Author

jbaum98 commented Aug 14, 2018 via email

@timokau
Copy link
Member

timokau commented Aug 14, 2018

Oh, didn't know about that one. Probably that is the one that started the standard. I always thought the first one was proprietary for some reason.

Apparently this is the upstream issue that caused debian to temporarily switch to atlas. You could try if downgrading openblas to 0.3.1 fixes the issue.

Edit: actually this is upstream

@timokau
Copy link
Member

timokau commented Aug 14, 2018

From your history it looks like you're trying to get sage to build on darwin, is that right?

@jbaum98
Copy link
Contributor Author

jbaum98 commented Aug 14, 2018 via email

@timokau
Copy link
Member

timokau commented Aug 14, 2018

Awesome! I'm the sage maintainer. If you need help or review, ping me.

@jbaum98
Copy link
Contributor Author

jbaum98 commented Aug 15, 2018

Okay here's the situation. There are three (maybe four) BLAS libraries we could use: openblas, blas, Accelerate, and maybe atlas. It seems like openblas is what we'd like to use, but it doesn't work on darwin:

==============================================
   FFLAS-FFPACK 2.3.2: tests/test-suite.log
==============================================

# TOTAL: 33
# PASS:  11
# SKIP:  0
# XFAIL: 0
# FAIL:  22
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: test-fger
===============

FAIL test-fger (exit status: 139)

FAIL: test-ftrsv
================

Checking with Modular<double> mod 36289873
FAIL test-ftrsv (exit status: 139)

FAIL: test-ftrtri
=================

Checking with Modular<double> mod 131
Checking FTRTRI_Lower_Unit....................PASSED (0.031471)
Checking FTRTRI_Upper_Unit....................PASSED (0.017059)
Checking FTRTRI_Lower_NonUnit.................PASSED (0.023665)
Checking FTRTRI_Upper_NonUnit.................PASSED (0.021203)
Checking with Modular<double> mod 13
Checking FTRTRI_Lower_Unit....................PASSED (0.018172)
Checking FTRTRI_Upper_Unit....................PASSED (0.020317)
Checking FTRTRI_Lower_NonUnit.................PASSED (0.016548)
Checking FTRTRI_Upper_NonUnit.................PASSED (0.00784)
Checking with Modular<double> mod 33811
Checking FTRTRI_Lower_Unit....................PASSED (0.004757)
Checking FTRTRI_Upper_Unit....................PASSED (0.004347)
Checking FTRTRI_Lower_NonUnit.................PASSED (0.004994)
Checking FTRTRI_Upper_NonUnit.................PASSED (0.007178)
Checking with ModularBalanced<double> mod 131
FAIL test-ftrtri (exit status: 139)

FAIL: test-ftrmv
================

Checking with Modular<double> mod 646771
Checking FTRMV_Lower_NoTrans_Unit............PASSED (0.004181)
FAIL test-ftrmv (exit status: 139)

FAIL: test-ftrsm
================

Checking with Modular<double> mod 1547437
FAIL test-ftrsm (exit status: 139)

FAIL: test-ftrsm-check
======================

FAIL test-ftrsm-check (exit status: 139)

FAIL: test-ftrmm
================

Checking with Modular<double> mod 61
FAIL test-ftrmm (exit status: 139)

FAIL: test-fgemm
================

Checking ..........................Modular<double> mod 1747 ...  ** On entry to DGEMM  parameter number 10 had an illegal value
 ** On entry to DGEMM  parameter number 10 had an illegal value
 ** On entry to DGEMM  parameter number 10 had an illegal value
 ** On entry to DGEMM  parameter number 10 had an illegal value
 ** On entry to DGEMM  parameter number 10 had an illegal value
 ** On entry to DGEMM  parameter number 10 had an illegal value
FAIL
a   :1, b   : 0
m   :16, n   : 44, k   : 36
ldA :48, ldB : 47, ldC : 45
Error C[0,0]=813 D[0,0]=202
Error C[0,1]=205 D[0,1]=612
Error C[0,2]=256 D[0,2]=1713
Error C[0,3]=102 D[0,3]=494
Error C[0,4]=872 D[0,4]=631
Error C[0,5]=165 D[0,5]=699
Error C[0,6]=1299 D[0,6]=1459
Error C[0,7]=246 D[0,7]=70
Error C[0,8]=1737 D[0,8]=1069
Error C[0,9]=592 D[0,9]=1088
Error C[0,10]=401 D[0,10]=637
Error C[0,11]=396 D[0,11]=1058
Error C[0,12]=1587 D[0,12]=848
Error C[0,13]=1498 D[0,13]=838
Error C[0,14]=1695 D[0,14]=1059
Error C[0,15]=196 D[0,15]=974
Error C[0,16]=290 D[0,16]=1518
Error C[0,17]=1634 D[0,17]=1479
Error C[0,18]=213 D[0,18]=1132
Error C[0,19]=769 D[0,19]=1695
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
FAILED
FAIL test-fgemm (exit status: 1)

FAIL: test-fgemm-check
======================

FAIL test-fgemm-check (exit status: 139)

FAIL: test-lu
=============

FAIL test-lu (exit status: 139)

FAIL: test-pluq-check
=====================

FAIL test-pluq-check (exit status: 139)

FAIL: test-fsyrk
================

Checking with Modular<double> mod 5
FAIL test-fsyrk (exit status: 139)

FAIL: test-fsytrf
=================

FAIL test-fsytrf (exit status: 139)

FAIL: test-invert-check
=======================

 -q 131071 -n 1000 -i 3 -s 1534291159349551
FAIL test-invert-check (exit status: 139)

FAIL: test-rankprofiles
=======================

FAIL test-rankprofiles (exit status: 139)

FAIL: test-det-check
====================

init: 0.00863194s (0.02807 cpu) [1]
FAIL test-det-check (exit status: 139)

FAIL: test-echelon
==================

FAIL test-echelon (exit status: 139)

FAIL: test-charpoly
===================

FAIL test-charpoly (exit status: 139)

FAIL: test-charpoly-check
=========================

FAIL test-charpoly-check (exit status: 139)

FAIL: test-minpoly
==================

FAIL test-minpoly (exit status: 139)

FAIL: test-solve
================

FAIL test-solve (exit status: 139)

FAIL: test-fgemv
================

FAIL test-fgemv (exit status: 139)

============================================================================
Testsuite summary for FFLAS-FFPACK 2.3.2
============================================================================
# TOTAL: 33
# PASS:  11
# SKIP:  0
# XFAIL: 0
# FAIL:  22
# XPASS: 0
# ERROR: 0

I looked at test-fger in lldb, and it seemed like the problem was within a call to an openblas function cblas_dger:

* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT)
    frame #0: 0x0000000102ec6e50 libopenblasp-r0.3.1.dylib`daxpy_kernel_8 + 16
libopenblasp-r0.3.1.dylib`daxpy_kernel_8:
->  0x102ec6e50 <+16>: vmovups (%rdx,%rax,8), %ymm12
    0x102ec6e55 <+21>: vmovups 0x20(%rdx,%rax,8), %ymm13
    0x102ec6e5b <+27>: vmovups 0x40(%rdx,%rax,8), %ymm14
    0x102ec6e61 <+33>: vmovups 0x60(%rdx,%rax,8), %ymm15
Target 0: (test-fger) stopped.
(lldb) up
frame #1: 0x0000000102ec69cb libopenblasp-r0.3.1.dylib`daxpy_k_HASWELL + 91
libopenblasp-r0.3.1.dylib`daxpy_k_HASWELL:
    0x102ec69cb <+91>:  cmpq   %r14, %rbx
    0x102ec69ce <+94>:  jge    0x102ec6e27               ; <+1207>
    0x102ec69d4 <+100>: movsd  -0x38(%rbp), %xmm0        ; xmm0 = mem[0],zero
    0x102ec69d9 <+105>: movq   %r14, %rax
(lldb) up
frame #2: 0x0000000102ece2e9 libopenblasp-r0.3.1.dylib`dger_k_HASWELL + 185
libopenblasp-r0.3.1.dylib`dger_k_HASWELL:
    0x102ece2e9 <+185>: movsd  -0x30(%rbp), %xmm1        ; xmm1 = mem[0],zero
    0x102ece2ee <+190>: movq   %r12, %rcx
    0x102ece2f1 <+193>: movq   %r15, %r12
    0x102ece2f4 <+196>: addq   $0x20, %rsp
(lldb) up
frame #3: 0x00000001001fcadb libopenblasp-r0.3.1.dylib`cblas_dger + 507
libopenblasp-r0.3.1.dylib`cblas_dger:
    0x1001fcadb <+507>: jmp    0x1001fcafd               ; <+541>
    0x1001fcadd <+509>: movq   %r13, %rdi
    0x1001fcae0 <+512>: movq   %r12, %rsi
    0x1001fcae3 <+515>: movq   %rcx, %rdx
(lldb) up
test-fger was compiled with optimization - stepping may behave oddly; variables may not be available.
frame #4: 0x000000010000ce26 test-fger`FFLAS::fger(F=<unavailable>, M=44, N=36, alpha=<unavailable>, x=0x0000000104701910, incx=1, y=0x0000000104701af0, incy=<unavailable>, A=<unavailable>, lda=<unavailable>, H=0x00007ffeefbfe538) at fflas_fger.inl:185 [opt]
   182 	#ifdef __FFLASFFPACK_OPENBLAS_NUM_THREADS
   183 			openblas_set_num_threads(__FFLASFFPACK_OPENBLAS_NUM_THREADS);
   184 	#endif
-> 185 			cblas_dger( CblasRowMajor, (int)M, (int)N, alpha, x, (int)incx, y, (int)incy, A, (int)lda );
   186 		}
   187 	
   188 		template<class Field>

Accelerate is made just for mac so it should be well-tuned, so that seems like it's our second choice. Unfortunately it has one failing test:

==============================================
   FFLAS-FFPACK 2.3.2: tests/test-suite.log
==============================================

# TOTAL: 33
# PASS:  32
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: test-ftrsm
================

Checking with Modular<double> mod 10103
Checking FTRSM_Lower_Left_NoTrans_Unit............PASSED (0.003281)
Checking FTRSM_Upper_Left_NoTrans_Unit............PASSED (0.002883)
libc++abi.dylib: terminating with uncaught exception of type FailureFgemmCheck
Checking FTRSM_Lower_Left_Trans_Unit..............FAIL test-ftrsm (exit status: 134)

This may or may not be a bug, because the README says it is, but the issue it links to is closed, so I'm confused.

So, then, we settle for blas and it build no problem. I haven't had a chance to get atlas building to see if that'll work.

@timokau timokau mentioned this pull request Aug 15, 2018
9 tasks
@timokau
Copy link
Member

timokau commented Aug 15, 2018

Did you try to build with an older version of openblas?

@jbaum98
Copy link
Contributor Author

jbaum98 commented Aug 15, 2018

I tried with a newer 0.3.2 and older 0.3.0, all the same. Should I go older?

@jbaum98
Copy link
Contributor Author

jbaum98 commented Aug 15, 2018

Maybe sage just doesn't run tests, and that's why they can get away with using openblas on darwin and we can't?

@timokau
Copy link
Member

timokau commented Aug 15, 2018

Can I use that to handle the --with-blas-libs in a uniform way? Right now I have to explicitly pass it in all-packages.nix.

Good question, I don't think you can. You could just make the value dependent on isDarwin.

Maybe sage just doesn't run tests, and that's why they can get away with using openblas on darwin and we can't?

Again, its a bit confusing 😀
They do run the tests on some dependencies sometimes. Specifically, they run the dependencies on all the packages where a spkg-check (instructions on how to run the tests are to be run), but not by default. Since there is no spkg-check in build/pkgs/fflas_ffpack, it looks like they don't run the tests for this package.

@timokau
Copy link
Member

timokau commented Aug 15, 2018

So if you want to double check what the reason for the failures is, you could write an spkg-check for sage's fflas-ffpack and try to build sage with tests from there. But that will take a long time and is quite some effort that will likely have the same failure as here. I'd try the upstream report first. Often times an issue packagers spend ages to debug is obvious to people familiar with the internals.

@timokau
Copy link
Member

timokau commented Aug 16, 2018

If you'd like to keep it the way it is now, please add a comment to the package file somewhere explaining that openblas with osx causes issues, linking to the upstream issue and mentioning that blas is set conditionally in all-packages.nix. If we only have the blas conditional in all-packages.nix it is likely to be forgotten, even if the issue is fixed upstream in the future.

After that if you're happy with it and tests pass on both platforms, I'd say its good to go.

@timokau
Copy link
Member

timokau commented Aug 16, 2018

For the record, I did ask on irc if there is a better way for the lib name, but apparently there is not.

@@ -9169,7 +9169,16 @@ with pkgs;

ffcast = callPackage ../tools/X11/ffcast { };

fflas-ffpack = callPackage ../development/libraries/fflas-ffpack {};
fflas-ffpack = callPackage ../development/libraries/fflas-ffpack {
blas = if stdenv.isDarwin then {
Copy link
Member

Choose a reason for hiding this comment

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

I think this is a bit confusing since blas is supposed to be a package. Adding a linkName as a passthru attribute to the packages and using blas.linkName or "blas" instead seems much nicer.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh, a passthru attribute is exactly what we want. Didn't know about that!

Copy link
Member

Choose a reason for hiding this comment

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

As always, please add a comment about the purpose of the linkName attribute. Otherwise these things tend to stay around forever even after nobody uses them anymore because nobody knows what it was good for.

@jbaum98 jbaum98 force-pushed the fflas-ffpack_darwin branch 2 times, most recently from 35c2860 to fbf012f Compare August 17, 2018 02:21
# see https://github.com/NixOS/nixpkgs/pull/45013.
# We need to pass a different name to --with-blas-libs
# based on which one we use.
blas = let addLinkName = { pkg, linkName }:
Copy link
Member

Choose a reason for hiding this comment

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

You can just add it directly to the openblas and blas packages. passthru won't cause a rebuild.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ohh you're saying I should modify them to add the passthru attribute in all-packages.nix.

configureFlags = [
"--with-blas-libs=-lopenblas"
"--with-lapack-libs=-lopenblas"
"--with-blas-libs=-l${blas.passthru.linkName}"
Copy link
Member

Choose a reason for hiding this comment

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

Not 100% sure on this but you should be able to just do blas.linkName.

Copy link
Member

Choose a reason for hiding this comment

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

Indeed

@jbaum98 jbaum98 force-pushed the fflas-ffpack_darwin branch 2 times, most recently from f9a15b2 to 55c4572 Compare August 17, 2018 19:13
# elsewhere.
# See see https://github.com/NixOS/nixpkgs/pull/45013.
blas = (callPackage ../development/libraries/science/math/blas { })
.overrideAttrs(oldAttrs: { passthru.linkName = "blas"; });
Copy link
Member

@LnL7 LnL7 Aug 18, 2018

Choose a reason for hiding this comment

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

I think I didn't explain this properly, there's no need for overrides in all-packages.nix. Add the overrides eg. here, similar to meta this won't cause a rebuild when changed. https://github.com/NixOS/nixpkgs/blob/55c4572dd1fae7043b1697116007d0f35edbcb64/pkgs/development/libraries/science/math/blas/default.nix#L55

Copy link
Member

Choose a reason for hiding this comment

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

So you can directly add this to pkgs/development/libraries/sciene/math/{open,}blas/default.nix.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah sorry, makes sense now.

@jbaum98 jbaum98 force-pushed the fflas-ffpack_darwin branch 3 times, most recently from 57acd20 to 5d958cc Compare August 18, 2018 20:27
"--with-blas-libs=-lopenblas"
"--with-lapack-libs=-lopenblas"
"--with-blas-libs=-l${blas.linkName}"
"--with-lapack-libs=-l${blas.linkName}"
] ++ stdenv.lib.optionals (!optimize) [
# disable SIMD instructions (which are enabled *when available* by default)
"--disable-sse"
Copy link
Member

Choose a reason for hiding this comment

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

Why did you remove those?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

What do you mean?

Copy link
Member

Choose a reason for hiding this comment

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

Never mind, I must've mis-read the github diff. I thought you removed a bunch of --disable-X.

@timokau
Copy link
Member

timokau commented Aug 19, 2018

As soon as you think this is ready, please remove the wip tag.

Copy link
Member

@LnL7 LnL7 left a comment

Choose a reason for hiding this comment

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

Looks good now.

@jbaum98 jbaum98 changed the title [WIP] fflas-ffpack: Add darwin support fflas-ffpack: Add darwin support Aug 19, 2018
@timokau
Copy link
Member

timokau commented Aug 19, 2018

@GrahamcOfBorg build fflas-ffpack

@GrahamcOfBorg
Copy link

Success on x86_64-linux (full log)

Attempted: fflas-ffpack

Partial log (click to expand)

 /nix/store/llyw6zn8bhwj6zw6lzdlxyd25bk0bwn1-coreutils-8.29/bin/install -c -m 644 fflas-ffpack.pc '/nix/store/346mlds1v2kbg04xz3xgy86yklcxkdfj-fflas-ffpack-2.3.2/lib/pkgconfig'
make[2]: Leaving directory '/build/source'
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/346mlds1v2kbg04xz3xgy86yklcxkdfj-fflas-ffpack-2.3.2
strip is /nix/store/553rihc190vsyy8b22iqcq25a6489h8y-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/346mlds1v2kbg04xz3xgy86yklcxkdfj-fflas-ffpack-2.3.2/lib  /nix/store/346mlds1v2kbg04xz3xgy86yklcxkdfj-fflas-ffpack-2.3.2/bin
patching script interpreter paths in /nix/store/346mlds1v2kbg04xz3xgy86yklcxkdfj-fflas-ffpack-2.3.2
/nix/store/346mlds1v2kbg04xz3xgy86yklcxkdfj-fflas-ffpack-2.3.2/bin/fflas-ffpack-config: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/79b6s2wql94lwk8dyib2jc4fq8ixl13f-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/346mlds1v2kbg04xz3xgy86yklcxkdfj-fflas-ffpack-2.3.2...

@GrahamcOfBorg
Copy link

Success on aarch64-linux (full log)

Attempted: fflas-ffpack

Partial log (click to expand)

make[2]: Leaving directory '/build/source'
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/idipsnnd3pzyhblfczayhr8dnn0ab5ia-fflas-ffpack-2.3.2
strip is /nix/store/4md2i310zklkkl5j41yw70gcwgn4kav5-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/idipsnnd3pzyhblfczayhr8dnn0ab5ia-fflas-ffpack-2.3.2/lib  /nix/store/idipsnnd3pzyhblfczayhr8dnn0ab5ia-fflas-ffpack-2.3.2/bin
patching script interpreter paths in /nix/store/idipsnnd3pzyhblfczayhr8dnn0ab5ia-fflas-ffpack-2.3.2
/nix/store/idipsnnd3pzyhblfczayhr8dnn0ab5ia-fflas-ffpack-2.3.2/bin/fflas-ffpack-config: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/x8npv3gr1rq1pf6gqpcdb9b68374pfd6-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/idipsnnd3pzyhblfczayhr8dnn0ab5ia-fflas-ffpack-2.3.2...
/nix/store/idipsnnd3pzyhblfczayhr8dnn0ab5ia-fflas-ffpack-2.3.2

@GrahamcOfBorg
Copy link

Success on x86_64-darwin (full log)

Attempted: fflas-ffpack

Partial log (click to expand)

 /nix/store/vc4q7zqpxx15ckxshdxikf7c6vq57c5k-coreutils-8.29/bin/install -c fflas-ffpack-config '/nix/store/7ja9ld59gji077yqfjzzksh4y75icmzl-fflas-ffpack-2.3.2/bin'
 /nix/store/vc4q7zqpxx15ckxshdxikf7c6vq57c5k-coreutils-8.29/bin/mkdir -p '/nix/store/7ja9ld59gji077yqfjzzksh4y75icmzl-fflas-ffpack-2.3.2/lib/pkgconfig'
 /nix/store/vc4q7zqpxx15ckxshdxikf7c6vq57c5k-coreutils-8.29/bin/install -c -m 644 fflas-ffpack.pc '/nix/store/7ja9ld59gji077yqfjzzksh4y75icmzl-fflas-ffpack-2.3.2/lib/pkgconfig'
make[2]: Leaving directory '/private/tmp/nix-build-fflas-ffpack-2.3.2.drv-0/source'
make[1]: Leaving directory '/private/tmp/nix-build-fflas-ffpack-2.3.2.drv-0/source'
post-installation fixup
strip is /nix/store/bg39mxc401qqxgjasxfgardi6xl2ikmc-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/7ja9ld59gji077yqfjzzksh4y75icmzl-fflas-ffpack-2.3.2/lib  /nix/store/7ja9ld59gji077yqfjzzksh4y75icmzl-fflas-ffpack-2.3.2/bin
patching script interpreter paths in /nix/store/7ja9ld59gji077yqfjzzksh4y75icmzl-fflas-ffpack-2.3.2
/nix/store/7ja9ld59gji077yqfjzzksh4y75icmzl-fflas-ffpack-2.3.2/bin/fflas-ffpack-config: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/avxlkpsr36xpnsy0byq2c4vxk6sw157a-bash-4.4-p23/bin/bash"

@timokau
Copy link
Member

timokau commented Aug 19, 2018

Thank you for your persistence!

@timokau timokau merged commit 8014c7f into NixOS:master Aug 19, 2018
@timokau
Copy link
Member

timokau commented Aug 25, 2018

I've reported this issue at sage upstream, maybe somebody there can help: https://trac.sagemath.org/ticket/26130

@multun multun mentioned this pull request Jan 2, 2020
10 tasks
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