From: Mike Frysinger <vapier@gentoo.org>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
"gdb@sourceware.org" <gdb@sourceware.org>,
Jan-Benedict Glaw <jbglaw@lug-owl.de>
Subject: Re: x86_64-elf gdb
Date: Mon, 30 Mar 2015 21:19:00 -0000 [thread overview]
Message-ID: <20150330211934.GG25224@vapier> (raw)
In-Reply-To: <5519B945.8030605@oarcorp.com>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
On 30 Mar 2015 15:59, Joel Sherrill 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.
so patch it locally, test everything, and only then send patches to the
respective projects ? i'm not sure why this is onerous ? this is how
it's always done for new targets ...
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-30 21:19 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 [this message]
2015-03-31 2:46 ` Jan-Benedict Glaw
2015-03-31 13:07 ` Jan-Benedict Glaw
2015-03-31 14:39 ` Joel Sherrill
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=20150330211934.GG25224@vapier \
--to=vapier@gentoo.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=jbglaw@lug-owl.de \
--cc=joel.sherrill@oarcorp.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