Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 15 May 2001 21:37:16 -0400 From: Christopher Faylor To: cygwin@cygwin.com Cc: mrs@windriver.com Subject: Re: 1.1.8: bug in \\ handling in absolute fns Message-ID: <20010515213716.B8966@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com, mrs@windriver.com References: <200105160000.RAA19521@kankakee.wrs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <200105160000.RAA19521@kankakee.wrs.com>; from mrs@windriver.com on Tue, May 15, 2001 at 05:00:13PM -0700 On Tue, May 15, 2001 at 05:00:13PM -0700, Mike Stump wrote: >I have found that when I do: > >mkdir /x >touch /x/y # ok >touch /x\\z # fails >touch d:/cygwin/x\\z # ok >cd /x >touch z # ok >touch ./z # ok >touch .\\z # ok > >I get the results as mentioned. This causes a newer gcc to fail to >work, as libiberty uses \ to separate names in my toolchain, and TEMP >is set by cygwin to /cygdrive/c/TEMP. And this combination doesn't >work, as mentioned above. This worked in B19. While libiberty could >be made to not do this, or to canonicalize the pathnames, I feel that >this is the wrong approach. If libiberty is using backslashed filenames under Cygwin, that's a bug. Do you know what particular function is incorrectly using backslashes? Our customers requested that backslashes in filenames be treated as native MS-DOS paths and so that change was incorporated into cygwin last year. So, I'm not surprised that a hybrid usage like /a\b would fail. That would be translated to x:\a\b on the current drive. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple