emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs-24.2.93 build problems


From: Paul Eggert
Subject: Re: emacs-24.2.93 build problems
Date: Mon, 04 Mar 2013 18:17:50 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3

On 03/04/2013 04:42 PM, Nelson H. F. Beebe wrote:
> MirBSD is a derivative of NetBSD and OpenBSD, and often causes porting
> issues.
> 
> I then made this one-line tweak to your patch:
> 
>       %  diff sysdep.c.~1~ sysdep.c
>       2654c2654
>       < # ifndef KERN_PROC
>       ---
>       > # if !defined(KERN_PROC) || defined(__MirBSD__)

Thanks, I pushed this into emacs-24 as well, as bzr 111317.

=== modified file 'src/ChangeLog'
--- src/ChangeLog       2013-03-05 02:03:05 +0000
+++ src/ChangeLog       2013-03-05 02:15:35 +0000
@@ -1,8 +1,9 @@
 2013-03-05  Paul Eggert  <address@hidden>
 
-       Fix a build failure on OpenBSD 4.x.
-       * sysdep.c (KERN_PROC, kinfo_proc) [BSD_SYSTEM && !KERN_PROC]:
-       Define to KERN_PROC2 and kinfo_proc2, for OpenBSD 4.9.
+       Fix a build failure on OpenBSD 4.x and MirBSD.
+       * sysdep.c (KERN_PROC, kinfo_proc)
+       [BSD_SYSTEM && (!KERN_PROC || __MirBSD__)]:
+       Define to KERN_PROC2 and kinfo_proc2, for OpenBSD 4.9 and MirBSD.
        list-system-processes still returns nil, but at least it doesn't crash.
        Problem reported by Nelson H. F. Beebe in
        <http://lists.gnu.org/archive/html/emacs-devel/2013-03/msg00021.html>.

=== modified file 'src/sysdep.c'
--- src/sysdep.c        2013-03-05 02:03:05 +0000
+++ src/sysdep.c        2013-03-05 02:15:35 +0000
@@ -2650,8 +2650,9 @@
 #elif defined BSD_SYSTEM
 
 /* OpenBSD 4.9 and earlier do not have KERN_PROC.  Approximate it with
-   KERN_PROC2.  */
-# ifndef KERN_PROC
+   KERN_PROC2.  MirBSD's KERN_PROC seems to be busted.  */
+# if !defined KERN_PROC || defined __MirBSD__
+#  undef KERN_PROC
 #  define KERN_PROC KERN_PROC2
 #  define kinfo_proc kinfo_proc2
 # endif





reply via email to

[Prev in Thread] Current Thread [Next in Thread]