From: "Eli Zaretskii" <eliz@gnu.org>
To: mec.gnu@mindspring.com (Michael Chastain)
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] PROBLEMS: document hpux cma thread build failure
Date: Fri, 13 Aug 2004 15:28:00 -0000 [thread overview]
Message-ID: <3405-Fri13Aug2004182530+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040812192106.1F0004B359@berman.michael-chastain.com> (mec.gnu@mindspring.com)
> Date: Thu, 12 Aug 2004 15:21:06 -0400 (EDT)
> From: mec.gnu@mindspring.com (Michael Chastain)
>
> This patch adds a section to PROBLEMS for build/1411, which is a build
> failure on HP/UX if the CMA thread package is installed.
>
> I wrote this because a user came to bug-gdb@ today and reported the
> same problem again. So I figure it's worth a mention in PROBLEMS.
I agree. Please commit the patch.
> (By the way, bug-gdb@gnu.org is the mailing list documented in
> gdb.texinfo, but only two gdb maintainers are subscribed to it. It's
> moderated now so you can subscribe and not get spam).
I will subscribe to it soon. Thanks for the heads-up.
next prev parent reply other threads:[~2004-08-13 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 19:21 Michael Chastain
2004-08-13 15:28 ` Eli Zaretskii [this message]
2004-08-13 16:32 ` Michael Chastain
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=3405-Fri13Aug2004182530+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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