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:33:17 +0300 Message-ID: <83tw0cwcle.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 1504942445 14986 195.159.176.226 (9 Sep 2017 07:34:05 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 9 Sep 2017 07:34:05 +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 09:33:58 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 1dqaGv-0002om-S3 for ged-emacs-devel@m.gmane.org; Sat, 09 Sep 2017 09:33:46 +0200 Original-Received: from localhost ([::1]:48531 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqaH1-0002nv-6X for ged-emacs-devel@m.gmane.org; Sat, 09 Sep 2017 03:33:51 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60356) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqaGP-0002nX-La for emacs-devel@gnu.org; Sat, 09 Sep 2017 03:33:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dqaGM-0001bn-Ca for emacs-devel@gnu.org; Sat, 09 Sep 2017 03:33:13 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:59930) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqaGM-0001bj-8z; Sat, 09 Sep 2017 03:33:10 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4709 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dqaGL-0004eH-Kx; Sat, 09 Sep 2017 03:33:10 -0400 In-reply-to: (message from Richard Copley on Fri, 8 Sep 2017 22:08:04 +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:218043 Archived-At: > From: Richard Copley > Date: Fri, 8 Sep 2017 22:08:04 +0100 > Cc: Paul Eggert , Angelo Graziosi , > Emacs Development > > >> Would you mind also suppressing warnings from find-file-noselect > >> when called from autoload-find-generated-file, please, if you don't > >> object? > > > > Sorry, I'm not sure that's the right solution in that case. We should > > try to understand why the problem happens in the first place. E.g., I > > don't see it here (but I don't use MinGW64 or MSYS2). > > Seriously (not being rude)? Yes, seriously. You'd expect that much of me, won't you? > It seems a lot of work for not much benefit. Not IME. I frequently find that the real root cause of such obscure problems is something altogether unexpected, and sometimes it's the tip of an iceberg. So I generally find looking into the root causes of such problems beneficial. > That conversion happens often, e.g., in normalize_filename. What conversion is that? > And it's unlikely a warning from find_file_noselect there is ever > going to be helpful in catching a new bug. You may be right. But we will only know for sure when we have understood the root cause. It could very well be that there is indeed a bug, and this warning has already caught it, except that it went unnoticed until now, because it was never reported before. For starters, can you or Angelo tell where did that upper-case "C:/" originate from? Also, are there other places in the build process that display file names with the upper-case drive letter? Thanks.