From: "Nelson H. F. Beebe" <beebe@math.utah.edu>
To: emacs-devel@gnu.org
Cc: beebe@math.utah.edu
Subject: emacs-24.2.93 build problems
Date: Sat, 2 Mar 2013 16:00:47 -0700 (MST) [thread overview]
Message-ID: <CMM.0.94.0.1362265247.beebe@psi.math.utah.edu> (raw)
I have spent much of today in build attempts for emacs-24.2.93 on
about 25 flavors of Unix in our lab. After a lot of restarts, I have
mostly succeeded, except for two platforms: OpenBSD 4.9 on x86, and
MirOS 10 on x86. On those two systems, compilation of src/sysdep.c
fails like this:
sysdep.c: In function 'list_system_processes':
sysdep.c:2656: error: 'KERN_PROC' undeclared (first use in this function)
sysdep.c:2656: error: (Each undeclared identifier is reported only once
sysdep.c:2656: error: for each function it appears in.)
sysdep.c:2684: error: 'struct kinfo_proc' has no member named 'p_pid'
Both systems previously had emacs-24.1 installed. A similar build of
emacs-24.2.93 on OpenBSD 5.1 was successful.
Examination of the source code reveals the problem: function
list_system_processes() is delving into kernel data structures defined
in <kvm.h> which in turn includes <sys/sysctl.h>, and that header file
defines kernel data structures that list_system_processes() attempts
to reference.
In OpenBSD 5.1, p_pid is in struct kinfo_proc, but on the other two
systems, p_pid is instead in struct kinfo_proc2. There is no support
code in list_system_processes() for that alternative, and no test for
it in configure either.
By contrast, the emacs-24.1 version of list_system_processes() has no
reference to the kinfo_proc* structs.
On request, I can provide off-list pointers to copies of sysctl.h for
the two failing systems.
Although some might argue that because OpenBSD 5.x is available,
OpenBSD 4.x is no longer of interest, I do not hold that view. Emacs
has been around now for almost 40 years, and for the last 30 or so,
its portability has been held in high regard. As a result, it is
available on, or has been ported to, all common desktop and mobile
platforms, even non-Unix ones. I prefer to see that portability
continue. Emacs is what makes computers usable in much the same way,
no matter what the underlying O/S platform is.
-------------------------------------------------------------------------------
- Nelson H. F. Beebe Tel: +1 801 581 5254 -
- University of Utah FAX: +1 801 581 4148 -
- Department of Mathematics, 110 LCB Internet e-mail: beebe@math.utah.edu -
- 155 S 1400 E RM 233 beebe@acm.org beebe@computer.org -
- Salt Lake City, UT 84112-0090, USA URL: http://www.math.utah.edu/~beebe/ -
-------------------------------------------------------------------------------
next reply other threads:[~2013-03-02 23:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 23:00 Nelson H. F. Beebe [this message]
2013-03-03 0:09 ` emacs-24.2.93 build problems Paul Eggert
2013-03-04 20:34 ` Glenn Morris
2013-03-04 23:44 ` Jérémie Courrèges-Anglas
2013-03-05 3:47 ` Glenn Morris
2013-03-05 14:00 ` Jérémie Courrèges-Anglas
2013-03-05 14:52 ` emacs-24.2.93 build problems (on OpenBSD) Jérémie Courrèges-Anglas
2013-03-05 20:06 ` Glenn Morris
2013-03-05 17:06 ` emacs-24.2.93 build problems Glenn Morris
2013-03-05 17:24 ` list-system-processes on OpenBSD [was Re: emacs-24.2.93 build problems] Glenn Morris
2013-03-05 17:36 ` Paul Eggert
2013-03-05 20:42 ` list-system-processes on OpenBSD Glenn Morris
2013-03-05 21:57 ` Paul Eggert
2013-03-05 22:30 ` Jérémie Courrèges-Anglas
2013-03-06 0:38 ` [24.3] possible build failure for list-system-processes on NetBSD Jérémie Courrèges-Anglas
2013-03-06 2:28 ` [24.3] possible build failure for list-system-processes on DragonFlyBSD Jérémie Courrèges-Anglas
2013-03-06 3:12 ` Glenn Morris
2013-03-06 5:07 ` Paul Eggert
2013-03-06 7:30 ` Glenn Morris
2013-03-06 2:31 ` list-system-processes on OpenBSD [was Re: emacs-24.2.93 build problems] Leo Liu
2013-03-04 23:51 ` emacs-24.2.93 build problems Glenn Morris
2013-03-05 2:06 ` Paul Eggert
[not found] <CMM.0.94.0.1362444120.beebe@psi.math.utah.edu>
2013-03-05 2:17 ` Paul Eggert
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=CMM.0.94.0.1362265247.beebe@psi.math.utah.edu \
--to=beebe@math.utah.edu \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.