From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Org mode update breaking build? Date: Wed, 03 May 2023 19:04:12 +0300 Message-ID: <83y1m5l7ur.fsf@gnu.org> References: <00b52cc1-b0ac-a0c0-c91d-33a7213e9881@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39215"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Tobias Bading Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 03 18:04:08 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 1puExb-000A02-Cp for ged-emacs-devel@m.gmane-mx.org; Wed, 03 May 2023 18:04:07 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1puEx2-00080p-IO; Wed, 03 May 2023 12:03:32 -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 1puEwz-0007ma-LH for emacs-devel@gnu.org; Wed, 03 May 2023 12:03:29 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1puEww-0005Hp-NO; Wed, 03 May 2023 12:03:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=T2Zv7KXt8RSJ/zFRvt7nr59Lxb10vb+L8zRfZnzJLdY=; b=dWenxoZEilUWeNnQzd6g suX+q5dDVOX7NVlk90y45Df4YPL/pwV0oALQ3JhYnRGry5qdFFHxK3KqZ+q5587BI6GJ3f3LbbUdg aYONEYueW2dLI/5gmFqewykgoCwPmxrMwgmQiXWD9McAbPue1m/hDn4nOr4IaRZ32kZd0mEH3OkOp 1w6QAND6UDuHt3xU24cFLPIRP6guCSmI2cjE+wcX4RuFKfrvKju3OCCJt6e87UPBa9bWRPYq4suo2 cLJ4ek5DuP8DfWY7i/g05AV17OSJyBtnzhLaJB2/oNIlPZ6ubBz2UO8lDT+oCcIc1uaAX20rblyP1 sRkWWZAEQUzRGA==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1puEwv-0003nk-EV; Wed, 03 May 2023 12:03:26 -0400 In-Reply-To: <00b52cc1-b0ac-a0c0-c91d-33a7213e9881@web.de> (message from Tobias Bading on Wed, 3 May 2023 17:26:05 +0200) 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:305785 Archived-At: > Date: Wed, 3 May 2023 17:26:05 +0200 > From: Tobias Bading > > Warning (emacs): Org version mismatch.  Org loading aborted. > This warning usually appears when a built-in Org version is loaded > prior to the more recent Org version. > > Version mismatch is commonly encountered in the following situations: > > […] > > In toplevel form: > org/ob-core.el:31:2: Error: Org version mismatch.  Make sure that correct ‘load-path’ is set early in init.el > make[3]: *** [Makefile:332: org/ob-core.elc] Error 1 > make[3]: *** Waiting for unfinished jobs.... > > --- >% --- > > A “git clean -fdx -e .ccls-cache -e compile_commands.json -e TAGS” plus > “./autogen.sh” plus “configure […]” plus “nice make -j4” later I have a > working clean Emacs 29 again. > > But of course the same happens again in my hacked worktree. So this time I > try “make distclean” for a change — plus the whole autogen, configure, > make aria again. And guess what… the error is still there! > > Is that normal? Yes, on emacs-29. Well, not "normal" but "expected". The fix is to remove lisp/org/*.elc and say "make" again. There's a solution on master, and an improvement on that solution in the works, but I decided not to risk that on the release branch, since the problem happens relatively rarely and the workaround is simple enough.