> OK, so that's one mystery down. We are left with the HarfBuzz issue;
> please answer the questions I asked about that.
Ah, yes sorry - I acquired the DLLs from the
mingw64/mingw-w64-x86_64-harfbuzz package.
$ objdump -x /mingw64/bin/libharfbuzz-0.dll | grep "DLL Name":
DLL Name: libgcc_s_seh-1.dll
DLL Name: GDI32.dll
DLL Name: KERNEL32.dll
DLL Name: msvcrt.dll
DLL Name: RPCRT4.dll
DLL Name: libstdc++-6.dll
DLL Name: USER32.dll
DLL Name: USP10.dll
DLL Name: libfreetype-6.dll
DLL Name: libglib-2.0-0.dll
DLL Name: libgraphite2.dll
DLL Name: libintl-8.dll
harfbuzz does load correctly now that the pdmp is being loaded correctly -
I believe because now it passes the `intialized` check and so actually
attempts to load them.
describe-char shows me: harfbuzz:-outline-Iosevka Fixed
SS02-regular-normal-normal-mono-14-*-*-*-c-*-iso8859-1 (#x56)
On Tue, Sep 10, 2024 at 2:47 PM Eli Zaretskii <e...@gnu.org> wrote:
> > From: Casey Banner <kcban...@gmail.com>
> > Date: Tue, 10 Sep 2024 14:31:07 -0400
> > Cc: 73...@debbugs.gnu.org
> >
> > > How come your LANG is set to en_US.UTF-8? Did you set this in the
> > > environment or something. Using UTF-8 as the default encoding on
> > > Windows is not a good idea.
> >
> > It seems that the msys2 .profile has `export LANG=$(locale -uU)`, and
> that returns en_US.UTF-8 for me.
>
> I don't recommend running Emacs from the MSYS2 Bash prompt. Instead,
> run it from a desktop shortcut or pin it to the task bar and run from
> there.
>
> > > Please look at src/epaths.h and see how PATH_EXEC is defined there.
> >
> > It is indeed #define PATH_EXEC
> "%emacs_dir%/libexec/emacs/30.0.50/x86_64-w64-mingw32"
> >
> > src/epaths.in has #define PATH_EXEC "/usr/local/libexec/emacs"
> >
> > I had been running configure and make in a subdirectory. If I run them
> in the top-level directory,
> > then it does update PATH_EXEC to the correct version. I think I made the
> wrong assumption that
> > running configure in a subdirectory would leave the main source clean.
> >
> > Thank you for your help debugging this!
>
> OK, so that's one mystery down. We are left with the HarfBuzz issue;
> please answer the questions I asked about that.
>
