Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] fix syntax errors in hpread.c
Date: Thu, 04 Jan 2007 14:11:00 -0000	[thread overview]
Message-ID: <20070104141105.GB15440@nevyn.them.org> (raw)
In-Reply-To: <20070104072205.GS3434@adacore.com>

On Thu, Jan 04, 2007 at 11:22:05AM +0400, Joel Brobecker wrote:
> Hello,
> 
> The gods of automated nightly builds whispered to me in my sleep that
> hpread.c failed to build last night. There are indeed a couple of
> syntax errors that slipped through the the last commit. Fixed thusly.
> 
> I can't test this myself because it looks like this code handles C++
> objects. I don't have a C++ compiler available to me on HP/UX. The
> change looks reasonably obvious, so hopefully it is fine.

Thanks.  This is not just C++ support but specifically aCC SOM support;
and it's on its way out, but let's keep it building until it goes.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2007-01-04 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04  7:21 Joel Brobecker
2007-01-04 14:11 ` Daniel Jacobowitz [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=20070104141105.GB15440@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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