From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: daemon.c broken on OpenBSD
Date: 24 Oct 2005 09:06:06 -0700 [thread overview]
Message-ID: <86irvmzyq9.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0510240901020.10477@g5.osdl.org>
>>>>> "Linus" == Linus Torvalds <torvalds@osdl.org> writes:
Linus> We're doing our own ctype.h.
Linus> The fix is to make sure that "cache.h" is included _after_ system
Linus> includes.
That probably won't work, because on OpenBSD, it's not a #define, but
rather a real function call. You can't just #undef that (unless my C
is even more rusty).
--
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!
next prev parent reply other threads:[~2005-10-24 16:06 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
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 [this message]
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=86irvmzyq9.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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.
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.