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: Merging feature/android Date: Thu, 02 Mar 2023 16:00:54 +0200 Message-ID: <83zg8vckx5.fsf@gnu.org> References: <87edq7ztks.fsf.ref@yahoo.com> <87edq7ztks.fsf@yahoo.com> <83pm9reccn.fsf@gnu.org> <87v8jjxxo9.fsf@yahoo.com> <835ybje2u5.fsf@gnu.org> <87fsanxoah.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40075"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, eggert@cs.ucla.edu To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Mar 02 15:01:49 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 1pXjVE-000ACX-DL for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Mar 2023 15:01:48 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pXjUY-0007M6-3j; Thu, 02 Mar 2023 09:01:06 -0500 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 1pXjUV-0007Km-Uj for emacs-devel@gnu.org; Thu, 02 Mar 2023 09:01:03 -0500 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 1pXjUU-0006PW-W3; Thu, 02 Mar 2023 09:01:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=CmdLB7jSXOOwusLTlHPMJNCqSgNz+gcROYQCAToPo9k=; b=RKIQ1AVpdX2B V6raInuQrhTYrs4aQV79GE6TLM56bsJIiMbMNjO9yOc71HZkX94IyNya1IlrifNKQSB262szvHU/E NvAeXwjT1cdVTo9eaJ1RASUhEP2Hc+BwLH3eyzj+BQSDxUDC7RPknJLRdMZAXRqY5KhLgsgu705bB 4k3bDUrR8DcxgOp25wB1nsHDYxEaAKfloIQwL4m9/mv8gbTRoRQxTCQ0tfUNnB9BPBmG1VWyTqmo8 aNGl3yDAwVxGSec/gQXr7g5J4i4HYTCEqyhwdAIY1cYyBVmf3pGotAF+uoslIrt2Vj55JkuMizXa0 4EasRlYkaXLU5s4azEe5ag==; 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 1pXjUS-0000zm-T0; Thu, 02 Mar 2023 09:01:02 -0500 In-Reply-To: <87fsanxoah.fsf@yahoo.com> (message from Po Lu on Thu, 02 Mar 2023 21:42:30 +0800) 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:303897 Archived-At: > From: Po Lu > Cc: emacs-devel@gnu.org, eggert@cs.ucla.edu > Date: Thu, 02 Mar 2023 21:42:30 +0800 > > Eli Zaretskii writes: > > > Rewriting the configury is OK, but that still doesn't need > > ifavailable, AFAIU. For example, we build with HarfBuzz if that is > > available, but we don't use ifavailable for it. How is this one > > different? > > Well, it would be a nasty shock for someone to configure --with-modules, > and not get an error when dynamic modules cannot be used. I'm talking about the default case, where there's no --with-modules option explicitly in the configure command line. If the user does explicitly asks for modules, then emitting an error message is reasonable. But if the user didn't ask for that explicitly, why not silently disable the feature, like we do with HarfBuzz and others? > > What do you mean by "from the wrong copy"? The two copies are > > identical, no? They are generated for the same platform, right? > > They are generated for different platforms: the first copy is generated > for the system which is building Emacs (where we need an emacs binary to > build the ELCs), whilst the second copy in cross/ is generated for the > Android system. > > > In any case, before we include two copies, we should ask Gnulib folks > > for help in this matter. > > Perhaps Paul has a better idea, yes. Thanks in advance. I'd be surprised if Gnulib didn't have a way of supporting cross builds similar to this case.