unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jca+emacs@wxcvbn.org (Jérémie Courrèges-Anglas)
To: emacs-devel@gnu.org
Subject: [24.3] possible build failure for list-system-processes on DragonFlyBSD
Date: Wed, 06 Mar 2013 03:28:11 +0100	[thread overview]
Message-ID: <87y5e1dzyc.fsf_-_@moo.wxcvbn.org> (raw)
In-Reply-To: <87d2vdfpj1.fsf@moo.wxcvbn.org> ("Jérémie Courrèges-Anglas"'s message of "Tue, 05 Mar 2013 23:30:26 +0100")

[-- Attachment #1: Type: text/plain, Size: 722 bytes --]


Same problem with DragonFlyBSD, which doesn't have KERN_PROC_PROC but
KERN_PROC_ALL and has switched to a flat kinfo_proc structure.

sys/sysctl.h (KERN_PROC_ALL)
http://gitweb.dragonflybsd.org/dragonfly.git/blob/HEAD:/sys/sys/sysctl.h

sys/kinfo.h (struct kinfo_proc)
http://gitweb.dragonflybsd.org/dragonfly.git/blob/HEAD:/sys/sys/kinfo.h

"Change kinfo_proc interface between kernel and userland."
http://gitweb.dragonflybsd.org/dragonfly.git/commit/5dfd06ac148512faf075c4e399e8485fd955578f

Perhaps should the list-system-processes function be enabled only on
targets where it is known to work?
-- 
Jérémie Courrèges-Anglas
GPG Key fingerprint: 61DB D9A0 00A4 67CF 2A90  8961 6191 8FBF 06A1 1494

[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2013-03-06  2:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-02 23:00 emacs-24.2.93 build problems Nelson H. F. Beebe
2013-03-03  0:09 ` 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                     ` Jérémie Courrèges-Anglas [this message]
2013-03-06  3:12                       ` [24.3] possible build failure for list-system-processes on DragonFlyBSD 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

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=87y5e1dzyc.fsf_-_@moo.wxcvbn.org \
    --to=jca+emacs@wxcvbn.org \
    --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).