From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Move gdbserver to top level
Date: Tue, 21 Jan 2020 05:34:00 -0000 [thread overview]
Message-ID: <1a97e456-8dc8-48bb-20d0-ce8b746c8066@simark.ca> (raw)
In-Reply-To: <87d0bf45up.fsf@tromey.com>
On 2020-01-19 2:13 p.m., Tom Tromey wrote:
> Here's the next patch in the ongoing effort to move gdbserver to the top
> level.
>
> I've edited this patch before sending to ensure it won't be too large to
> be accepted by the list. In particular, I used "git show" to create the
> patch (this seems to handle moves better than "git send-email"), and I
> removed the generated files.
Top-level configure.ac says that configs:
- or1k*-*-linux*
- score-*-*
should build gdbserver, but I don't think they have a gdbserver port (despite
them having build_gdbserver=yes prior to this patch), do they?
When autoconf-ing gdbserver, I get:
gdbserver$ autoconf
/usr/bin/m4:acinclude.m4:20: cannot open `../../config/lib-ld.m4': No such file or directory
/usr/bin/m4:acinclude.m4:21: cannot open `../../config/lib-prefix.m4': No such file or directory
/usr/bin/m4:acinclude.m4:22: cannot open `../../config/lib-link.m4': No such file or directory
autom4te: /usr/bin/m4 failed with exit status: 1
I presume these paths need to be updated?
Other than that it LGTM. I fixed the paths above, re-generated everything, and I was able to
build fine.
Simon
next prev parent reply other threads:[~2020-01-21 4:21 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 20:07 Tom Tromey
2020-01-21 5:34 ` Simon Marchi [this message]
2020-01-23 22:03 ` Tom Tromey
2020-01-24 14:29 ` Hannes Domani via gdb-patches
2020-01-24 15:12 ` Tom Tromey
2020-01-24 15:57 ` Tom Tromey
2020-01-24 16:02 ` Hannes Domani via gdb-patches
2020-01-24 16:28 ` Tom Tromey
2020-01-24 16:35 ` Hannes Domani via gdb-patches
2020-01-24 19:03 ` Hannes Domani via gdb-patches
2020-01-24 15:23 ` Pedro Alves
2020-01-25 0:07 ` Tom Tromey
2020-01-25 16:55 ` Pedro Alves
2020-01-26 16:01 ` Tom Tromey
2020-01-27 18:13 ` Pedro Alves
2020-01-28 0:37 ` Tom Tromey
2020-01-28 14:28 ` Pedro Alves
2020-02-03 21:34 ` Tom Tromey
2020-02-07 16:06 ` Simon Marchi
2020-02-09 13:59 ` Tom de Vries
2020-02-09 14:17 ` Tom de Vries
2020-02-10 10:01 ` Tom de Vries
2020-02-10 15:54 ` Sergio Durigan Junior
2020-02-12 0:55 ` Tom Tromey
2020-02-12 16:47 ` Sergio Durigan Junior
2020-02-14 3:54 ` Sergio Durigan Junior
2020-02-14 18:43 ` Tom Tromey
2020-02-14 21:14 ` Tom Tromey
2020-02-17 13:58 ` Luis Machado
2020-02-17 14:21 ` Maciej W. Rozycki
2020-02-17 14:29 ` Luis Machado
2020-02-17 16:57 ` Luis Machado
2020-02-17 17:01 ` Tom Tromey
2020-02-17 17:28 ` Aktemur, Tankut Baris
2020-02-17 18:46 ` Tom Tromey
2020-02-10 10:59 ` [PATCH][gdb/testsuite] Skip multi-target.exp without gdbserver Tom de Vries
2020-02-10 12:20 ` Pedro Alves
2020-02-09 23:05 ` [PATCH] Move gdbserver to top level Alan Modra
2020-02-10 12:02 ` Pedro Alves
2020-02-10 9:52 ` Andreas Schwab
2020-02-10 12:13 ` Pedro Alves
2020-02-10 13:04 ` Andreas Schwab
2020-02-10 13:15 ` Andreas Schwab
2020-02-11 13:48 ` [PATCH] Disable gdbserver on host != target configurations (Re: [PATCH] Move gdbserver to top level) Pedro Alves
2020-02-11 15:29 ` 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=1a97e456-8dc8-48bb-20d0-ce8b746c8066@simark.ca \
--to=simark@simark.ca \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).