Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 9.0.90 available for testing
Date: Mon, 23 Dec 2019 13:56:00 -0000	[thread overview]
Message-ID: <83blrzxi1f.fsf@gnu.org> (raw)
In-Reply-To: <20191223080116.GA14905@adacore.com> (message from Joel Brobecker	on Mon, 23 Dec 2019 12:01:16 +0400)

> Date: Mon, 23 Dec 2019 12:01:16 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> > 1. The produced gdb.exe and gdbserver.exe depend on the libstdc++ and
> >    libgcc DLLs.  I thought this was supposed to be prevented, or did I
> >    dream?  Should I force -static-libgcc etc. switches via
> >    configure-time variables?
> 
> If you build with GNU Highligh support (used to highlight the sources),
> then you need to use the shared libstdc++. So, if you need GDB to use
> the static version of the libgcc/libstdc++, you'll need to configure
> GDB explicitly, via:
> 
>     --with-static-standard-libraries
>     --disable-source-highlight

I don't think this is related to source-highlight in my case, because
I have only the static libsource-highlight.a library installed.  (I
didn't install the shared library version precisely because it depends
on libstdc++ DLL.)

I think Pedro explained why I suddenly have the dependency on libstc++
DLL where I didn't with previous GDB versions: we no longer inherit
-static-libstdc++ switch from GCC.  It now has to be requested
explicitly, via --with-static-standard-libraries.


  reply	other threads:[~2019-12-23 13:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 21:47 Joel Brobecker
2019-12-11 21:56 ` Joel Brobecker
2019-12-16 17:23 ` Eli Zaretskii
2019-12-16 17:38   ` Simon Marchi
2019-12-16 17:50     ` Eli Zaretskii
2019-12-23  7:54       ` Joel Brobecker
2019-12-16 18:52   ` Christian Biesinger via gdb-patches
2019-12-16 19:18     ` Eli Zaretskii
2019-12-16 19:36       ` Pedro Alves
2019-12-16 19:57         ` Eli Zaretskii
2019-12-16 20:37           ` Christian Biesinger via gdb-patches
2019-12-16 20:38           ` Pedro Alves
2019-12-17 17:25             ` Eli Zaretskii
2019-12-18 20:19   ` Christian Biesinger via gdb-patches
2019-12-19 15:00     ` Eli Zaretskii
2019-12-19 19:17       ` Christian Biesinger via gdb-patches
2019-12-19 19:38         ` Eli Zaretskii
2019-12-23  7:43           ` Joel Brobecker
2019-12-23 17:32             ` Eli Zaretskii
2019-12-24  3:53               ` Joel Brobecker
2019-12-24 15:30                 ` Eli Zaretskii
2020-01-17 20:56                   ` Christian Biesinger via gdb-patches
2020-01-17 21:09                     ` Eli Zaretskii
2019-12-23  8:01   ` Joel Brobecker
2019-12-23 13:56     ` Eli Zaretskii [this message]
2019-12-24  3:49       ` Joel Brobecker

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83blrzxi1f.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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