From: Simon Marchi <simark@simark.ca>
To: Tamar Christina <Tamar.Christina@arm.com>,
Tom Tromey <tom@tromey.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: nd <nd@arm.com>
Subject: Re: [PATCH] Change gdbserver to use existing gnulib and libiberty
Date: Mon, 24 Feb 2020 19:46:00 -0000 [thread overview]
Message-ID: <5f45f667-f425-d4e3-d0fd-3ed18c1dc590@simark.ca> (raw)
In-Reply-To: <PR2PR08MB4747C57E200D279F1E1E1F99FFEC0@PR2PR08MB4747.eurprd08.prod.outlook.com>
On 2020-02-24 9:16 a.m., Tamar Christina wrote:
> Hi Tom,
>
> We're having trouble building cross toolchains after this change.
>
> Before this we were able to build gdb running on HOST but build gdbserver running on TARGET.
>
> After this change we can no longer do this since you can't link objects from different architectures.
>
> Is this not a supported workflow anymore? Any suggestions how to do this after these changes?
>
> Thanks,
> Tamar
Hi Tamar,
When you were building gdb running on HOST and gdbserver running on TARGET, I presume
you were running two configure scripts, like this?
$ .../binutils-gdb/configure --host=x86-foo --target=arm-bar
and in another directory
$ .../binutils-gdb/gdb/gdbserver/configure --host=arm-bar
Now, gdbserver being a proper top-level project (just like gdb and binutils
are), you can do:
$ .../binutils-gdb/configure --host=x86-foo --target=arm-bar
... to configure GDB, and:
$ .../binutils-gdb/configure --target=arm-bar
... to configure GDBserver.
In fact, these commands set up build directories to build the entire
binutils-gdb repository. You could either pass a bunch of --disable-*
options to configure in order to disable the projects you don't want
to build, or build using "make all-gdb" / "make all-gdbserver" to only
build gdb or gdbserver respectively.
Hope that helps.
Simon
next prev parent reply other threads:[~2020-02-24 19:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 22:53 Tom Tromey
2020-02-08 7:42 ` Eli Zaretskii
2020-02-14 21:27 ` Tom Tromey
2020-02-24 14:16 ` Tamar Christina
2020-02-24 19:46 ` Simon Marchi [this message]
2020-02-26 21:50 ` Tamar Christina
2020-02-27 15:30 ` Pedro Alves
2020-02-27 16:36 ` Simon Marchi
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=5f45f667-f425-d4e3-d0fd-3ed18c1dc590@simark.ca \
--to=simark@simark.ca \
--cc=Tamar.Christina@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.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