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 9 10 .. 15 Next › Last »
tobac commented on 2020-07-19 07:51 (UTC)
Or just write me an email and I'll provide you with a binary Arch package :)
adkipnis commented on 2020-07-18 19:36 (UTC) (edited on 2020-07-18 19:57 (UTC) by adkipnis)
If you NEED to use fsl on your Arch install but cannot build it from source: I have dual booted Ubuntu with Arch and installed fsl there instead, then copied the contents of
/opt/fsl
to Arch, edited.bashrc
to includeand source
.bashrc
(cf. the FSL wiki on the general setup procedure).Had to additionally edit
/opt/fsl/tcl/fslstart.tcl
to change the lineset HOSTNAME "the-hostname-of-my-arch-install"
.And now fsl seems to run properly. Will give updates if I encounter bugs.
Feakster commented on 2020-06-05 11:09 (UTC)
With the newer version of GCC, I still can't successfully build the package. However, this time the errors start a bit sooner in the build process on line 3358 of the build.log, in the section for building the
meshclass
project. Output below:Feakster commented on 2020-03-06 20:49 (UTC) (edited on 2020-03-06 20:50 (UTC) by Feakster)
Not sure whether it helps or not, but the errors seem to start at around line 3999 in my build.log, in the section for building
fslsurface
. All other errors seem to propagate downstream from the resulting missingfslsurface/fslsurfaceio.h
file. The relevant section of output is below:tobac commented on 2020-02-24 10:23 (UTC)
The thing is, my initial efforts to reproduce this (apparently quite common) error were unsuccessful. I hope I can work on it later this week.
Anyway, if you contact me by e-mail (see PKGBUILD), we can usually find a solution on a one-by-one basis.
Fjalar commented on 2020-02-24 09:55 (UTC)
Got the exact same error as Feakster and jpeter, have provided build.log
tobac commented on 2020-01-08 10:24 (UTC)
@jpeter Sure. You can find a valid address in the PKGBUILD file.
jpeter commented on 2020-01-08 10:20 (UTC)
@tobac The build.log is very large. Email?
tobac commented on 2020-01-08 10:08 (UTC)
@jpeter Fair enough, but I still don't have a build.log :). Feakster didn't get back to me. Could you email/pastebin me yours?
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 15 Next › Last »