[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#45303: #45303 [feature/native-comp] building error on Windows
From: |
Eli Zaretskii |
Subject: |
bug#45303: #45303 [feature/native-comp] building error on Windows |
Date: |
Sat, 19 Dec 2020 19:37:49 +0200 |
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Sat, 19 Dec 2020 17:15:02 +0000
>
> > I must be missing something, because I don't see strsignal used on
> > master in the MinGW build at all. Moreover, Gnulib's strsignal.c is
> > not even in lib/. We call sigdescr_np instead. So I wonder how did
> > you see that the Gnulib replacement for strsignal is used on master in
> > the Windows build.
>
> Entirely possible that I have misunderstood something from reading
> sources and grepping (the gnulib gyrations are hard to follow).
>
> The emacs source calls strsignal, and something provides it (whether via
> a macro replacement or a linkable symbol). The only difference I could
> see was the configure test, as noted above.
The ultimate test is this:
gdb ./emacs.exe
GNU gdb (GDB) 10.1
Copyright (C) 2020 Free Software Foundation, Inc.
...
(gdb) rbreak strsignal
On my system, I see just this:
Breakpoint 2 at 0x119b88b: file sysdep.c, line 2617.
const char *safe_strsignal(int);
> I see that src/syssignal.h has a replacement macro:
>
> #ifndef HAVE_STRSIGNAL
> # define strsignal(sig) safe_strsignal (sig)
> #endif
>
> So is the problem that on the native branch the configure test succeeds
> and sets HAVE_STRSIGNAL, resulting in trying to link the wrong symbol ?
Possibly. The question is, how come the test succeeds? Can you look
in libjccjit.a with "nm -A" and see if it exports strsignal?
- bug#45303: 28.0.50; [feature/native-comp] comp.c compilation error on Windows 10, (continued)
- bug#45303: #45303 [feature/native-comp] building error on Windows, Pal Gloss, 2020/12/18
- bug#45303: #45303 [feature/native-comp] building error on Windows, Andrea Corallo, 2020/12/18
- bug#45303: #45303 [feature/native-comp] building error on Windows, Eli Zaretskii, 2020/12/18
- bug#45303: #45303 [feature/native-comp] building error on Windows, Pal Gloss, 2020/12/18
- bug#45303: #45303 [feature/native-comp] building error on Windows, Andrea Corallo, 2020/12/19
- bug#45303: #45303 [feature/native-comp] building error on Windows, Andy Moreton, 2020/12/19
- bug#45303: #45303 [feature/native-comp] building error on Windows, Eli Zaretskii, 2020/12/19
- bug#45303: #45303 [feature/native-comp] building error on Windows, Andy Moreton, 2020/12/19
- bug#45303: #45303 [feature/native-comp] building error on Windows,
Eli Zaretskii <=
- bug#45303: #45303 [feature/native-comp] building error on Windows, Andy Moreton, 2020/12/19
- bug#45303: #45303 [feature/native-comp] building error on Windows, Pal Gloss, 2020/12/19
- bug#45303: #45303 [feature/native-comp] building error on Windows, Andrea Corallo, 2020/12/19
- bug#45303: #45303 [feature/native-comp] building error on Windows, Andy Moreton, 2020/12/20
- bug#45303: #45303 [feature/native-comp] building error on Windows, Andrea Corallo, 2020/12/20
- bug#45303: #45303 [feature/native-comp] building error on Windows, Andrea Corallo, 2020/12/20
- bug#45303: #45303 [feature/native-comp] building error on Windows, Andy Moreton, 2020/12/20
- bug#45303: #45303 [feature/native-comp] building error on Windows, Andrea Corallo, 2020/12/21
- bug#45303: #45303 [feature/native-comp] building error on Windows, Andrea Corallo, 2020/12/21
- bug#45303: #45303 [feature/native-comp] building error on Windows, Andy Moreton, 2020/12/21