From: David Carlton <carlton@math.stanford.edu>
To: Phil Edwards <phil@jaj.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: SYMBOL_SOURCE_NAME breakage
Date: Thu, 20 Feb 2003 20:06:00 -0000 [thread overview]
Message-ID: <ro1adgq67kb.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20030220174204.GA8906@disaster.jaj.com>
On Thu, 20 Feb 2003 12:42:04 -0500, Phil Edwards <phil@jaj.com> said:
> The recent rename of SYMBOL_SOURCE_NAME missed a couple spots in
> gdb/gdbtk/generic/gdbtk-cmds.c, leading to link failure using current
> (as of 10 minutes ago) CVS HEAD. Doing the 2 renames in that file allows
> the build to pass.
> (I'm not fixing it myself because I don't have write privs to src repo.)
My apologies; that's twice in the last two days that I've done this.
I'll go and replace my gdb+dejagnu CVS source tree with an
insight+dejagnu CVS source tree, so hopefully it won't happen again in
the future.
Thanks to you and Keith for dealing with this.
David Carlton
carlton@math.stanford.edu
prev parent reply other threads:[~2003-02-20 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 17:42 Phil Edwards
2003-02-20 17:47 ` Keith Seitz
2003-02-20 20:06 ` David Carlton [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=ro1adgq67kb.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=gdb-patches@sources.redhat.com \
--cc=phil@jaj.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