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: Android port Date: Sat, 05 Aug 2023 15:31:51 +0300 Message-ID: <83h6pdsma0.fsf@gnu.org> References: <1428589171.162865.1691134964773@mail1.libero.it> <4266545.pEEEotNZAM@nimes> <1613375937.6291379.1691233559950@mail1.libero.it> <4484333.4B0zn089NQ@nimes> <83msz5sn66.fsf@gnu.org> <87zg357kgv.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37099"; mail-complaints-to="usenet@ciao.gmane.io" Cc: bruno@clisp.org, angelo.g0@libero.it, eggert@cs.ucla.edu, emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 05 14:32:01 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 1qSGRs-0009PW-Ok for ged-emacs-devel@m.gmane-mx.org; Sat, 05 Aug 2023 14:32:00 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qSGRY-0005YC-0k; Sat, 05 Aug 2023 08:31:40 -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 1qSGRX-0005Y3-3j for emacs-devel@gnu.org; Sat, 05 Aug 2023 08:31:39 -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 1qSGRV-0001Ep-Hg; Sat, 05 Aug 2023 08:31:37 -0400 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=iKxx14z6no9Hr+a28sBZ42KG/3/Bfj7VzH8ZPQ85/9M=; b=iwlnGEc9Ga9C 19rTP1wmwcyImS9i0LFDQsRfpQSLaIPE2scbI0URLyXiivhTcjU0SAJMS+XAwv252iGMkgOcPxOb2 TFnBdSdGanFvuRgmiGqipiI+4RmsGoe5O/ZEt+x3P59HJyzFe5B7ezX9tVLqVgb8hbyw+Sk8jSDWZ 6X7cdphNGktDTVamsTqZPi3ouah0HQCJfsmOslLPLpHiXEPmYwO2qWAWuC+ZrlxwioOcKZhPoS0NE TqgsnQtZBXq0hboNorXxkXPjUCCqw741PGVW6/dx/l7FlP3st8zuh1BFAGe6frHjJe9FrTNKAbl9t LXsM1zqKiEWXvOwYGQL8mw==; 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 1qSGRV-0000HM-0d; Sat, 05 Aug 2023 08:31:37 -0400 In-Reply-To: <87zg357kgv.fsf@yahoo.com> (message from Po Lu on Sat, 05 Aug 2023 20:16:32 +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:308316 Archived-At: > From: Po Lu > Cc: Bruno Haible , angelo.g0@libero.it, > eggert@cs.ucla.edu, emacs-devel@gnu.org > Date: Sat, 05 Aug 2023 20:16:32 +0800 > > Eli Zaretskii writes: > > > Since the *printf family doesn't need to be replaced in the Emacs > > build on MS-Windows, I'd rather we understood why the above causes > > compilation errors. Aren't Gnulib replacements for *printf functions > > supposed to have prototypes compatible to the MinGW headers? > > Judging from the headers Angelo provided, the issue lies in MinGW's > headers defining (not merely declaring) asprintf: > > #ifdef _GNU_SOURCE > __mingw_ovr > __attribute__ ((__format__ (gnu_printf, 2, 3))) __attribute__((nonnull (1,2))) > int asprintf(char **__ret, const char *__format, ...) > { > int __retval; > __builtin_va_list __local_argv; __builtin_va_start( __local_argv, __format ); > __retval = __mingw_vasprintf( __ret, __format, __local_argv ); > __builtin_va_end( __local_argv ); > return __retval; > } > > IMHO, the least risky solution remains disabling the vasprintf module > entirely. I agree. We wanted to do that from the get-go, but you said it was somehow impossible, or didn't work? > We can revisit this problem when and if Emacs begins to rely on ISO > C2X and C99 features supplied by Gnulib. Right.