Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: x86_64-elf gdb
Date: Tue, 31 Mar 2015 13:07:00 -0000	[thread overview]
Message-ID: <20150331130659.GA25589@lug-owl.de> (raw)
In-Reply-To: <20150331024600.GJ4243@lug-owl.de>

[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]

On Tue, 2015-03-31 04:46:01 +0200, Jan-Benedict Glaw <jbglaw@lug-owl.de> 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.

...and here's the very first x86_64-elf build:

	http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=433054


Pure Binutils (without GDB) und GCC worked fine so far, but GDB
didn't, as expected:

make all-gdb
[...]
configure: error: configuration x86_64-pc-elf is unsupported.
make: *** [configure-gdb] Error 1

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:             God put me on earth to accomplish a certain number of
the second  :            things. Right now I am so far behind I will never die.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-03-31 13:07 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 [this message]
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=20150331130659.GA25589@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --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