git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: daemon.c broken on OpenBSD
Date: 25 Oct 2005 16:29:09 -0700	[thread overview]
Message-ID: <86vezljhve.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <7v64rnsd83.fsf@assigned-by-dhcp.cox.net>


I can confirm that the following patch lets the current origin
compile on OpenBSD.  If you could apply this until you sort out the
rest of the namespace issue, I would be happy.  Thanks.

diff --git a/daemon.c b/daemon.c
index 0c6182f..c3f8641 100644
--- a/daemon.c
+++ b/daemon.c
@@ -1,5 +1,3 @@
-#include "cache.h"
-#include "pkt-line.h"
 #include <signal.h>
 #include <sys/wait.h>
 #include <sys/socket.h>
@@ -9,6 +7,8 @@
 #include <netinet/in.h>
 #include <arpa/inet.h>
 #include <syslog.h>
+#include "pkt-line.h"
+#include "cache.h"
 
 static int log_syslog;
 static int verbose;


-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

  parent reply	other threads:[~2005-10-25 23:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24  4:06 daemon.c broken on OpenBSD Randal L. Schwartz
2005-10-24  5:20 ` Junio C Hamano
2005-10-24 14:03   ` Matthias Urlichs
2005-10-25 23:29   ` Randal L. Schwartz [this message]
2005-10-25 23:32     ` Randal L. Schwartz
2005-10-25 23:40       ` Randal L. Schwartz
2005-10-24 16:02 ` Linus Torvalds
2005-10-24 16:06   ` Randal L. Schwartz
2005-10-24 16:43     ` Linus Torvalds
2005-10-24 17:04       ` H. Peter Anvin
2005-10-24 17:14       ` Linus Torvalds
2005-10-24 17:26         ` H. Peter Anvin
2005-10-24 17:58           ` Linus Torvalds
2005-10-24 18:03             ` H. Peter Anvin
2005-10-24 18:25               ` Morten Welinder
2005-10-24 20:59           ` Junio C Hamano

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=86vezljhve.fsf@blue.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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;
as well as URLs for NNTP newsgroup(s).