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: Sat, 04 Mar 2023 09:28:48 +0200 Message-ID: <83edq5asb3.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> <83zg8vckx5.fsf@gnu.org> <87bklay7wg.fsf@yahoo.com> <83ilficn4k.fsf@gnu.org> <87zg8uw9b9.fsf@yahoo.com> <837cvycjse.fsf@gnu.org> <87ttz2w4c3.fsf@yahoo.com> <83356mcbxw.fsf@gnu.org> <87pm9qvu9w.fsf@yahoo.com> <83y1odc37g.fsf@gnu.org> <87cz5pwf9c.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19564"; 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 Sat Mar 04 08:29:40 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 1pYMKm-0004nU-W6 for ged-emacs-devel@m.gmane-mx.org; Sat, 04 Mar 2023 08:29:37 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pYMKJ-0000Gk-8i; Sat, 04 Mar 2023 02:29:07 -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 1pYMKE-0000GL-Fg for emacs-devel@gnu.org; Sat, 04 Mar 2023 02:29: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 1pYMKD-000723-NH; Sat, 04 Mar 2023 02:29:01 -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=S5uF7UVdYHFFN2FJU8mDNpviHSCYtAqoycsguvTbjOQ=; b=k8gp7Ygyy5z4 BOg/QUKQfGxx11LFtuvDmUPsslG6xnFefq35lbH7zX2Gkf6kVB8DTvFR3KKV03FTM516l605jhJdj LVidBrcBAyCP6IYJNN3YlDXTelr4NTWzr/Yo5uxCj2zzCBJfzATu53WdNJOC+Z82INFTqiRCE37Ms 4NWbWdbkvCVrrjPhxTKtmBSSURmoajYwCiqCZclWu5AKhkRDpSkPyelyCKH9HhZn0HpxgjJg5EU7a 3aiB6jvOkshznJTtjwnz08HbljoFg81J56e4557bGKP77D/IZDcUiVc4/PO8PrgXxYYk7WuOcW2Jp 6lbCfTemRJvH9KQOEgSoeA==; 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 1pYMKC-0007kQ-9g; Sat, 04 Mar 2023 02:29:01 -0500 In-Reply-To: <87cz5pwf9c.fsf@yahoo.com> (message from Po Lu on Sat, 04 Mar 2023 08:07:27 +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:303934 Archived-At: > From: Po Lu > Cc: emacs-devel@gnu.org, eggert@cs.ucla.edu > Date: Sat, 04 Mar 2023 08:07:27 +0800 > > Eli Zaretskii writes: > > >> From: Po Lu > >> Cc: emacs-devel@gnu.org, eggert@cs.ucla.edu > >> Date: Fri, 03 Mar 2023 21:28:27 +0800 > >> > >> Eli Zaretskii writes: > >> > >> > So why shouldn't it be the same with modules? Don't we want the user > >> > to be aware that modules support will be absent? > >> > >> No, I don't think so: that would amount to making Emacs not build > >> by default without a recent GCC. > > > > We had this in emacs-module.c for a long time, including two major > > releases. How come it was never a problem until now? > > I don't know, but it doesn't surprise me, since most people use GCC. macOS builds don't use GCC. But if this problem is basically limited to Android, how about solving it in emacs-module.c, via preprocessor directives, instead? Or even unconditionally disable modules in the configure script for Android? I think making changes that affect all the platforms for the benefit of Android should be limited to the absolute minimum.