Re: [PATCH 0/1] Build GDB as a C++ program by default

Eli Zaretskii
2016-04-19T15:23:33Z

> Cc: simon.marchi@ericsson.com, gdb-patches@sourceware.org
> From: Pedro Alves <palves@redhat.com>
> Date: Tue, 19 Apr 2016 16:03:41 +0100
>
> On 04/19/2016 03:48 PM, Eli Zaretskii wrote:
> >> From: Pedro Alves <palves@redhat.com>
> >> Date: Tue, 19 Apr 2016 15:18:35 +0100
> >>
> >> MinGW (w64) builds and runs cleanly for me too.
> >
> > Did you look at what libraries it depends on? Doesn't it pull in
> > libgcc DLL and libstdc++ DLL? If it does, that'll put a huge damper
> > on those who make precompiled binaries of GDB available for Windows
> > users, because you need to accompany that with the full GCC source
> > tarball, which weighs in at more than 80MB.
>
> GDB links with libgcc even when built as a C program.

Not here, it doesn't. It is linked statically against libgcc. (I
don't use MinGW64, but I don't think it matters.) Here's what
'objdump -x | fgrep "DLL Name:"' says about the latest GDB 7.11 I
built:

(standard input):73: DLL Name: libguile-2.0-22.dll
(standard input):204: DLL Name: KERNEL32.dll
(standard input):298: DLL Name: msvcrt.dll
(standard input):323: DLL Name: msvcrt.dll
(standard input):450: DLL Name: libncurses5.dll
(standard input):501: DLL Name: USER32.dll
(standard input):510: DLL Name: WS2_32.dll
(standard input):531: DLL Name: zlib1.dll
(standard input):542: DLL Name: python26.dll

This is a build that (as you see) supports TUI, Python, and Guile, so
it's as full as it gets.

> How's C++ any different?

With C, you can get away by using "CC='gcc -static-libgcc'" at
configure time, but can you do the same with -static-libstdc++? I had
bad experience with that in the past (the binary still depended on
libstdc++ DLL), but maybe that was when building shared libraries, not
.exe programs. Thus my question (sorry, didn't yet have time to build
a recent development snapshot of GDB).

Thanks.