From: joakim@verona.se
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Alternatives for reliable build environments for emacs?
Date: Thu, 28 Oct 2021 16:38:54 +0200 [thread overview]
Message-ID: <871r45ciyp.fsf@tanaka.verona.se> (raw)
In-Reply-To: <83zgqts28b.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 28 Oct 2021 16:33:40 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: joakim@verona.se
>> Date: Thu, 28 Oct 2021 14:55:27 +0200
>>
>> 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)
>
> Why? what are the difficulties?
In my case one of the problems that started the downward spiral was the versions shipped of gnutls in
fedora which didnt work with emacs.
The separate aproach of building all the dependencies emacs need in a
separate build environment does work, like the Guix aproach.
I could probably convince guix to do what I want, but guix is also
fiddly. I was just wondering if somebody else had a solution for a
reproducible development environment for emacs.
Maybe I'm the only one facing these difficulties, that's fine I guess.
--
Joakim Verona
joakim@verona.se
next prev parent reply other threads:[~2021-10-28 14:38 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871r45ciyp.fsf@tanaka.verona.se \
--to=joakim@verona.se \
--cc=eliz@gnu.org \
--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 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.