From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: karl@freefriends.org, raman@google.com, emacs-devel@gnu.org
Subject: Re: Can't build previous versions of Emacs?
Date: Sun, 17 Jul 2022 08:35:39 +0300 [thread overview]
Message-ID: <83fsj0qp1w.fsf@gnu.org> (raw)
In-Reply-To: <87tu7gh8ba.fsf@yahoo.com> (message from Po Lu on Sun, 17 Jul 2022 08:49:45 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: raman@google.com, emacs-devel@gnu.org
> Date: Sun, 17 Jul 2022 08:49:45 +0800
>
> Karl Berry <karl@freefriends.org> writes:
>
> > FWIW, I was able to compile e21 on a current x86_64 machine running
> > Alma Linux 8 (I doubt the os matters much) with the attached.
> > Copied in m/amdx86-64.h from 22.3 as a starting point. I didn't try to
> > include X support, since I had no interest in it.
>
> Nice. I was able to build Emacs 19.34 on a modern Fedora system. I
> wrote some new machine files based on the existing Alpha support, but
> just that unfortunately did not quite work, since it made assumptions
> about the DEC Alpha calling convention. So most of the work ended up
> being writing prototypes for the many implicitly declared functions,
> since returning int simply doesn't work (unlike on the Alpha.)
My hats off to MS-Windows, whose libc stability and backward
compatibility allow me to run and debug _today_ all the original
binaries of Emacs from 21.4 all the way to 28.1, each binary as it was
built in its own time. "Modern" systems have a lesson to learn there.
next prev parent reply other threads:[~2022-07-17 5:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 3:23 Can't build previous versions of Emacs? Eric Abrahamsen
2022-07-14 3:33 ` Po Lu
2022-07-14 16:13 ` Eric Abrahamsen
2022-07-14 17:07 ` Ulrich Mueller
2022-07-14 17:24 ` Lars Ingebrigtsen
2022-07-14 18:21 ` Stefan Monnier
2022-07-14 18:23 ` Lars Ingebrigtsen
2022-07-14 18:38 ` Stefan Monnier
2022-07-14 18:41 ` Lars Ingebrigtsen
2022-07-14 19:33 ` Andreas Schwab
2022-07-14 21:52 ` Stefan Kangas
2022-07-15 9:47 ` Lars Ingebrigtsen
2022-07-15 13:37 ` Stefan Kangas
2022-07-16 10:31 ` Lars Ingebrigtsen
2022-07-16 11:03 ` Po Lu
2022-07-16 11:05 ` Lars Ingebrigtsen
2022-07-16 11:17 ` Ulrich Mueller
2022-07-16 12:49 ` Po Lu
2022-07-16 13:01 ` Lars Ingebrigtsen
2022-07-16 14:54 ` Ulrich Mueller
2022-07-16 16:10 ` Lars Ingebrigtsen
2022-07-14 23:30 ` T.V Raman
2022-07-15 14:03 ` andrés ramírez
2022-07-15 14:50 ` Stefan Kangas
2022-07-15 15:30 ` Eli Zaretskii
2022-07-16 20:59 ` Karl Berry
2022-07-17 0:49 ` Po Lu
2022-07-17 5:35 ` Eli Zaretskii [this message]
2022-07-17 8:04 ` Gregory Heytings
2022-07-17 8:53 ` Po Lu
2022-07-17 8:56 ` Gregory Heytings
2022-07-17 9:27 ` Po Lu
[not found] ` <DM6PR03MB3803454A10E226097F5A3877A68D9@DM6PR03MB3803.namprd03.prod.outlook.com>
[not found] ` <83wncbq2ya.fsf@gnu.org>
2022-07-17 15:44 ` andrés ramírez
2022-07-14 19:02 ` Alan Mackenzie
2022-07-14 17:01 ` Lars Ingebrigtsen
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=83fsj0qp1w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=karl@freefriends.org \
--cc=luangruo@yahoo.com \
--cc=raman@google.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 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).