arrayfire-haskell
arrayfire-haskell copied to clipboard
Add .travis.yml and test target
Why not use haskell-ci (which is really good), using travis for ubuntu? Unless you can have multiple travis setups for nix and non-nix builds. We could potentially test-drive typhon here for nix
@chessai I'll check out haskell-ci tonight, bigger issue is why cabal on ubuntu doesn't respect extra-lib-dirs
and extra-include-dirs
in the cabal file after cabal configure
@chessai try passing the -v3
flag to cabal.
why is a travis build not triggering on the most recent commits?
@chessai It is working again, but you added -v3
in the wrong place.
The log shows:
/usr/bin/gcc returned ExitFailure 1 with error message:
gcc: error: /opt/arrayfire/lib: No such file or directory
I think this is because of the ld-options
field in the cabal file. I think it is best if the entire field is removed completely.
okay, configure seems to succeed now. however, hspec-discover fails.
Yes, I fixed that error on my machine by running cabal install hspec-discover
.
most recent failure seems spurious (just adding hvr-ppa)
changed cabal
to ${CABAL}
. typo
use $WITHCOMPILER
sorry, i keep forgetting that git with do weird things with '$'-prefixed strings.
Now we're seeing real errors :tada:
okay, the library is building, but running anything is failing with:
/tmp/dist-test.N8AS/dist-newstyle/build/x86_64-linux/ghc-8.8.1/arrayfire-0.1.0.0/build/libHSarrayfire-0.1.0.0-inplace.a(LAPACK.o)(.text+0x71f): error: undefined reference to 'af_pinverse'
/tmp/dist-test.N8AS/dist-newstyle/build/x86_64-linux/ghc-8.8.1/arrayfire-0.1.0.0/build/libHSarrayfire-0.1.0.0-inplace.a(Image.o)(.text+0x48a5): error: undefined reference to 'af_iterative_deconv'
/tmp/dist-test.N8AS/dist-newstyle/build/x86_64-linux/ghc-8.8.1/arrayfire-0.1.0.0/build/libHSarrayfire-0.1.0.0-inplace.a(Image.o)(.text+0x4be4): error: undefined reference to 'af_inverse_deconv'
/tmp/dist-test.N8AS/dist-newstyle/build/x86_64-linux/ghc-8.8.1/arrayfire-0.1.0.0/build/libHSarrayfire-0.1.0.0-inplace.a(LAPACK.o)(.text+0x1000): error: undefined reference to 'af_pinverse'
/tmp/dist-test.N8AS/dist-newstyle/build/x86_64-linux/ghc-8.8.1/arrayfire-0.1.0.0/build/libHSarrayfire-0.1.0.0-inplace.a(Signal.o)(.text+0x4aa): error: undefined reference to 'af_approx1_uniform'
/tmp/dist-test.N8AS/dist-newstyle/build/x86_64-linux/ghc-8.8.1/arrayfire-0.1.0.0/build/libHSarrayfire-0.1.0.0-inplace.a(Signal.o)(.text+0xa6f): error: undefined reference to 'af_approx2_uniform'
That was fixed in #17
ok, rebasing
once a build with 8.8.1 passes, i will re-add the older ghcs
It seems that #23 forgot to also remove the tests for the Ord instance.
/tmp/dist-test.Iv7D/dist-newstyle/build/x86_64-linux/ghc-8.8.1/arrayfire-0.3.0.0/t/test/build/test/test: error while loading shared libraries: libaf.so.3: cannot open shared object file: No such file or directory
Test suite test: FAIL
Test suite logged to: /tmp/dist-test.Iv7D/dist-newstyle/build/x86_64-linux/ghc-8.8.1/arrayfire-0.3.0.0/t/test/test/arrayfire-0.3.0.0-test.log
0 of 1 test suites (0 of 1 test cases) passed.
-----BEGIN CABAL OUTPUT-----
cabal: Tests failed for test:test from arrayfire-0.3.0.0.
-----END CABAL OUTPUT-----
looks like this isnt getting copied in properly
It is strange. There are two builds, pr and push, and they give different outputs:
- https://travis-ci.org/arrayfire/arrayfire-haskell/builds/608426254?utm_source=github_status&utm_medium=notification
- https://travis-ci.org/arrayfire/arrayfire-haskell/builds/608426245?utm_source=github_status&utm_medium=notification
hmm. that is strange.
do i need to remove the Ord tests from the test suite?
Yes, I think so.
now we at least see the same error on both.
Oh, I think I know how to fix this. The linux documentation of arrayfire mentions that you have to do this:
Given sudo permissions, you can add the ArrayFire libraries via ldconfig like so:
echo /opt/arrayfire/lib64 > /etc/ld.so.conf.d/arrayfire.conf sudo ldconfig
Otherwise, you will need to set the LD_LIBRARY_PATH environment variable in order to let your shared library loader find the ArrayFire libraries.
I think that is also the reason for the ld-options field in the cabal file.
So another alternative we have is putting:
ld-options: -Wl,-rpath /opt/arrayfire/lib64
back in the cabal file.
(not -Wl,-rpath /opt/arrayfire/lib
)
we could do that. would it be better instead to do export LD_LIBRARY_PATH="/opt/arrayfire/lib64:$LD_LIBRARY_PATH"
?
Yes, that would also work.
I don't know if it carries over from before-install to script, but we will see.
me either. i should probably just do it right after the arrayfire script finishes.