From: Tim Cross <theophilusx@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Alternatives for reliable build environments for emacs?
Date: Fri, 29 Oct 2021 06:58:07 +1100 [thread overview]
Message-ID: <875ytgj4w5.fsf@gmail.com> (raw)
In-Reply-To: <jwvv91ht1p3.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> I'm finding it increasingly difficult to build emacs in my distro,
>> Fedora(Ok, I havent managed to build emacs using distro dependencies for
>> a long time)
>
> That's a serious problem for Emacs, so please report these as bugs.
> I use the kind of "stgit" setup you describe on Debian testing machines
> and have none of the problems you describe, so my guess is that Fedora
> is a bit more "bleeding edge" and the Emacs code gets adjusted for the
> new libs before they reach Debian testing.
>
> Maybe we should have a "bleeding edge Fedora" build VM in EMBA to catch
> those problems?
>
Yes, some more details would be useful. I built emacs on fedora a few
months back without issue. Could it possibly be the issue is not that
Fedora is too bleeding endge or is it that the OP's version is too old
and so they have to install later lib versions than are available? It
would be good to know what version of fedora they are trying to build on.
I've also built emacs on recent arch without issue and arch typically
has pretty bleeding edge libs.
next prev parent reply other threads:[~2021-10-28 19:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 12:55 Alternatives for reliable build environments for emacs? joakim
2021-10-28 13:33 ` Eli Zaretskii
2021-10-28 14:38 ` joakim
2021-10-28 14:45 ` Robert Pluim
2021-10-28 15:22 ` joakim
2021-10-28 15:29 ` Robert Pluim
2021-10-28 19:09 ` Tassilo Horn
2021-10-29 6:14 ` Po Lu
2021-10-28 16:08 ` Eli Zaretskii
2021-10-28 17:37 ` joakim
2021-10-28 20:37 ` Pierre Téchoueyres
2021-10-29 0:29 ` Yuchen Pei
2021-10-29 6:14 ` Eli Zaretskii
2021-11-03 6:53 ` Yuchen Pei
2021-10-28 16:07 ` Yuri Khan
2021-10-28 20:20 ` Daniel Martín
2021-10-28 19:02 ` Stefan Monnier
2021-10-28 19:58 ` Tim Cross [this message]
2021-10-28 21:35 ` joakim
2021-10-30 6:52 ` Richard Stallman
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=875ytgj4w5.fsf@gmail.com \
--to=theophilusx@gmail.com \
--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).