From: Christian Biesinger <cbiesinger@google.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Reuben Thomas via Gdb <gdb@sourceware.org>,
Tom Tromey <tom@tromey.com>,
Romain Naour <romain.naour@smile.fr>
Subject: Re: Building just gdbserver ?
Date: Thu, 10 Sep 2020 12:34:15 +0200 [thread overview]
Message-ID: <CAPTJ0XGYEU=P2vGU_ZnTre=+BVdKjRS-8p0mnV2-nXBai+2Q6g@mail.gmail.com> (raw)
In-Reply-To: <20200910115339.52495057@windsurf.hq.k.grp>
On Thu, Sep 10, 2020 at 11:53 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
> Prior to the move of gdb/gdbserver/ to the top-level
> (919adfe8409211c726c1d05b47ca59890ee648f1), and its use of the common
> gnulib (1a627e7e6c61e97951932e3a9c5fb706efe3ef3e), it was possible to
> build just gdbserver by doing:
>
> $ cd gdb/gdbserver/
> $ ./configure
>
> This is a feature that was used by the Buildroot build system when we
> only needed to build gdbserver and not the full gdb.
>
> What is now the recommended way to build just gdbserver ?
See the "Building" section in
https://github.com/bminor/binutils-gdb/blob/master/gdbserver/README
> Running the top-level configure script would be annoying, as it checks
> for ncurses, which would make ncurses a mandatory requirement to build
> gdbserver, which by itself doesn't need ncurses.
I don't believe the toplevel configure script checks for ncurses...?
Christian
next prev parent reply other threads:[~2020-09-10 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 9:53 Thomas Petazzoni
2020-09-10 10:34 ` Christian Biesinger [this message]
2020-09-11 8:29 ` Thomas Petazzoni
2020-09-11 8:45 ` Christian Biesinger
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='CAPTJ0XGYEU=P2vGU_ZnTre=+BVdKjRS-8p0mnV2-nXBai+2Q6g@mail.gmail.com' \
--to=cbiesinger@google.com \
--cc=gdb@sourceware.org \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).