Try this:
FSLDIR=/Users/xuelin/fsl
. ${FSLDIR}/etc/fslconf/fsl.sh
PATH=${FSLDIR}/bin:${PATH}
export FSLDIR PATH
export DISPLAY=localhost:0.0
-Ravi
On Thu, 26 Jul 2007 17:11:13 -1000, Xuelin Cui <[log in to unmask]> wrote:
>Yes, I exit the terminal and relaunch it everytime after I modified my .bashrc file. But still, it
didn't work. I type fsl in X terminal to launch FSL, but failed.
>
>I could echo $FSLDIR, but I failed to echo $FSLCONFDIR and $PATH, I dont figure it out so far
>
>Xuelin
>
>----- Original Message -----
>From: Ravi Shetty <[log in to unmask]>
>Date: Thursday, July 26, 2007 4:50 pm
>Subject: Re: [FSL] FSL on Mac
>To: [log in to unmask]
>
>> Have you tried exiting the terminal and opening up a new one? Also
>> since you are on a Mac you
>> will need to type the fsl command in an X windows terminal. If you
>> type fsl in a normal terminal
>> window you will get something to this effect:
>>
>> Application initialization failed: couldn't connect to display
>> "localhost:0.0"Error in startup script: couldn't connect to display
>> "localhost:0.0"
>> Hope that helps.
>>
>> -Ravi
>>
>>
>>
>> On Thu, 26 Jul 2007 15:45:58 -1000, Xuelin Cui <[log in to unmask]>
>> wrote:
>> >hi All:
>> >
>> >My computer is a Mac G5. And I downloaded FSL for Mac G5, 3.3.11.
>> I unzipped the FSL package,
>> and tried to setup the environment variable.
>> >
>> >I followed every step on FSL website. I copied the online script
>> into both .bash_profile
>> and .bashrc file, and following are my exact script:
>> >
>> >export FSLDIR=/Users/xuelin/fsl
>> >. ${FSLDIR}/etc/fslconf/fsl.sh
>> >PATH=${FSLDIR}/bin:${PATH}
>> >export FSLDIR PATH
>> >export DISPLAY=localhost:0.0
>> >
>> >where /Users/xuelin/fsl is the location where I installed my FSL,
>> and I am sure it is correct. When
>> I echo $FSLDIR, the console reflects the correct value, which is:
>> /Users/xuelin/fsl. But when I type
>> "fsl" in console, it shows: bash: fsl: command not found
>> >.
>> >I dont know how I should modified the .bash_profile/.bashrc file
>> to make FSL work. Or this is due
>> to other reasons? Does anyone have same problemm before?
>> >
>> >Thanks a lot
>> >
>> >Xuelin
>>
