all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Rudi C <rudiwillalwaysloveyou@gmail.com>
Cc: 70071@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#70071: [FR] Provide official install scripts without requiring root, e.g., by making a static build possible
Date: Sat, 30 Mar 2024 09:19:23 +0800	[thread overview]
Message-ID: <87frw84iuc.fsf@yahoo.com> (raw)
In-Reply-To: <CAE9z9A0Ac815UYVuiL_YcWd9aHd7EDuzexyGyOxTNv7sBiiXVg@mail.gmail.com> (Rudi C.'s message of "Fri, 29 Mar 2024 17:54:13 +0330")

Rudi C <rudiwillalwaysloveyou@gmail.com> writes:

> My primary concern with your approach is that it requires numerous
> manual steps, each of which can introduce new points of failure.
> Would it be possible for you to provide a single script that I can run
> on Ubuntu (even on older versions with an outdated gcc, etc.) that
> will build Emacs under my home directory (~/)?

Emacs supports "older operating systems" with "outdated GCC" (back to
3.4.x) quite well, so I fail to see what the difficulty is with the
following two-liner:

  ./configure --prefix=$HOME
  make -j `nproc` install

which has been standard among autoconf-using programs since time
immemorial, if not earlier.

> While I don't claim to have a deep understanding of these terms, my
> interpretation is that dynamic linking connects to the installed
> system libraries, making the binary heavily reliant on the specific
> conditions of its host operating system.

This is not true or important, when two lines and a set of basic
development packages available on any self-respecting GNU/Linux
distribution should provide through their package repositories.

> In contrast, a statically linked binary includes all of its
> dependencies within itself, allowing a single binary for Linux x86 to
> function on most other similar systems. A "portable" binary is one
> that can be downloaded using wget and executed without relying on any
> dependencies from the host operating system. Of course, no binary can
> be completely portable, and portability exists on a spectrum. However,
> some binaries are quite portable, such as those found at
> https://github.com/Mozilla-Ocho/llamafile.

Statically linking against libc.a is inherently unreliable, but programs
dynamically linking against one specific version of the GNU C library,
and more often than not, other C libraries, will function normally on
systems with subsequent releases of the same.

In any event, volunteers are welcome to provide such binary
distributions of Emacs, but, Emacs being a portable program without
numerous elusive dependencies or non-standard build systems, I very much
doubt the game will be worth the candle.





  parent reply	other threads:[~2024-03-30  1:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29 12:42 bug#70071: [FR] Provide official install scripts without requiring root, e.g., by making a static build possible Rudi C
2024-03-29 13:27 ` Eli Zaretskii
2024-03-29 14:24   ` Rudi C
2024-03-29 14:33     ` Eli Zaretskii
2024-03-30  1:19     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-03-30 12:55       ` Rudi C
2024-03-30 13:28         ` Eli Zaretskii
2024-03-30 14:31           ` Rudi C
2024-03-31  0:37             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-31  6:02             ` Eli Zaretskii
2024-03-31  8:39 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-31  9:06   ` Rudi C
2024-03-31  9:31     ` Eli Zaretskii
2024-04-02 21:41       ` Richard Stallman
2024-04-06 10:31         ` Eli Zaretskii

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=87frw84iuc.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=70071@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=rudiwillalwaysloveyou@gmail.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 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.