Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: joel.sherrill@oarcorp.com
Cc: gdb-patches@sourceware.org
Subject: Re: Recent simulator patches broke many sims
Date: Sun, 24 Mar 2013 05:39:00 -0000	[thread overview]
Message-ID: <201303240038.r2O0cTSq009264@ignucius.se.axis.com> (raw)
In-Reply-To: <514E316E.6040107@oarcorp.com> (message from Joel Sherrill on	Sat, 23 Mar 2013 23:49:18 +0100)

> From: Joel Sherrill <joel.sherrill@oarcorp.com>
> Date: Sat, 23 Mar 2013 23:49:18 +0100

> And built successfully when configured like this:
> 
> ../gdb/configure --target=frv-elf --prefix=/home/joel/test-gdb/install 
> --enable-sim-hardware --enable-sim --enable-sim-trace

"gdb" as in toplevel from a gdb checkout, I presume.
(If from the gdb subdir I guess you wouldn't get very far.)
Is that why you have to add those options?

One major difference is that I use the toplevel configure after
a checkout of *the "sim" CVS module*, so not much of gdb there,
actually just MAINTAINERS and version.in.

> I can hop on IRC if you give me a channel so we can work through
> this quickly. Other forms of chat are OK also. I want to run this down
> so a release can happen.

Sometimes I'm at irc.oftc.net#gcc

brgds, H-P


  reply	other threads:[~2013-03-24  0:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-24  0:22 Hans-Peter Nilsson
2013-03-24  0:38 ` Joel Sherrill
2013-03-24  5:39   ` Hans-Peter Nilsson [this message]
2013-03-24  5:39     ` Joel Sherrill
2013-03-24 11:04       ` Hans-Peter Nilsson
2013-03-24  2:12 ` Joel Sherrill
2013-03-24  2:35 ` Joel Sherrill
2013-03-24  2:53   ` Hans-Peter Nilsson
2013-03-24  5:22     ` Hans-Peter Nilsson
2013-03-24  5:36     ` Hans-Peter Nilsson
2013-03-24  4:51   ` Hans-Peter Nilsson
2013-03-24 11:33   ` Mike Frysinger
2013-03-25  3:30     ` Joel Sherrill
2013-03-25  3:50       ` Hans-Peter Nilsson
2013-03-25  7:39         ` Joel Sherrill
2013-03-26 17:49         ` Mike Frysinger
2013-03-26 18:41           ` Hans-Peter Nilsson
2013-03-26 18:43             ` Joel Sherrill
2013-03-26 19:49             ` Mike Frysinger
2013-03-26 20:50               ` Hans-Peter Nilsson
2013-03-26 21:24                 ` Mike Frysinger
2013-03-27  1:39                   ` Hans-Peter Nilsson
2013-03-27  9:13                     ` Mike Frysinger
2013-03-26 18:56     ` Mike Frysinger
2013-03-27  8:47       ` Joel Brobecker
2013-03-27  8:50         ` Hans-Peter Nilsson
2013-03-27 18:38           ` Joel Sherrill
2013-03-27 19:01             ` Joel Brobecker
2013-03-27 19:43             ` Joel Brobecker

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=201303240038.r2O0cTSq009264@ignucius.se.axis.com \
    --to=hans-peter.nilsson@axis.com \
    --cc=gdb-patches@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