From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
gdb-patches@sources.redhat.com, dave@hiauly1.hia.nrc.ca
Subject: Re: [hpux] Fix build problem on hpux
Date: Fri, 10 Mar 2006 12:50:00 -0000 [thread overview]
Message-ID: <20060310023252.GA10422@nevyn.them.org> (raw)
In-Reply-To: <4410C609.5090207@tausq.org>
On Fri, Mar 10, 2006 at 08:19:21AM +0800, Randolph Chung wrote:
> 2005-03-09 Randolph Chung <tausq@debian.org>
>
> * hpread.c (hpread_start_psymtab): Remove hpread_psymtab_to_symtab
> declaration.
> * acinclude.m4 (gdb_AC_HPUX): Define.
> * config.in (_XOPEN_SOURCE_EXTENDED): Define if needed.
> * configure.ac: Call gdb_AC_HPUX.
> * configure: Regenerate.
config.in is a generated file, as the comment at the top says.
> +AC_DEFUN(gdb_AC_HPUX,
> +[AC_BEFORE([$0], [AC_TRY_COMPILE])dnl
> +AC_BEFORE([$0], [AC_TRY_RUN])dnl
> +AC_MSG_CHECKING(for HPUX)
> +AC_EGREP_CPP(yes,
> +[#ifdef _HPUX_SOURCE
> + yes
> +#endif
> +], [AC_MSG_RESULT(yes); AC_DEFINE(_XOPEN_SOURCE_EXTENDED)], AC_MSG_RESULT(no))
> +])
> +
What does the existance of _HPUX_SOURCE have to do with this?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-10 2:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 18:05 Randolph Chung
2006-03-09 19:14 ` Mark Kettenis
2006-03-10 1:35 ` Randolph Chung
2006-03-10 1:48 ` John David Anglin
2006-03-10 2:33 ` Randolph Chung
2006-03-10 11:15 ` John David Anglin
2006-03-10 12:50 ` Daniel Jacobowitz [this message]
[not found] ` <4410EE58.1060007@tausq.org>
[not found] ` <20060310035929.GA12013@nevyn.them.org>
[not found] ` <4410FF26.40509@tausq.org>
2006-03-26 8:33 ` Randolph Chung
2006-03-28 22:29 ` Daniel Jacobowitz
2006-03-29 0:28 ` Randolph Chung
2006-03-29 4:36 ` Daniel Jacobowitz
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=20060310023252.GA10422@nevyn.them.org \
--to=drow@false.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
--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