From: "andrés ramírez" <rrandresf@hotmail.com>
To: "T.V Raman" <raman@google.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Lars Ingebrigtsen <larsi@gnus.org>,
Ulrich Mueller <ulm@gentoo.org>,
Eric Abrahamsen <eric@ericabrahamsen.net>,
emacs-devel@gnu.org
Subject: Re: Can't build previous versions of Emacs?
Date: Fri, 15 Jul 2022 14:03:28 +0000 [thread overview]
Message-ID: <DM6PR03MB38037C379FE0B28A542B4254A68B9@DM6PR03MB3803.namprd03.prod.outlook.com> (raw)
In-Reply-To: <p91lesvjmqk.fsf@google.com>
Hi. Guys.
JIC. If You want to try emacs-20 right now. You try in on netbsd. netbsd
guys still compile and have a packaged emacs-20.
If You want to try emacs-23. Ulrich and the gentoo guys have a heavily
patched emacs-23 version still compiling on latest gentoo. And they also
have an emacs18 still compiling too.
But. Right. +1 on having an 'emacs wayback machine'
BTW: {compiling 21.4 took some workarounds on arm. But I believe It
could be possible compiling it on x86 too}. Below is the probe.
--8<---------------cut here---------------start------------->8---
To: bug-gnu-emacs@gnu.org
Subject: I am report-emacs-bug on emacs-21.4 {compiled}
--text follows this line--
This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.
Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.
In GNU Emacs 21.4 (armv7l-unknown-linux-gnu)
of 2022-04-08 on chama
configured using `configure '--with-x-toolkit=no' '--with-xpm=no' '--with-jpeg=no' '--with-tiff=no' '--with-gif=no' '--with-png=no''
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: nil
locale-coding-system: nil
default-enable-multibyte-characters: t
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
--8<---------------cut here---------------end--------------->8---
Best Regards
>>>>> "T" == T V Raman <raman@google.com> writes:
T> That said should we think of a "emacs wayback machine" -- would be nice in 2030 to download
T> and run an Emacs-21 to see how it was back then :-) --
T> Thanks,
T> --Raman(I Search, I Find, I Misplace, I Research) ♉ Id: kg:/m/0285kf1 🦮
next prev parent reply other threads:[~2022-07-15 14:03 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 [this message]
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
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=DM6PR03MB38037C379FE0B28A542B4254A68B9@DM6PR03MB3803.namprd03.prod.outlook.com \
--to=rrandresf@hotmail.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=raman@google.com \
--cc=ulm@gentoo.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).