From: "Andy Hare" <ahare@btinternet.com>
To: "Sourceware Mail List" <cygwin@sourceware.cygnus.com>
Cc: "Chris Faylor cygnus-cygwin" <cgf@cygnus.com>
Subject: Re: File name syntax (WAS: RE: FW: Can not config sshd)
Date: Mon, 29 May 2000 10:28:00 -0000 [thread overview]
Message-ID: <116501bfc993$6855eb60$0100000a@dualbeast> (raw)
In-Reply-To: <20000528121433.A1363@cygnus.com>
Chris,
I too have suffered the problems with make failing when a // is used in
the path. However my problem was due to mounting another drive on the root
file system and using the file://e/ as the descriptor. The make process
would
fail. I have not tried using e: as the descriptor as I figured that e: was
not the Unix way to describe the disk. The make file was called with the
mount path but this was translated into the file://e name ether by make or
by
bash calling make. Either way it caused make a headache. Make would stop
retreating out of sub-directories and would eventually fail.
I was actually trying to get the temporary build directory onto an empty
disk away from the root disk to give me more space. This was under b20.1 as
I haven't had the nerve to move to the latest net release yet. Waiting for
all the fuss to die down before I mess with a working system, I've made that
mistake before.
Andy Hare
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-05-29 10:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-28 8:14 Earnie Boyd
2000-05-28 9:14 ` Chris Faylor
2000-05-29 10:28 ` Andy Hare [this message]
[not found] <200005301721.KAA00107@cygnus.com>
2000-05-30 10:35 ` Chris Faylor
-- strict thread matches above, loose matches on Subject: below --
2000-05-30 10:21 Parker, Ron
2000-05-29 6:14 Bernard Dautrevaux
2000-05-29 6:07 Bernard Dautrevaux
2000-05-28 0:17 David Bolen
[not found] <200005262126.RAA23411@acestes-fe0.ultra.net>
2000-05-27 9:32 ` Larry Hall (RFK Partners, Inc)
2000-05-27 9:44 ` Chris Faylor
2000-05-27 10:15 ` Larry Hall (RFK Partners, Inc)
2000-05-27 17:07 ` Chris Faylor
[not found] <200005262150.OAA10858@cygnus.com>
2000-05-26 15:04 ` Chris Faylor
2000-05-27 16:27 ` AJ Reins
2000-05-26 14:51 Parker, Ron
2000-05-26 15:27 ` Bob McGowan
2000-05-26 16:00 ` Chris Faylor
2000-05-26 16:18 ` Bob McGowan
2000-05-26 16:49 ` Chris Faylor
2000-05-27 9:49 ` Larry Hall (RFK Partners, Inc)
2000-05-28 0:05 ` Robert McGowan
2000-05-28 3:51 ` Corinna Vinschen
2000-05-26 14:27 Parker, Ron
2000-05-26 14:16 Parker, Ron
[not found] <200005262110.RAA09230@acestes-fe0.ultra.net>
2000-05-26 14:15 ` Larry Hall (RFK Partners, Inc)
2000-05-26 14:42 ` Chris Faylor
2000-05-27 16:19 ` AJ Reins
2000-05-27 16:50 ` Chris Faylor
2000-05-26 14:10 Parker, Ron
[not found] <200005261702.KAA22136@athena.veritas.com>
2000-05-26 10:21 ` Bob McGowan
2000-05-26 10:47 ` Larry Hall (RFK Partners, Inc)
2000-05-26 10:19 Earnie Boyd
[not found] <200005261701.NAA11863@acestes-fe0.ultra.net>
2000-05-26 10:10 ` Larry Hall (RFK Partners, Inc)
2000-05-26 10:01 Parker, Ron
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='116501bfc993$6855eb60$0100000a@dualbeast' \
--to=ahare@btinternet.com \
--cc=cgf@cygnus.com \
--cc=cygwin@sourceware.cygnus.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).