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: Fri, 11 Sep 2020 10:45:30 +0200 [thread overview]
Message-ID: <CAPTJ0XGYXs-+db6w49d_QBNX16hYajOtXBQZt0nemVXE_GToeg@mail.gmail.com> (raw)
In-Reply-To: <20200911102955.71f38097@windsurf.hq.k.grp>
On Fri, Sep 11, 2020 at 10:29 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> On Thu, 10 Sep 2020 12:34:15 +0200
> Christian Biesinger <cbiesinger@google.com> wrote:
> > > 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.
(technically it's make that recurses, not configure)
It's true that gdb's configure checks for ncurses but that should be
an optional dependency. Did you find that configure fails if ncurses
is not found?
Christian
prev parent reply other threads:[~2020-09-11 8:46 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
2020-09-11 8:45 ` Christian Biesinger [this message]
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=CAPTJ0XGYXs-+db6w49d_QBNX16hYajOtXBQZt0nemVXE_GToeg@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).