From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#53358: 29.0.50; Compilation output messed up again Date: Fri, 21 Jan 2022 10:24:58 +0100 Message-ID: <87czklwidx.fsf@gnus.org> References: <87lezcdtm3.fsf@gnus.org> <83czkot7og.fsf@gnu.org> <877dawdr1o.fsf@gnus.org> <46443e67-1a43-cfa6-35c1-8284af383389@cs.ucla.edu> <87k0eu7rov.fsf@gnus.org> <3c5c8f89-86ae-0fa9-9151-773cced53bd9@cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23091"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: 53358@debbugs.gnu.org To: Paul Eggert Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jan 21 10:27:26 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAqCc-0005lx-44 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 21 Jan 2022 10:27:26 +0100 Original-Received: from localhost ([::1]:53416 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nAqCb-0001OD-5U for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 21 Jan 2022 04:27:25 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:33618) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nAqBN-0007kH-Gp for bug-gnu-emacs@gnu.org; Fri, 21 Jan 2022 04:26:09 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39033) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nAqBG-0002qT-4Q for bug-gnu-emacs@gnu.org; Fri, 21 Jan 2022 04:26:09 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nAqBF-0001TB-VR for bug-gnu-emacs@gnu.org; Fri, 21 Jan 2022 04:26:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 21 Jan 2022 09:26:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 53358 X-GNU-PR-Package: emacs Original-Received: via spool by 53358-submit@debbugs.gnu.org id=B53358.16427571115582 (code B ref 53358); Fri, 21 Jan 2022 09:26:01 +0000 Original-Received: (at 53358) by debbugs.gnu.org; 21 Jan 2022 09:25:11 +0000 Original-Received: from localhost ([127.0.0.1]:60169 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nAqAR-0001Ry-1V for submit@debbugs.gnu.org; Fri, 21 Jan 2022 04:25:11 -0500 Original-Received: from quimby.gnus.org ([95.216.78.240]:60232) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nAqAP-0001Rf-BX for 53358@debbugs.gnu.org; Fri, 21 Jan 2022 04:25:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=vZCN49bDmEU8qSHbpcx50b7erGsV3ZSjSS3SOHxyEYo=; b=tr/lDc4tW5SWFAJV6UXkXYm88M mrirPDmGoQGo5Xd/RxZF2HVDI6247EZJ2WT8xXByWhaUXYrn1YT0E5Yjwkkf+vokHUqOYkWXMeMeL 6GaprtL3JryKOChgGE1BxT7SynZ4pUvhgKwcrFLI7p5GxAMmLw3spQMo38mmz93Ya7vo=; Original-Received: from [84.212.220.105] (helo=giant) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAqAF-0008IE-1d; Fri, 21 Jan 2022 10:25:01 +0100 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAAG1BMVEU8WyYdI11fMxOU aUK4r7QZEQ6UWRHjpiX///93nAk3AAAAAWJLR0QIht6VegAAAAd0SU1FB+YBFQkLOnxH59QAAAGC SURBVDjLdZPBboMwDIZRpd3LpD5AjWLuhG4PUJ4gUsp5mUjuSCWvP9tQkYTuPwDKx287sVNV/6p+ pw0ASWvd3+/NqTPmqvVZwCeDnoAetO4sNHW9g4YdAwHdwfUFLhsYhk4zuSYO/NW6uvcnQO8gAeiD 1h99BT7EJQfeKWuV8b4AMTCwFjPHhUBcrKh0LF6t4FGA2W4yBVAvYEMOZA2AHmMCalmxY4xkNBmQ SFN4Sl0pmHhFtWsJaQ4n9ZCmN+BxBDX43UEt2B0YODsDZbMNeqlnBaPLAAf/JmANdinASJW2csTZ kVB7ZslOEdsMYJilSyWAFdhwI5oClBy0xakA1Fr6l7If+yFg5IcvAI3s2vOvAiwKGj4XUzpmmlLu H2bAUShAHjnj8ACAGwze+PysbjIQNPYTZo5F/reAoBCT5O1iNqDSKSEQrYyOQvfIkrdRuXV/rs2r ogsGRlkKmF81T1fKO0THH6nDs6hWYP4GAMgr7XkicD9pDieRVu0jetS5+gOKr92CeTbTtgAAACV0 RVh0ZGF0ZTpjcmVhdGUAMjAyMi0wMS0yMVQwOToxMTo1OCswMDowMF2s0GkAAAAldEVYdGRhdGU6 bW9kaWZ5ADIwMjItMDEtMjFUMDk6MTE6NTgrMDA6MDAs8WjVAAAAAElFTkSuQmCC X-Now-Playing: Brian Auger & Julie Driscoll's _Open_: "Isola Natale" In-Reply-To: <3c5c8f89-86ae-0fa9-9151-773cced53bd9@cs.ucla.edu> (Paul Eggert's message of "Thu, 20 Jan 2022 10:21:17 -0800") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:224725 Archived-At: Paul Eggert writes: > Surely it's just an accident that you've seen it only for ELC, as the > problem can occur if 'make' executes any two $(info ...)s at about the > same time. In principle, but that's the only place I'm seeing this. > How badly does it occur for you? For me, it's only the first line > (when many 'makes' start in parallel, which is a glitch I can easily > ignore. I see it on every build I do (8 core machine, 16 threads, so I use -j16). And since the build is so nice and warning-free these days, those messed-up lines stick out. > If it's a real annoyance please try the attached patch, which should > fix the problem for the AM_V_ stuff at the cost of appending annoying > empty lines with current and older GNU make. (Which annoyance do you > prefer? :-) You'll need to run './config.status' after applying the > patch. Unfortunately there's been other changes in these files, so the patch no longer applies. But I don't think it makes sense to work around this problem by making the output look worse for most people, so I'd rather just avoid using $(info) in the problematic parts -- then it'll look OK for everybody (and without obfuscation). -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no