From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: static linking of gdb
Date: Sun, 5 Apr 2020 15:23:45 +0200 [thread overview]
Message-ID: <AM6PR03MB51708CF3E2278A9ACB3C5C8AE4C50@AM6PR03MB5170.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <837dyut6kx.fsf@gnu.org>
Oh, no.
We need to catch exceptions from shared libraries?
Why ?
Not being able to link gdbserver with static libstdc++
will render this tool useless....
Sorry,
Bernd.
On 4/5/20 3:17 PM, Eli Zaretskii wrote:
>> From: Bernd Edlinger <bernd.edlinger@hotmail.de>
>> Date: Sun, 5 Apr 2020 12:13:42 +0200
>>
>> I noticed that gdb is currently not
>> linking libstdc++ statically, as it did
>> in the past if I remember correclty.
>
> You need to request that by passing --with-static-standard-libraries
> to the configure script. Note that if you do that, you may encounter
> an error at configure time, because the configure script thinks the
> above option is incompatible with source-highlight library (without
> checking whether a static version of that library is available). This
> was reported here:
>
> https://sourceware.org/pipermail/gdb-patches/2020-February/165843.html
>
> but AFAIK was not fixed yet.
>
next prev parent reply other threads:[~2020-04-05 13:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 10:13 Bernd Edlinger
2020-04-05 13:17 ` Eli Zaretskii
2020-04-05 13:23 ` Bernd Edlinger [this message]
2020-04-05 13:48 ` Bernd Edlinger
2020-04-05 14:19 ` Eli Zaretskii
2020-04-05 14:56 ` Bernd Edlinger
2020-04-06 3:27 ` Bernd Edlinger
2020-04-06 7:14 ` Bernd Edlinger
2020-04-06 13:43 ` Tom Tromey
2020-04-06 13:42 ` Tom Tromey
2020-04-06 13:45 ` Bernd Edlinger
2020-04-06 14:11 ` Tom Tromey
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=AM6PR03MB51708CF3E2278A9ACB3C5C8AE4C50@AM6PR03MB5170.eurprd03.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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