Package Details: fsl 6.0.4-2

Git Clone URL: (read-only, click to copy)
Package Base: fsl
Description: A comprehensive library of analysis tools for FMRI, MRI and DTI brain imaging data
Upstream URL:
Licenses: custom
Submitter: fishburn
Maintainer: tobac
Last Packager: tobac
Votes: 11
Popularity: 0.049444
First Submitted: 2012-07-02 23:36
Last Updated: 2020-08-26 10:02

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

tobac commented on 2019-10-02 10:53

To test it again, I set up a fresh Arch VM, installed only openssh, vim and yay and did "yay -S fsl". It worked as expected.

tobac commented on 2019-10-02 08:53

I tested it on three different machines, no errors there. Could you at least tell me yours?

maciex commented on 2019-09-30 22:15

build has an error

tobac commented on 2019-09-30 11:21

@wangqr: Could you try 6.0.2? They changed some things with regard to their build system (it still needs manual adapting, but in a somewhat less complicated manner).

wangqr commented on 2019-04-13 06:10

Turns out that the error is caused by uninstantiated template function read_volumeROI (see line 4841 of the log). This can be fixed by the following patch:

After fixing this issue, there are still 4 components that fails to build, namely fslsurface, film, ptx2, and MSM. The latter 2 depends on fslsurface. fslsurface fails due to corrupted .o file (not sure why this happens). film fails due to missing header QPBO/QPBO.hpp

wangqr commented on 2019-04-12 20:35

The build fails for me. Full build.log at

It seems that the errors are caused by missing headers. According to the command line options (See line 4868 of the log), the compiler is looking for headers in $HOME/fsldev, which does not exist.

Anonymous comment on 2019-03-26 20:39

Thanks, I tried reinstalling fslpy and to run the test suite manually from the executable. Nonetheless the same output came out without any new information about the problem.

I think the issue might be a problem in the building itself. I will try to read through the build.log.

martin3141 commented on 2019-03-26 16:31

I ran the test suite manually and a more useful Python error came up. There should be an executable called RUN in the src/feeds directory. A couple of environment variables need setting up (which is fiddly), but you can find the required steps in the check() section of the PKGBUILD file.

I'd also try updating and reinstalling the fslpy package if you haven't done that already.

Anonymous comment on 2019-03-26 16:24

@martin3141 I'm having the same error with check() that you reported. It is the exact same output. I tried your solution of reinstalling the python-deprecation package, but the failure keeps occurring. How did you realize which package was missing from your system?

tobac commented on 2019-03-23 17:34

I'm glad it's working for you now. Thanks for mentioning the fslpy dependencies issue, I sadly failed to notice AKSoo's comment.