Search Criteria
Package Details: fsl 6.0.7.16-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/fsl.git (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: | http://www.fmrib.ox.ac.uk/fsl/ |
Licenses: | custom |
Submitter: | fishburn |
Maintainer: | tobac |
Last Packager: | tobac |
Votes: | 12 |
Popularity: | 0.000000 |
First Submitted: | 2012-07-02 23:36 (UTC) |
Last Updated: | 2024-12-22 17:38 (UTC) |
Required by (4)
- fsl-palm (optional)
- fsleyes (optional)
- python-nipype (optional)
- python-pyfab
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 .. 15 Next › Last »
javierbg commented on 2021-09-10 16:57 (UTC)
Reinstalling CUDA did not solve this. I tried running './build fslsurface' in the "src/fsl" directory and, surprisingly, it completed successfully. I have actually been able to build everything by copying the commands from the PKGBUILD file (NJOBS=6), but running makepkg is unsuccessful.
It is running on a laptop with an AMD Ryzen 5 4500U laptop (HP Probook x360 435 G7).
tobac commented on 2021-09-10 10:58 (UTC) (edited on 2021-09-10 11:01 (UTC) by tobac)
So it's the same error? Does reinstalling CUDA solve this? Could you try to cd into "/home/javier/Descargas/fsl/src/fsl" and run './build fslsurface'? And what CPU do you run this on?
The thing is, I was never able to reproduce this. On all machines tested (five in total, some virtual, some bare-metal), the build process runs just fine with or without CUDA.
javierbg commented on 2021-09-10 08:56 (UTC)
I'm trying to reinstall (last time CUDA was needed and I removed it), but I get the following error while building fslsurface:
tobac commented on 2021-09-10 00:41 (UTC)
Just released 6.0.5-5 which supports current GCC versions. Also, enabling CUDA is now possible by setting an environment variable, for example by running "CUDA=1 makepkg" or "CUDA=1 paru -S fsl" or whatever command you're using. This is arguably neater and more intuitive. Setting "CUDA" to 1 in the PKGBUILD is still possible. I'm sorry if you have to laboriously rebuild now, but being able to remove gcc9 from your system is hopefully justification and incentive enough.
tobac commented on 2021-09-07 18:40 (UTC)
All right. Set CUDA=1 in the PKGBUILD to enable CUDA support and remember to install cuda-9.1 first.
tobac commented on 2021-09-05 18:35 (UTC)
That's exactly what I'm planning on doing :)
keiichiiownsu12 commented on 2021-09-05 18:25 (UTC)
Re CUDA:
Looks like fsl only supports up to version 10.1. eddy_cuda only supports version 9.1. You could add 9.1 as an optional-dependency.
tobac commented on 2021-09-05 16:28 (UTC) (edited on 2021-09-05 16:31 (UTC) by tobac)
Just pushed FSL 6.0.5. I had to include another couple of weird workarounds, but was able to streamline the build process somewhat. Compiling is now done in parallel, where the number of parallel jobs defaults to the number of CPUs as determined by nproc(1). Feel free to change the NJOBS variable to an appropriate number in the PKGBUILD file. GPU-based compilation and CUDA support is disabled for now -- couldn't get it to work, which might have something to do with the CUDA version shipped with Arch. I'm trying a few things, but didn't want to hold back with the update until then. Ideally we'll have a "enable CUDA" switch in the future for those who want/need it without having to pull an enormous package even if you don't. Enjoy.
keiichiiownsu12 commented on 2021-06-28 23:32 (UTC)
Adding to the conversation on build issues: I recently tried to build the fsl package, with CUDA installed. Build failed for fdt and ptx2...again.
Feakster commented on 2021-03-21 19:44 (UTC)
I ran into the same problem as @llamtimms on a fresh EndeavourOS install. Installing
cuda
fixed the problem for me. I agree with @quoctrl in that this is a bit irksome if you don't even own an NVIDIA card. I can't see any obvious ways to remove the dependency. Removing all the lines related to cuda from the "buildSettings.mk" file 'might' work, but I haven't tried it, & have no idea what would happen if these weren't set. This might be an upstream issue.« First ‹ Previous 1 2 3 4 5 6 7 8 .. 15 Next › Last »