public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: zack@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: Remaining host configuration fragments
Date: Mon, 14 Jan 2002 14:59:00 -0000	[thread overview]
Message-ID: <200201142149.g0ELnsr14067@greed.delorie.com> (raw)
In-Reply-To: <20020114213729.GG13101@codesourcery.com> (message from Zack Weinberg on Mon, 14 Jan 2002 13:37:29 -0800)


> In that case I wonder if it's appropriate to declare
> HAVE_DOS_BASED_FILE_SYSTEM at all under cygwin.  GCC currently does
> think it can get a drive letter in a pathname fed to it under
> cygwin...

Cygwin will automagically alter $PATH (and a few others) to have
posix-compliant unix-like paths, with ':' separators.  This is
transparent to the application.

However, you can pass DOS paths to gcc *as parameters* like this:

	C:\DOS> gcc c:\foo\bar.c

Cygwin will not change those for you.

So, colons in filenames are OK but colons in $PATH are separators.

  reply	other threads:[~2002-01-14 21:50 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10 14:26 Zack Weinberg
2002-01-10 15:25 ` DJ Delorie
2002-01-13 17:38   ` Zack Weinberg
2002-01-13 20:15     ` Christopher Faylor
2002-01-14 14:11       ` Zack Weinberg
2002-01-14 14:59         ` DJ Delorie [this message]
2002-01-14 11:11     ` DJ Delorie
2002-01-16  1:17     ` Mark Mitchell
2002-01-16  2:06       ` Eric Christopher
2002-01-16  5:38         ` Gerald Pfeifer
2002-01-16  8:04         ` Paul Koning
2002-01-16 12:40           ` Eric Christopher
2002-01-16  7:23       ` Joseph S. Myers
2002-01-16  8:41       ` DJ Delorie
2002-01-16  9:52         ` Joseph S. Myers
2002-01-16 11:42           ` DJ Delorie
2002-01-16 11:56             ` Joseph S. Myers
2002-01-16 12:18               ` DJ Delorie
2002-01-16 12:45                 ` Joseph S. Myers
2002-01-16 13:08                 ` Zack Weinberg
2002-01-16 13:15                   ` DJ Delorie
2002-01-16 13:20                     ` Joseph S. Myers
2002-01-17  3:03                     ` Eric Christopher
2002-01-17  7:34                       ` Rainer Orth
2002-01-16 12:13             ` Joe Buck
2002-01-16 13:56       ` Zack Weinberg
2002-01-16 14:17         ` DJ Delorie
2002-01-16 14:23         ` Robert Lipe
2002-01-16 22:12           ` Tim Prince
2002-01-16 14:27         ` Paul Koning
2002-01-16 14:48         ` Joseph S. Myers
2002-01-16 15:18           ` Jason R Thorpe
2002-01-22 11:37           ` Lars Brinkhoff
2002-01-22 13:18             ` Paul Koning
2002-01-22 14:10               ` Joseph S. Myers
2002-01-22 15:02               ` law
2002-01-16 19:08         ` Joe Buck
2002-01-16 15:27       ` Stan Shebs
2002-01-17 16:54         ` Toon Moene
2002-01-16  7:36 Bernard Dautrevaux
2002-01-16  8:46 ` DJ Delorie
2002-01-16 19:20 mike stump
2002-01-16 20:02 ` Jason R Thorpe
2002-01-17  3:01   ` Joseph S. Myers
2002-01-16 21:31 ` DJ Delorie
2002-01-17  8:08   ` Alexandre Oliva
2002-01-17  9:34     ` DJ Delorie
2002-01-17 10:13   ` Paul Koning
2002-01-16 20:23 mike stump
2002-01-17  5:24 ` Eric Christopher
2002-01-17 10:49 ` Geoff Keating
2002-01-16 21:00 mike stump
2002-01-17  7:26 Richard Kenner
2002-01-17  7:33 Richard Kenner
2002-01-17  8:04 ` DJ Delorie
2002-01-17 11:53   ` Phil Blundell
2002-01-17 12:29 ` Joe Buck
2002-01-17 14:25   ` Stan Shebs
2002-01-17 14:31     ` Joseph S. Myers
2002-01-17 15:01     ` Joe Buck
2002-01-17 16:58       ` DJ Delorie
2002-01-18  2:01         ` Stan Shebs
2002-01-18 11:27           ` Paul Koning
2002-01-22 13:06 Richard Kenner
2002-01-22 15:28 ` Joe Buck
2002-01-23  5:56 ` Lars Brinkhoff

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=200201142149.g0ELnsr14067@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=zack@codesourcery.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).