public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Christian Biesinger <cbiesinger@google.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: Fri, 11 Sep 2020 10:29:55 +0200	[thread overview]
Message-ID: <20200911102955.71f38097@windsurf.hq.k.grp> (raw)
In-Reply-To: <CAPTJ0XGYEU=P2vGU_ZnTre=+BVdKjRS-8p0mnV2-nXBai+2Q6g@mail.gmail.com>

On Thu, 10 Sep 2020 12:34:15 +0200
Christian Biesinger <cbiesinger@google.com> wrote:

> 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

Thanks for the pointer, seems useful, I'll give it a try.

> > 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...?

Well, I had missed the --disable-gdb option, and so for me a top-level
./configure would always recurse into gdb/, and gdb/configure.ac does
check for ncurses.

I'll give it a try with --disable-gdb and "make all-gdbserver" as
suggested by the documentation.

Thanks !

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-09-11  8:29 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
2020-09-11  8:29   ` Thomas Petazzoni [this message]
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=20200911102955.71f38097@windsurf.hq.k.grp \
    --to=thomas.petazzoni@bootlin.com \
    --cc=cbiesinger@google.com \
    --cc=gdb@sourceware.org \
    --cc=romain.naour@smile.fr \
    --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).