From: Andrew Cagney <cagney@gnu.org>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA:] The CRIS simulator.
Date: Fri, 28 Jan 2005 20:49:00 -0000 [thread overview]
Message-ID: <41FAA54E.8080100@gnu.org> (raw)
In-Reply-To: <200501280442.j0S4g4B0013369@ignucius.se.axis.com>
> I certainly had a lot of fun with the autoconf change. I can't
> use the sim/README-HACKING instructions. For example the
> autoheader-common rule barfs all over and I still have an empty
> sim/cris/config.in. Running aclocal or autoheader manually
> doesn't help. Since sim/cris works anyway, I checked in the
> empty config.in to keep sim/cris/configure.ac uniform with the
> others. The barfing indicates missing quotations in
> common/aclocal.m4. Whatever.
Ah, ok (thanks). Remember that for GDB anyone can commit configure
changes and fixes (just ask your self "do you feel lucky" :-).
Andrew
next prev parent reply other threads:[~2005-01-28 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-18 14:25 Hans-Peter Nilsson
2005-01-10 23:43 ` Andrew Cagney
2005-01-28 4:42 ` Hans-Peter Nilsson
2005-01-28 20:49 ` Andrew Cagney [this message]
2005-01-29 0:57 ` Committed: fix sim subdir make calls Hans-Peter Nilsson
2005-02-02 16:20 ` Andrew Cagney
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=41FAA54E.8080100@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=hans-peter.nilsson@axis.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