From: Phillip Lord <phillip.lord@russet.org.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: juanjose.garciaripoll@gmail.com, emacs-devel@gnu.org
Subject: Re: Avoid duplicate emacs.exe / emacs-$version.exe
Date: Sun, 29 Mar 2020 19:18:49 +0100 [thread overview]
Message-ID: <87a73zdnxy.fsf@russet.org.uk> (raw)
In-Reply-To: <83blof5kjr.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 29 Mar 2020 16:59:20 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Phillip Lord <phillip.lord@russet.org.uk>
>> Cc: Juan José García-Ripoll
>> <juanjose.garciaripoll@gmail.com>,
>> emacs-devel@gnu.org
>> Date: Sun, 29 Mar 2020 13:59:40 +0100
>>
>> >> Just a side note: the build-zips.sh script that makes the Windows
>> >> distribution files always uses the flag -static when building emacs.
>> >
>> > I don't think the build should use that. It is certainly not the
>> > default.
>>
>> IIRC, without this the no-deps version fails, because of a requirement
>> for libwinpthreads.
>
> We should try building Emacs so that it isn't dependent on
> libwinpthreads. (Mine isn't, but I'm using a different MinGW flavor.)
Well, my records tell me that I have used "-static" since Emacs-25.1
which is the first version with a 64bit build, and the first version I
built.
I cannot find any discussion about this on the mailing list other than this:
https://lists.gnu.org/archive/html/emacs-devel/2016-11/msg00271.html
which just shows my failing memory and a different problem.
Anyway, I just tried a build without it on an Emacs-28 snapshot. Emacs
fails to launch with an "libgmp-10.dll is missing" error.
I am happy if someone wants to work out how to remove "-static" from the
build files, but I have neither the time nor expertise.
Phil
next prev parent reply other threads:[~2020-03-29 18:18 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
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 [this message]
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
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=87a73zdnxy.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 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).