***  For details on how to be removed from this list visit the  ***
***          CCP4 home page http://www.ccp4.ac.uk         ***


Hi Christian

I got CCP4 working by commenting out that line (putting a # before the
statement) 

Have not gotten around to finding a way increase the stacksize yet.

Good Luck 

TC 



> From: Christian Benda <[EMAIL PROTECTED]>
> Date: Thu, 4 May 2006 23:22:05 +0200
> To: <[email protected]>
> Conversation: ccp4 on intel-mac setup problem (limit stacksize)
> Subject: [ccp4bb]: ccp4 on intel-mac setup problem (limit stacksize)
> 
> ***  For details on how to be removed from this list visit the  ***
> ***          CCP4 home page http://www.ccp4.ac.uk         ***
> 
> 
> Dear All:
> 
> I have fink-installed and compiled cpp4-6.0 on an intel mac under my user
> account (administrator). Now I am stuck with a banality (hopefully) which I
> seem to be unable to resolve:
> 
> In order to get everything setup correctly (paths etc.) the file
> /sw/bin/init.csh has to be sourced from the .cshrc file. After adding 'source
> /sw/bin/init.csh' to my .cshrc file I get the following error message in every
> new shell:
> 
>  limit: stacksize: Can't set limit (Operation not permitted)
> 
> As one consequence, the PATH variable is not modified correctly.
> The 'set limit' command is issued from whithin the ccp4.setup script (limit
> stacksize 65536) which - in turn - is called from init.csh. What seems to be a
> permission conflict works alright when I source init.csh in a shell as root. I
> tried to source init.csh from the system-wide csh.cshrc in /etc but that
> doesn't help either (no error message, but no paths etc. either).
> 
> The current limit for stacksize is 8164 kbytes
> 
> Has any one else had this problem and? Any hint is highly appreciated!
> 
> Many thanks in advance,
> 
> Christian
> 
> __________________________________________________
> Max-Planck-Institute for Biochemistry
> Structural Cell Biology
> 8252 Martinsried
> Germany
> 
> Phone: +49 (0)89 8578-2337
> Email: [EMAIL PROTECTED]
> 
> 
> 


Reply via email to