Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: Fix gdb compilation on Tru64 UNIX
Date: Thu, 21 Jan 2010 17:05:00 -0000	[thread overview]
Message-ID: <m3wrzbwfqy.fsf@fleche.redhat.com> (raw)
In-Reply-To: <yddtyujfjut.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's 	message of "Mon, 18 Jan 2010 17:39:22 +0100")

>>>>> "Rainer" == Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:

Rainer> napms() is declared only if _XOPEN_SOURCE_EXTENDED is defined, which
Rainer> requires _XOPEN_SOURCE >= 420.

Rainer> 2010-01-18  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
Rainer> 	* gdb_curses.h [__osf__] (_XOPEN_SOURCE, _XOPEN_SOURCE_EXTENDED)
Rainer> 	Define.
Rainer> 	* solib-osf.c (osf_current_sos): Initialize tail.

The solib-osf.c change is ok.

I am not as sure about the gdb_curses.h change.  I don't think we have
many host tests like that.  Perhaps some kind of configury would be
better.

Tom


  reply	other threads:[~2010-01-21 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 16:39 Rainer Orth
2010-01-21 17:05 ` Tom Tromey [this message]
2010-01-21 22:49   ` Rainer Orth
2010-01-22  1:43     ` Tom Tromey

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=m3wrzbwfqy.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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