From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Madhu Newsgroups: gmane.emacs.devel Subject: Re: Org mode update breaking build? Date: Mon, 08 May 2023 17:30:17 +0530 Message-ID: References: <00b52cc1-b0ac-a0c0-c91d-33a7213e9881@web.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31987"; mail-complaints-to="usenet@ciao.gmane.io" To: emacs-devel@gnu.org Cancel-Lock: sha1:cOEQE1M1C8xwNzpRRcomPscQpaA= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 08 15:16:54 2023 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 1pw0jW-00083T-8S for ged-emacs-devel@m.gmane-mx.org; Mon, 08 May 2023 15:16:54 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pw0hG-00030I-Rh; Mon, 08 May 2023 09:14:34 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pvzXv-0004fb-LT for emacs-devel@gnu.org; Mon, 08 May 2023 08:00:51 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pvzXt-0004mq-52 for emacs-devel@gnu.org; Mon, 08 May 2023 08:00:51 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1pvzXq-0000X3-4r for emacs-devel@gnu.org; Mon, 08 May 2023 14:00:46 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Mon, 08 May 2023 09:14:06 -0400 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:305977 Archived-At: * Alan Mackenzie : Wrote on Wed, 3 May 2023 15:55:55 +0000: > On Wed, May 03, 2023 at 17:26:05 +0200, Tobias Bading wrote: >> Grrr. Is it normal that Org updates break builds? > For me, it has become normal. I'm not happy about it. > I don't use org, and I don't understand why I should be expected to > debug its breaking of the build. > > In practice, I have to do make bootstrap every time I update my > repositories. I haven't update master very recently but a while ago I got into the habit of running a script before calling `make'. the $1 parameter is the path to src/lisp. it lists stale elc files, which I then delete by hand. ``` for i in $(find "$1" -name \*.elc); do j=${i%c}; if [ ! -e "$i" ]; then echo "MISSING $i" >> /dev/stderr elif [ ! -e "$j" ]; then echo "MISSING $j" >> /dev/stderr else # file-newer-p.sh $j $i # UNTESTED. a=$(stat -c '%Y' "$j") b=$(stat -c '%Y' "$i") if [ $a -gt $a ]; then echo "$i"; fi; fi done ``` Since I started doing this, I don't think I've faced elisp recompilation problems. But I never understood the rationale for "loading stale elc" behaviour as a part of recompilation. If someone can explain that I'd appreciate it.