From: Phillip Lord <phillip.lord@russet.org.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Avoid duplicate emacs.exe / emacs-$version.exe
Date: Sat, 28 Mar 2020 20:13:09 +0000 [thread overview]
Message-ID: <87h7y8me5m.fsf@russet.org.uk> (raw)
In-Reply-To: <83tv285ole.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 28 Mar 2020 21:19:41 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Right now in my hard disk I have two copies of statically linked Emacs.
>
> (This is a secondary point, but Emacs is not linked statically, at
> least not by default. The large size is mostly due to debug info, and
> you can strip it if you want, although I don't recommend doing so for
> a pretest version, because you cannot produce meaningful backtraces
> from a stripped binary.)
The pretests should be stripped actually. I use make install for
snapshot builds. The ones with an actual version number are make
install-strip'd.
> This means your installation procedure is modified, or maybe you
> installed a binary someone else produced, in which case the archive
> used to package the binaries didn't support hard links. You can
> restore the hard link by removing onhe of the copies and making a hard
> link to the remaining copy under the other name.
Incidentally, I build, run and (sort of) test the Windows distribution
under NTFS compression which all works fine. If these circumstances, I
think, even the difference between two files or hard-linked is moot.
Phil
next prev parent reply other threads:[~2020-03-28 20:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 16:53 Avoid duplicate emacs.exe / emacs-$version.exe Juan José García-Ripoll
2020-03-28 18:19 ` Eli Zaretskii
2020-03-28 20:41 ` Juan José García-Ripoll
2020-03-28 22:45 ` Phillip Lord
2020-03-29 2:31 ` Eli Zaretskii
2020-03-29 9:38 ` Juan José García-Ripoll
2020-03-29 13:08 ` Phillip Lord
2020-03-29 14:10 ` Eli Zaretskii
2020-03-28 18:19 ` Eli Zaretskii
2020-03-28 20:13 ` Phillip Lord [this message]
2020-03-28 20:48 ` Juan José García-Ripoll
2020-03-28 22:22 ` Phillip Lord
2020-03-28 23:36 ` Juan José García-Ripoll
2020-03-29 12:55 ` Phillip Lord
2020-03-29 2:27 ` Eli Zaretskii
2020-03-29 12:52 ` Phillip Lord
2020-03-29 13:56 ` Eli Zaretskii
2020-03-29 17:25 ` Phillip Lord
2020-03-28 23:36 ` Juan José García-Ripoll
2020-03-29 2:36 ` Eli Zaretskii
2020-03-29 12:59 ` Phillip Lord
2020-03-29 13:59 ` Eli Zaretskii
2020-03-29 18:18 ` Phillip Lord
2020-03-29 18:34 ` Eli Zaretskii
2020-03-29 20:49 ` Phillip Lord
-- strict thread matches above, loose matches on Subject: below --
2020-03-29 17:01 Angelo Graziosi
2020-03-29 17:22 ` 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=87h7y8me5m.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juanjose.garciaripoll@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.