From: Eli Zaretskii <eliz@gnu.org>
To: Daniele Nicolodi <daniele@grinta.net>
Cc: emacs-devel@gnu.org
Subject: Re: Supported platforms
Date: Mon, 17 Jun 2019 21:45:48 +0300 [thread overview]
Message-ID: <83ef3st5ib.fsf@gnu.org> (raw)
In-Reply-To: <97896823-3052-6616-7ded-3424a112469c@grinta.net> (message from Daniele Nicolodi on Mon, 17 Jun 2019 12:20:56 -0600)
> Cc: emacs-devel@gnu.org
> From: Daniele Nicolodi <daniele@grinta.net>
> Date: Mon, 17 Jun 2019 12:20:56 -0600
>
> On 15-06-2019 00:42, Eli Zaretskii wrote:
> >> From: Daniele Nicolodi <daniele@grinta.net>
> >> Date: Fri, 14 Jun 2019 14:42:32 -0600
> >>
> >> is there anywhere a list of the platforms (operating system and
> >> architecture) supported by Emacs?
> >
> > I don't think there are innate limitations. Any platform that
> > supports running a Posix shell, GNU Make, a C99-compliant C compiler,
> > and a standard C library, will do.
>
> Where are you drawing the line to call those the only required
> dependencies? For example, Emacs uses autoconf for the build process,
> thus I guess independently of the fact that autoconf support exists for
> the given platform, also an m4 implementation is required.
Not AFAIK, not for building a release tarball. For that, you only
need a Posix-compatible shell, capable of running a configure script.
So I think what I mentioned are indeed the only required dependencies.
You will need more only if you want to build from Git.
> Also, what standard C library?
A C99-compliant library will do, although we don't even assume that
100%.
> > Is there some specific question that you are interested in, or a
> > specific platform? And also, what version of Emacs are we talking
> > about? Versions before 27 could have problems in the dumping process.
>
> It is a question mostly out of curiosity. But there have been talks
> recently of working on improvements to the build process, and I am
> trying to understand what systems Emacs is targeting, what systems the
> build process needs to support, and on which systems Emacs is tested.
Well, is your curiosity satisfied?
prev parent reply other threads:[~2019-06-17 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 20:42 Supported platforms Daniele Nicolodi
2019-06-15 6:42 ` Eli Zaretskii
2019-06-17 18:20 ` Daniele Nicolodi
2019-06-17 18:45 ` Eli Zaretskii [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ef3st5ib.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=daniele@grinta.net \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).