X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 7 Jan 2009 15:31:32 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: tcsh problems with Cygwin on 64-bit Windows Server 2008 Message-ID: <20090107143132.GD19133@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <090105115048 DOT ZM835 AT adobe DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <090105115048.ZM835@adobe.com> User-Agent: Mutt/1.5.17 (2007-11-01) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Jan 5 11:50, Freddy Jensen wrote: > > I just finished setting up my new 64-bit Windows Server 2008 machine. > One of the final things was to install cygwin on the machine so I > could get all the Unix functionality. However, I ran into a problem > when launching the tcsh shell. I got this error: > > "Badly placed ()'s", and the shell stopped reading the startup file. > > I have tracked this down to one element of the PATH environment variables, > namely this one: /cygdrive/c/Program Files ( x86 ) /Microsoft ...." > > What happens is that on 64 bit WinServ-2008 the installers for various > programs put native 64-bit applications into C:\Program Files\... and > 32-bit applications into C:\Program Files ( x86 ) \... and the installers > then add the path into the environment variables for the user. > > When you start a CMD window then the DOS command inherits all the env > vars, including the PATH variable and then when you launch the tcsh > it first reads this file: > > /etc/profile.d/lapack.csh > > Inside that file there is a loop that evaluates each > path element and it finally chokes on > > "/cygdrive/c/Program Files ( x86 ) /Microsoft ...." > > because the parens have special meaning to tcsh unless > they are escaped. In my opinion it is a bug in cygwin's > /etc/profile.d/lapack.csh profile script. This is a problem of the lapack package. Unfortunately the lapack package is orphaned and nobody volunteered to be the new package maintainer so far. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/