From: Tom Tromey <tom@tromey.com>
To: William Tambe via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: how to build gdbserver as a static binary ?
Date: Fri, 04 Feb 2022 11:12:13 -0700 [thread overview]
Message-ID: <87leyqwlfm.fsf@tromey.com> (raw)
In-Reply-To: <CAF8i9mMbk1ZL-W2s-n2-hxuc7O9f_vwQQJAn6HDOvnSpiw64PA@mail.gmail.com> (William Tambe via Gdb-patches's message of "Thu, 3 Feb 2022 15:15:57 -0600")
>>>>> "William" == William Tambe via Gdb-patches <gdb-patches@sourceware.org> writes:
William> Is it possible to build gdbserver as a static binary ?
William> Using --enable-static --with-static-standard-libraries has not helped.
I don't know the answer. I guess you could check to see if
--with-static-standard-libraries even affects gdbserver.
Also, I wonder if it's even possible. Isn't there some problem with
statically linked programs using dlopen? (I only vaguely recall
something like this.) Anyway, this matters because gdbserver has to
dlopen libthread_db.
Tom
next prev parent reply other threads:[~2022-02-04 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 21:15 William Tambe
2022-02-04 18:12 ` Tom Tromey [this message]
2022-02-05 0:28 ` Maciej W. Rozycki
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=87leyqwlfm.fsf@tromey.com \
--to=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).