Massimo Marino writes: > Viktor, > > I checked the PATH and indeed you got it right. Now, shouldn't > this be taken care by init.sh ?
It should be. You can check to make sure that /sw/bin/init.sh exists and does reset the PATH. Then you should check that you don't re-reset the PATH *after* init.sh gets called in your login sequence... (and check to make sure that you're in fact sourcing /sw/bin/init.sh correctly in your login sequence)... > On Thursday, November 21, 2002, at 10:52 PM, Viktor Haag wrote: [snip] > > It seems to me that the most likely cause of your problem is > > having /usr/bin before /sw/bin in your path... ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
