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: Wed, 08 Mar 2023 15:41:12 +0200 Message-ID: <83356f5pjb.fsf@gnu.org> References: <87edq7ztks.fsf.ref@yahoo.com> <87lekcvho4.fsf@yahoo.com> <83r0u4adgd.fsf@gnu.org> <87a60suknn.fsf@yahoo.com> <83356jafll.fsf@gnu.org> <87o7p7tz16.fsf@yahoo.com> <83sfej8v17.fsf@gnu.org> <87fsajtrrx.fsf@yahoo.com> <83o7p78ns8.fsf@gnu.org> <87y1obsamf.fsf@yahoo.com> <0100f288-fcc0-8b91-5f12-18bf22969e50@cs.ucla.edu> <87ttyzs8q1.fsf@yahoo.com> <253e9494-6f78-89b7-8f5f-9c2e8461d95a@cs.ucla.edu> <878rgaspvs.fsf@yahoo.com> <86bkl6z1sc.fsf@aarsen.me> <87mt4qqi2o.fsf@yahoo.com> <83a60q84eo.fsf@gnu.org> <87a60qqb0c.fsf@yahoo.com> <83y1oa6k71.fsf@gnu.org> <87sfehpfcv.fsf@yahoo.com> <83a60o7mif.fsf@gnu.org> <87jzzspvcl.fsf@yahoo.com> <83ttyw65v5.fsf@gnu.org> <4B15D851-5638-48E6-A789-3017A1CBA971@yahoo.com> <8584ff7c-f83e-18b1-1300-dfa0788e4443@cs.ucla.edu> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13679"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Luangruo@yahoo.com, arsen@aarsen.me, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Mar 08 14:42:02 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 1pZu3O-0003LC-KO for ged-emacs-devel@m.gmane-mx.org; Wed, 08 Mar 2023 14:42:02 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pZu2j-00088g-Tb; Wed, 08 Mar 2023 08:41:21 -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 1pZu2e-000889-Hu for emacs-devel@gnu.org; Wed, 08 Mar 2023 08:41:18 -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 1pZu2d-0000sP-6u; Wed, 08 Mar 2023 08:41:15 -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=gtzvlQ70OUojnRa0CNyhy8tPHUH78O96GlgD5DhvyWQ=; b=AvcchNYeTRa4 dz5vbm04kJUW4LSo0WVBK+TzFWUYM0iOJGWMPhm5aHwfbJQBuzmDnBnj2YpVN01LuWC/7g5avJMqv MRJ+vQU6xcDNjrWY5Ck8w2s9TwyK20GdVvteg40bTv7WI0NKEZw/rRH6QnfWGYRXiwHx06h2MnSj9 LN3JPA+Vt78XUPScvGTIyS92EuEs+MJZnRYJztJmqBvApVgWckrTqRNzZ0aMFBPNaWW2tQzJfha0m ++IHY4i14+6//XTwrkKm/SUEgvSr2ZrXkWQ5YyP7Rb5hWgePJcd24jPYpobHzgq/+W+Ba7geqBMXI IaPV7kYvbswjgq3G3Q6UvA==; 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 1pZu2c-0002px-8T; Wed, 08 Mar 2023 08:41:14 -0500 In-Reply-To: <8584ff7c-f83e-18b1-1300-dfa0788e4443@cs.ucla.edu> (message from Paul Eggert on Tue, 7 Mar 2023 21:38:39 -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:304127 Archived-At: > Date: Tue, 7 Mar 2023 21:38:39 -0800 > Cc: arsen@aarsen.me, emacs-devel@gnu.org > From: Paul Eggert > > On 2023-03-07 15:55, Po Lu wrote: > > XPM is actually a good example of what I'm talking about: it is used by default only if the system in question typically has libXpm preinstalled. > > That's not true for JPEG, PNG, GIF, TIFF, GnuTLS, and probably other > libraries. > > I routinely run into the sort of messages that Eli is talking about if I > run plain 'configure' on some platforms. Solaris 10, for example, > typically doesn't have a JPEG library installed. It's not that big a > deal to read the error message at the end of the failed 'configure', > sigh, and re-run configure with the --with-jpeg=ifavailable option that > 'configure' suggests. 100% agreement.