From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Timo Hirvonen <tihirvon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: 1.3.2.gde1d fails to build on OpenBSD
Date: 15 May 2006 08:57:40 -0700 [thread overview]
Message-ID: <86bqtzth57.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20060515185819.ff05f6fe.tihirvon@gmail.com>
>>>>> "Timo" == Timo Hirvonen <tihirvon@gmail.com> writes:
>> I think you want
>>
>> #include <sys/types.h>
>>
>> on OpenBSD.
Timo> I think it should be #include <inttypes.h>. It works at least on BSD
Timo> and Linux.
Yes, that's present in OpenBSD.
--
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:[~2006-05-15 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 14:24 1.3.2.gde1d fails to build on OpenBSD Randal L. Schwartz
2006-05-15 15:58 ` Timo Hirvonen
2006-05-15 15:57 ` Randal L. Schwartz [this message]
2006-05-15 16:00 ` Linus Torvalds
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=86bqtzth57.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=tihirvon@gmail.com \
/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).