From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: src/Makefile unhelpful Date: Sat, 10 Sep 2022 23:38:09 -0400 Message-ID: References: <83bkrrj48w.fsf@gnu.org> <81B26ACA-E8C3-4FAC-9BB5-A6B40C3B4A55@gentoo.org> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4385"; mail-complaints-to="usenet@ciao.gmane.io" Cc: eliz@gnu.org, emacs-devel@gnu.org To: Sam James Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Sep 11 05:39:11 2022 Return-path: Envelope-to: ged-emacs-devel@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 1oXDoM-0000yF-NN for ged-emacs-devel@m.gmane-mx.org; Sun, 11 Sep 2022 05:39:10 +0200 Original-Received: from localhost ([::1]:54494 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oXDoL-0008QY-8J for ged-emacs-devel@m.gmane-mx.org; Sat, 10 Sep 2022 23:39:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43536) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oXDnO-0006bP-B0 for emacs-devel@gnu.org; Sat, 10 Sep 2022 23:38:10 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55588) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oXDnO-0000fI-1n; Sat, 10 Sep 2022 23:38:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=caFUKpSIqASr+VxrqvKjQpw2nqjl0+A2zRSwjrwE4r4=; b=Ti/X82x+gjKw 0jJzWMZ0/gLACVMnRH42KgYO3q3xkN2EhBvv2kcfgWP1fVjlgxN/Ck47PH/L5IgzJje6jyD4bVhtr xUYJPHbyJH9Wni29pAQUBhjMXUx9gtESb7XuiytUuSdtuX3wAXilzbXkDagFJmeN7K2E4YMbI39s4 ITDK+ZmeApLrzXr5l3UK/Bk6vaK3+n5TDg7SXgeRg1jaFRMJIIrvHImqNwz1kgFUt1l51e+l8J1cv VJdCAwVDPJFqGUp3ha9nsE9oskQWGg6r2MPrtAGua4MH6bu0+8LJpAQHOcKqqQK8JnCzSxyPcAshg qQDxdnIXQxgJ6f/Dw462Yg==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1oXDnN-0002nY-LW; Sat, 10 Sep 2022 23:38:09 -0400 In-Reply-To: <81B26ACA-E8C3-4FAC-9BB5-A6B40C3B4A55@gentoo.org> (message from Sam James on Thu, 8 Sep 2022 05:51:37 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:295151 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > I agree we do not want to output the expansion more than once. > Note that CFLAGS can (I don't speak for whether they do in Emacs) > vary per file, target, directory, ... I'm asking for this in Emacs, and obly Emacs. The other programs I've worked on did not need anything like this. Their makefile commands were simple enough that you could figure out the precise options easily enough. So instead of proposing new features for make or automake, which nobody here is likely to work on, let's look for a simple way to implement this in the makefiles for Emacs itself. > As for CC, I think you could read configure output if you're particularly > interested in that. I'd have to figure out which make variables get used, since the output does not say. Then find out the value of each of them. It would be a lot of work. With the feature I proposed, it would be pretty easy. > I think if you do want this, the best place to recommend it would be > the automake mailing lists. Emacs will become harder to maintain > if it develops quirks like this, Alas, the quirks are already implemented. This command-explaining feature would not require any of the complexity. > >> The way to see the arguments is to say > > > >> make V=1 How about adding a make command such as @echo Use V=1 to see the actual compilation commands to run near the start of the make run. That would inform people. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)