From: Klaus Zeitler <kzeitler@lucent.com>
Cc: emacs-devel@gnu.org
Subject: Re: syswait.h
Date: 29 Jul 2002 13:08:08 +0200 [thread overview]
Message-ID: <q5gheiikd0n.fsf@lucent.com> (raw)
In-Reply-To: <200207261843.g6QIhxX09256@aztec.santafe.edu>
>>>>> "Richard" == Richard Stallman <rms@gnu.org> writes:
Richard>
Richard> It looks like your system's sys/wait.h defines macros to access
Richard> the wait argument as a structure, but that is not what Emacs
Richard> expects on a POSIX system. I don't have a copy of the POSIX spec
Richard> here; does anyone know what it says about this?
Richard>
Richard> Meanwhile, I think some people have build Emacs on HPUX 11
Richard> and do not have this problem. Why is that? Could others who
Richard> have HPUX 11 see how these macros are defined in sys/wait.h?
Richard> Do they expect to operate on a struct or on an int?
Richard>
this is amazing, so here's an excerpt from /usr/include/sys/wait.h, i.e.
the last 20 lines:
#ifdef _BSD
# undef WIFEXITED
# define WIFEXITED(_X) ((_X).w_stopval != WSTOPFLG && (_X).w_termsig == 0)
# undef WIFSTOPPED
# define WIFSTOPPED(_X) ((_X).w_stopval == WSTOPFLG)
# undef WIFSIGNALED
# define WIFSIGNALED(_X) ((_X).w_stopval != WSTOPFLG && (_X).w_termsig != 0)
# undef WEXITSTATUS
# define WEXITSTATUS(_X) ((_X).w_retcode)
# undef WTERMSIG
# define WTERMSIG(_X) ((_X).w_termsig)
# undef WCOREDUMP
# define WCOREDUMP(_X) ((_X).w_coredump)
# undef WSTOPSIG
# define WSTOPSIG(_X) ((_X).w_stopsig)
#endif /* _BSD */
#endif /* _SYS_WAIT_INCLUDED */
now looking at wait.h I thought maybe an #undef of _BSD would do also and
yes it works when I remove those 2 -D_BSD definitions from:
gcc -c -D_BSD -Demacs -DHAVE_CONFIG_H -DUSE_MOTIF -I. -I/vol/freeware/source/emacs-cvs/emacs/src -D_BSD -I/usr/include/X11R6 -I/usr/local/gnu/include -I/usr/include/X11R6 -I/usr/include/X11R5 -I/usr/include/Motif1.2 -I/usr/contrib/X11R6/include -I/usr/contrib/X11R5/include -g -O2 /vol/freeware/source/emacs-cvs/emacs/src/process.c
a quick grep for _BSD showed that this is hardly used, but set in Makefile,
so I removed it and emacs compiled fine (under HP-UX-B.11.11).
So maybe it would be a better idea to remove -D_BSD instead of
an undef of HAVE_SYS_WAIT_H
Richard> If you add #undef HAVE_SYS_WAIT_H to s/hpux11.h, does that make it
Richard> work?
Richard>
I've put it in s/hpux10.h since I had the same problems under 10.20 and yes
that works for 10.20 and 11.11, but as I said above I think it'd be
better to remove _BSD (for HP-UX 10.20 and above that is)
Klaus
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: kzeitler@lucent.com |
------------------------------------------
---
The economy depends about as much on economists as the weather
does on weather forecasters. -- Jean-Paul Kauffmann
next prev parent reply other threads:[~2002-07-29 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 18:43 syswait.h Richard Stallman
2002-07-26 18:52 ` syswait.h Andreas Schwab
2002-07-29 11:08 ` Klaus Zeitler [this message]
2002-07-30 0:59 ` syswait.h Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=q5gheiikd0n.fsf@lucent.com \
--to=kzeitler@lucent.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).