From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Joel Brobecker <brobecker@adacore.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: x86_64-elf gdb
Date: Tue, 31 Mar 2015 14:39:00 -0000 [thread overview]
Message-ID: <551AB1AD.7050509@oarcorp.com> (raw)
In-Reply-To: <20150331024600.GJ4243@lug-owl.de>
On 3/30/2015 9:46 PM, Jan-Benedict Glaw wrote:
> On Mon, 2015-03-30 15:59:49 -0500, Joel Sherrill <joel.sherrill@oarcorp.com> wrote:
>> On 3/30/2015 3:54 PM, Joel Brobecker wrote:
>>>> It built for me. But I don't have any way to test it. Is that
>>>> enough to submit a patch for the elf stanza addition?
>>> That seems odd to me. What would be the advantage of pushing that
>>> patch if it's a configuration that you can't test?
>> At the moment, x86_64-elf doesn't even build for binutils-gdb. It
>> fails due to a missing gdb configuration.
>>
>> And if binutils-gdb doesn't complete successfully, that means gcc
>> can't be built for this target.
>>
>> Jan.. do you build binutils-gdb and gcc for this target?
> I didn't build it until a minute ago, just x86_64-linux was on the
> list. It's added now, so let's wait for the first build to take place
> and see how well that works.
This is the patch I posted before I dragged you into this. It includes
both -elf
and -rtems targets. If you use this, just drop the -rtems target. I was just
experimenting and realized the -elf target didn't build. With this, it
built.
$ git diff gdb
diff --git a/gdb/configure.tgt b/gdb/configure.tgt
index 8feda7c..bd03600 100644
--- a/gdb/configure.tgt
+++ b/gdb/configure.tgt
@@ -664,6 +664,9 @@ x86_64-*-freebsd* | x86_64-*-kfreebsd*-gnu)
i387-tdep.o i386bsd-tdep.o i386fbsd-tdep.o \
bsd-uthread.o fbsd-tdep.o solib-svr4.o"
;;
+x86_64-*-elf* | x86_64-*-rtems*)
+ gdb_target_obs="amd64-tdep.o i386-tdep.o i387-tdep.o i386bsd-tdep.o"
+ ;;
x86_64-*-mingw* | x86_64-*-cygwin*)
# Target: MingW/amd64
gdb_target_obs="amd64-tdep.o amd64-windows-tdep.o \
> MfG, JBG
>
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
prev parent reply other threads:[~2015-03-31 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 21:08 Joel Sherrill
2015-03-30 16:39 ` Joel Brobecker
2015-03-30 19:15 ` Joel Sherrill
2015-03-30 20:54 ` Joel Brobecker
2015-03-30 20:59 ` Joel Sherrill
2015-03-30 21:19 ` Mike Frysinger
2015-03-31 2:46 ` Jan-Benedict Glaw
2015-03-31 13:07 ` Jan-Benedict Glaw
2015-03-31 14:39 ` Joel Sherrill [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=551AB1AD.7050509@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=jbglaw@lug-owl.de \
/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