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 13:42:54 +0300 Message-ID: <83h8wcw3td.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> <83tw0cwcle.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1504953836 9723 195.159.176.226 (9 Sep 2017 10:43:56 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 9 Sep 2017 10:43:56 +0000 (UTC) Cc: 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 12:43:51 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 1dqdET-00013U-G5 for ged-emacs-devel@m.gmane.org; Sat, 09 Sep 2017 12:43:25 +0200 Original-Received: from localhost ([::1]:48947 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqdEa-0002j3-Q4 for ged-emacs-devel@m.gmane.org; Sat, 09 Sep 2017 06:43:32 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43712) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqdDy-0002ir-D2 for emacs-devel@gnu.org; Sat, 09 Sep 2017 06:42:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dqdDv-00075o-AQ for emacs-devel@gnu.org; Sat, 09 Sep 2017 06:42:54 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:34657) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqdDv-00075e-78; Sat, 09 Sep 2017 06:42:51 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1287 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dqdDt-0001CV-W1; Sat, 09 Sep 2017 06:42:51 -0400 In-reply-to: (message from Richard Copley on Sat, 9 Sep 2017 10:36: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:218054 Archived-At: > From: Richard Copley > Date: Sat, 9 Sep 2017 10:36:28 +0100 > Cc: Angelo Graziosi , Emacs Development > > >> That conversion happens often, e.g., in normalize_filename. > > > > What conversion is that? > > The down-casing of the drive letter in a native or MSYS file name. But find-file-noselect insists on comparing file names as simple case-sensitive strings. Which will fail in a few more interesting cases. > > For starters, can you or Angelo tell where did that upper-case "C:/" > > originate from? > > You can see the warnings, for example, by invoking configure by > absolute file name with an upper-case drive letter before running make. > > Usually one uses a relative path and the problem can't arise. > > I used to see this when I used a complicated Perl script to build > Emacs. The upper-case drive letter was just an artifact. It was > derived from the current directory of the calling command prompt. So you are saying that upper-case C:/ comes from the user? And if the user configures Emacs with a lower-case c:/, the problem will never happen? If so, would binding find-file-suppress-same-file-warnings non-nil in autoload-find-generated-file solve the problem? (This is less drastic than invoking find-file-noselect with a non-nil 2nd argument.) > > Also, are there other places in the build process > > that display file names with the upper-case drive letter? > > Yes. Transcript attached. I see a lot of warnings in that log. It's a pity no one reports them, let alone works on fixing them. (I don't see any of them on my systems.) Thanks.