From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Working rgrep in windows emacs in 2024? (GNU emacs 29.1, windows 11 Enterprise)
Date: Tue, 13 Feb 2024 15:47:39 +0200 [thread overview]
Message-ID: <86r0hgpjb8.fsf@gnu.org> (raw)
In-Reply-To: <yqoonklo7ckh6bk.fsf@dod.no> (message from Steinar Bang on Tue, 13 Feb 2024 13:55:27 +0100)
> From: Steinar Bang <sb@dod.no>
> Date: Tue, 13 Feb 2024 13:55:27 +0100
>
> I have downloaded the grep w32 utilities from ezwinports and the find
> w64 utilities, unpacked them, and copied the files in bin directory of
> both unpacked zip files, into a directory found in the PATH (as set with
> setenv in a previous post in the thread), and in exec-path (as set with
> a different setting):
> c:\Windows\ezwinports
>
> But I couldn't find the required dlls mentioned in the ezwinports
> README.
>
> The
> https://osdn.net/projects/mingw/downloads/72215/libgcc-9.2.0-3-mingw32-dll-1.tar.xz/
> and
> https://osdn.net/projects/mingw/downloads/72210/libstdc%2B%2B-9.2.0-3-mingw32-dll-6.tar.xz/
> URLs get 504 Bad Gateway and broken SSL
I still see the files:
https://osdn.net/projects/mingw/downloads/72215/libgcc-9.2.0-3-mingw32-dll-1.tar.xz/
https://osdn.net/projects/mingw/downloads/72210/libstdc%2B%2B-9.2.0-3-mingw32-dll-6.tar.xz/
The site is a bit slow to load, and you could get a warning about an
expired license, but if you insist, you will get to the DLLs.
> And I can't figure out where they are, starting at
> https://osdn.net/projects/mingw/releases/
They are under "MinGW.OSDN Compiler Collection (GCC)".
I'm sorry about the hassle, but I cannot distribute the binaries of
these DLLs without also distributing the humongous GCC and libstdc++
source tarballs.
next prev parent reply other threads:[~2024-02-13 13:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 11:20 Working rgrep in windows emacs in 2024? (GNU emacs 29.1, windows 11 Enterprise) Steinar Bang
2024-02-13 12:23 ` Steinar Bang
2024-02-13 12:32 ` Steinar Bang
2024-02-13 12:55 ` Steinar Bang
2024-02-13 13:47 ` Eli Zaretskii [this message]
2024-02-14 7:50 ` Steinar Bang
2024-02-13 13:28 ` Eli Zaretskii
2024-02-14 8:26 ` Steinar Bang
2024-02-14 9:00 ` Steinar Bang
2024-02-14 15:08 ` Eli Zaretskii
2024-02-14 15:09 ` Eli Zaretskii
2024-02-15 9:40 ` Gregor Zattler
2024-02-15 10: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=86r0hgpjb8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).