X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Message-ID: <723394.43466.qm@web25002.mail.ukl.yahoo.com>
Date: Fri, 3 Apr 2009 12:51:53 +0000 (GMT)
From: Marco Atzeri <marco_atzeri AT yahoo DOT it>
Subject: Re: compilation with cygport spoiled by spaces in pathnames?
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com




--- Ven 3/4/09, Charles Wilson  ha scritto:

> Da: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
> Oggetto: Re: compilation with cygport spoiled by spaces in pathnames?
> A: cygwin AT cygwin DOT com
> Data: Venerd=EC 3 Aprile 2009, 14:38
> Thomas Wolff wrote:
>=20
> > Is this a generic problem? From the make output, it's
> not clear which program=20
> > actually raised the problem ("Can't find c:\Program on
> PATH.") - gcc, mv, rm?
> > I had the impression that spaces in path names (which
> unfortunately do occur=20
> > under Windows) are usually handled properly.
>=20
> No, spaces are NOT usually handled "properly" in the way
> you mean.
>=20
> OTOH, they ARE handled "properly" if by "properly" you mean
> "treated as
> separators between words". This is just ONE of the reasons
> why EVERYBODY
> and their sister says "Spaces are DUMB. You're just asking
> for trouble.
> Don't do it if you want to use cmdline tools -- like
> cygwin"
>=20
> I'm sorry to say that mixing spaces into Cygwin paths is
> never going to
> work smoothly; there are just too many unix-derived
> entities that rely
> on the spaces-separate-words behavior.=A0 To change them
> all would
> be...more trouble than it is worth.=A0 And there's
> already a workaound:
> mount any external paths that embed spaces:
>=20
> mount [options] C:/Programs\ Files /program_files
>=20
> --
> Chuck

other workaround, define a PATH for cygwin=20
without space in names

in my .bash_profile I put=20

PATH=3D${HOME}/bin:/usr/local/bin:/bin:/usr/lib/lapack:/cygdrive/c/WINDOWS/=
system32:/cygdrive/c/WINDOWS

to clean and remove all redundant directories

Marco

=20




--
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/