From: Andrew Cagney <ac131313@ges.redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] gdb/configure: Add check for sys/proc.h
Date: Mon, 08 Jul 2002 21:24:00 -0000 [thread overview]
Message-ID: <3D2A62AA.3020304@ges.redhat.com> (raw)
In-Reply-To: <20020706021043.GA1091@gnat.com>
> This is in preparation for some later patches porting GDB to
> i386-interix: when compiling proc-api.c, we try to include <sys/proc.h>
> but this header file does not exist. I haven't checked this myself,
> but I trust that the definitions that proc-api was needing from this
> file will be found elsewhere. So I would like to conditionalize the
> inclusion of this file using the HAVE_SYS_PROC_H macro. The following
> patch introduces this macro.
>
> 2002-07-05 Joel Brobecker <brobecker@gnat.com>
>
> Define HAVE_SYS_PROC_H if sys/proc.h exists
> * configure.in: Add check for sys/proc.h
> * config.in: Regenerate.
> * configure: Regenerate.
>
> This patch has been tested on x86-linux (no sys/proc.h), and on
> sparc-solaris (have sys/proc.h).
>
> Ok to commit?
Yes. In general, any developer ``brave enough'' can commit changes to
configure.in. Just post them first for comment.
Can you just check that you're using the BINUTILS 000227 autoconf. I'm
asking as I noticed:
> ***************
> *** 379,392 ****
> /* Define if you have the <sys/select.h> header file. */
> #undef HAVE_SYS_SELECT_H
>
> - /* Define if you have the <sys/stat.h> header file. */
> - #undef HAVE_SYS_STAT_H
> -
> /* Define if you have the <sys/syscall.h> header file. */
> #undef HAVE_SYS_SYSCALL_H
> -
> - /* Define if you have the <sys/types.h> header file. */
> - #undef HAVE_SYS_TYPES_H
>
> /* Define if you have the <sys/user.h> header file. */
> #undef HAVE_SYS_USER_H
which has me puzzled. I suspect it might just be that config.in is
out-of-datem dig dig. Yep :-/
Andrew
next prev parent reply other threads:[~2002-07-09 4:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 8:46 Joel Brobecker
2002-07-08 21:24 ` Andrew Cagney [this message]
2002-07-09 16:16 ` Joel Brobecker
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=3D2A62AA.3020304@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.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