From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Suspicious warning in W64 build Date: Sat, 09 Sep 2017 10:37:39 +0300 Message-ID: <83shfwwce4.fsf@gnu.org> References: <1017454172.910810.1504618695244@mail.libero.it> <83tw0ezgi1.fsf@gnu.org> <1146932094.13821.1504798935795@mail.libero.it> <83mv66z66p.fsf@gnu.org> <102a4c21-c275-c73e-ec53-0d85975dc968@cs.ucla.edu> <83a825znuf.fsf@gnu.org> <831snhzkgw.fsf@gnu.org> <837ex9x7vf.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1504942673 23640 195.159.176.226 (9 Sep 2017 07:37:53 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 9 Sep 2017 07:37:53 +0000 (UTC) Cc: eggert@cs.ucla.edu, angelo.g0@libero.it, emacs-devel@gnu.org To: Richard Copley Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Sep 09 09:37:48 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dqaKd-0005Dx-1O for ged-emacs-devel@m.gmane.org; Sat, 09 Sep 2017 09:37:35 +0200 Original-Received: from localhost ([::1]:48540 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqaKi-0003pd-M0 for ged-emacs-devel@m.gmane.org; Sat, 09 Sep 2017 03:37:40 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:32791) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqaKc-0003pX-Pa for emacs-devel@gnu.org; Sat, 09 Sep 2017 03:37:35 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dqaKZ-0004A5-NV for emacs-devel@gnu.org; Sat, 09 Sep 2017 03:37:34 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:59968) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqaKZ-00049v-Jo; Sat, 09 Sep 2017 03:37:31 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4711 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dqaKY-0008W7-Sx; Sat, 09 Sep 2017 03:37:31 -0400 In-reply-to: (message from Richard Copley on Fri, 8 Sep 2017 22:37:28 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:218044 Archived-At: > From: Richard Copley > Date: Fri, 8 Sep 2017 22:37:28 +0100 > Cc: Paul Eggert , Angelo Graziosi , > Emacs Development > > As a short-cut/side-step, could we normalize one or both filenames > explicitly, somewhere nearer to the call site (perhaps for w32 only)? Once again, this could be the right solution, but we can only decide that when we understand the problem a bit better. > But I don't know if there's a lisp function for that. Almost all of the functions that work with file names do that, AFAIK. Which is why I don't yet see how this file name with an upper-case drive letter came into existence. It must have originated somewhere, most probably in user-space. Let's find that out before we decide on the right course of action.