From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com,
Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Subject: Re: [patch/gdb-6.1] Backport fix for hpux C compiler problem
Date: Fri, 04 Jun 2004 16:24:00 -0000 [thread overview]
Message-ID: <40C0A251.6030407@gnu.org> (raw)
In-Reply-To: <20040603073056.GN601@tausq.org>
> This fixes a build problem on hpux2.0w-hp-hpux11.00 when using the HP
> ANSI C compiler. It was committed to the branch earlier. Would like to
> get this into the 6.1 respin.
>
> Should be "obvious", but as this is for a stable release i'll just
> double check with you all before i check this in, ok? :-)
>
> As I mentioned in feedback to PR build/1458, I think that bug is
> resolved, partially via this fix.
>
> thanks,
> randolph
>
> 2004-06-03 Randolph Chung <tausq@debian.org>
>
> Fix PR build/1458
> * somsolib.c (som_solib_remove_inferior_hook): Use constant array size
> for dld_flags_buffer and make all size references consistent.
> * NEWS: Mention this fix.
Ok for 6.1.
Andrew
prev parent reply other threads:[~2004-06-04 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 7:31 Randolph Chung
2004-06-04 16:24 ` Andrew Cagney [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=40C0A251.6030407@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
--cc=randolph@tausq.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