From: Karl M <karlm30@hotmail.com>
To: <cygwin@cygwin.com>
Subject: RE: Coreutils' Build Fails After Linking rm.exe
Date: Tue, 15 Feb 2011 19:52:00 -0000 [thread overview]
Message-ID: <COL102-W613AD78E9D70BA039BCA45B5D30@phx.gbl> (raw)
In-Reply-To: <4D5A9978.3020903@redhat.com>
> Date: Tue, 15 Feb 2011 08:19:20 -0700
> From: eblake
> Subject: Re: Coreutils' Build Fails After Linking rm.exe
>
> Hmm. Does your $PATH include '.' somewhere near the beginning? That
> may be the culprit; I _never_ run with '.' at the beginning (too much
> risk of a trojan horse executable taking over); running with '.' at the
> end or not in PATH at all would be safer.
>
Just for the archive, a dot in $PATH can be caused by a double ; in the windows
path. A ";;" in the windows path creates a null entry that gets interpreted
as a ".".
--
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:[~2011-02-15 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 7:58 L Anderson
2011-02-15 15:19 ` Eric Blake
2011-02-15 15:33 ` L Anderson
2011-02-15 19:52 ` Karl M [this message]
2011-02-15 15:26 ` Coreutils' Build Fails After Linking rm.exe--Solved L Anderson
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=COL102-W613AD78E9D70BA039BCA45B5D30@phx.gbl \
--to=karlm30@hotmail.com \
--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).