Package: mricron
Version: 0.20101102.1~dfsg.1-1
Severity: normal

Relaying a user bug report that came via email (not mentioning the origin
yet as I'm waiting for approval):

> To reproduce:
> 1. go to About-Preferences and enable the drawing menus
> 2. Draw - Advanced - Brain extraction ; click 'go'
> 
> It seems the location of 'bet' is hardcoded in the app for three locations 
> (/usr/bin/bet, /usr/local/fsl/bin/bet, /usr/local/fsl/bin/bet_8UI).
> Installing FSL from neuro-repos drops it into /usr/lib/fsl/4.1/bin/bet, 
> although the location set by /etc/fsl/fsl.sh is /usr/share/fsl/4.1  
> (symlinked back to /usr/lib/fsl/4.1)
> and unfortunately, none of the three (presumably) hardcoded locations in 
> mricron is thus correct.
> 
> The ~/.mricron/mricron.ini contains a line for the location of FSLDIR, but 
> this seems not to be used, or only _after_ 'bet' (the wrapper script) is 
> found in the hardwired location, it seems the FSLDIR dir is used to hold tabs 
> on bet2, the actual extraction tool.
> So setting this location to
> FSLDIR=FSLDIR=/usr/share/fsl/4.1
> does lead to bet2 to be found.
> However, bet2 then bails out with libmeshclass.so not found.
> 
> source /etc/fsl/fsl.sh _does_ set  LD_LIBRARY_PATH=/usr/lib/fsl/4.1 but that 
> does not get picked up.
> 
> 
> To remedy or work around, i
> 
> ## FOR ADMIN
> #make the hardcoded bet found:
> mkdir /usr/local/fsl
> cd /usr/local/fsl
> ln -s /usr/share/fsl/4.1/bin
> 
> #have bet2 pick up the library
> echo "/usr/lib/fsl/4.1" > /etc/ld.so.conf.d/fsl.conf
> ldconfig
> 
> ## FOR USERS
> #edit ~/.mricron/mricron.ini to feed proper FSL location to mricron
> # change FSLDIR (under [STR]) to
> FSLDIR=FSLDIR=/usr/share/fsl/4.1
> 
> 
> At this point the extraction seems to work.
> 
> 
> I am not sure if it is only mricron (remove hardcoded line to read the FSLDIR 
> location from the mricron.ini file)
> or also FSL (not finding libs after sourcing /etc/fsl/fsl.sh)
> being in need of a change when used from the debian-repos.



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to