From: Gregory Heytings <gregory@heytings.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Bruno Haible <bruno@clisp.org>, 65340-done@debbugs.gnu.org
Subject: bug#65340: further build failure on Android (Termux)
Date: Fri, 18 Aug 2023 12:13:20 +0000 [thread overview]
Message-ID: <94e8ba2aff2fd2ea39ed@heytings.org> (raw)
In-Reply-To: <874jkwh86b.fsf@yahoo.com>
>>> ./configure [...] --without-all --without-x
>>
>> Note that you can also build an unrestricted Emacs under Termux.
>
> If you read the bug report, you would have realized that it revolves
> entirely around building Emacs under Termux.
>
I did read the bug report, and did realize that it "revolves entirely
around building Emacs under Termux". See the first sentence of my post.
>
> Also, prior to the last several commits, building master under such an
> environment was impossible.
>
Not "impossible". It required patches, such as those provided by the
Termux team, some of which (or variants thereof) have now be included in
master.
next prev parent reply other threads:[~2023-08-18 12:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 10:34 bug#65340: further build failure on Android (Termux) Bruno Haible
2023-08-16 12:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-16 22:46 ` Bruno Haible
2023-08-17 0:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-17 13:50 ` Bruno Haible
2023-08-17 14:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 0:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 10:55 ` Bruno Haible
2023-08-18 11:50 ` Gregory Heytings
2023-08-18 12:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 12:13 ` Gregory Heytings [this message]
2023-08-18 12:48 ` Bruno Haible
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94e8ba2aff2fd2ea39ed@heytings.org \
--to=gregory@heytings.org \
--cc=65340-done@debbugs.gnu.org \
--cc=bruno@clisp.org \
--cc=luangruo@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.