From: Aaron Schneider <notstop@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: Cygwin fresh install imports Windows PATH which includes spaces causing errors
Date: Tue, 24 Jul 2012 15:58:00 -0000 [thread overview]
Message-ID: <BLU0-SMTP184CD1D0A81E3DA2FFD5908CEDC0@phx.gbl> (raw)
In-Reply-To: <20120724155038.GD5572@ednor.casa.cgf.cx>
On 24/07/2012 17:50, Christopher Faylor wrote:
>
> The Cygwin version of make would not display "c:" anything. That's not
> a Cygwin path specification and it shouldn't even be possible for a
> Cygwin program to see the Windows PATH environment variable. You must
> be running a non-cygwin make. Spaces in the PATH are acceptable on both
> Linux and Cygwin and Windows.
>
> That said, however, make does not deal well with spaces in file
> specifications. If something is actually parsing a PATH environment
> variable then it could cause problems.
>
> cgf
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
It was actually that make wasn't installed, it works now. I was
expecting the usual "bash: make: command not found"
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-07-24 15:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 15:32 Aaron Schneider
2012-07-24 15:51 ` Christopher Faylor
2012-07-24 15:58 ` Aaron Schneider [this message]
2012-07-24 16:08 ` Christopher Faylor
2012-07-24 20:35 ` Aaron Schneider
2012-07-25 0:48 ` Andrew DeFaria
2012-07-25 1:10 ` Aaron Schneider
2012-07-25 2:00 ` Andrew DeFaria
2012-07-25 2:25 ` Aaron Schneider
2012-07-25 3:41 ` Andrew DeFaria
2012-07-25 13:34 ` Thrall, Bryan
2012-07-25 13:50 ` Aaron Schneider
2012-07-25 14:57 ` Earnie Boyd
2012-07-25 18:12 ` Aaron Schneider
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BLU0-SMTP184CD1D0A81E3DA2FFD5908CEDC0@phx.gbl \
--to=notstop@users.sourceforge.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).