From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: git 565ebbf79f61873042c22a7126d002c104e056f4 broken on OpenBSD
Date: 26 Oct 2005 08:10:47 -0700 [thread overview]
Message-ID: <86mzkwfh54.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0510261708280.2803@wbgn013.biozentrum.uni-wuerzburg.de>
>>>>> "Johannes" == Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Johannes> Hi,
Johannes> On Wed, 26 Oct 2005, Randal L. Schwartz wrote:
Randal> sha1_file.c:1247: error: `ENOTSUP' undeclared (first use in this
>> function)
Johannes> I thought ENOTSUP is POSIX standard?
Johannes> What does your man page for link() say? If it is not supported, what value
Johannes> will be in errno?
EOPNOTSUPP
Probably a BSD thing.
--
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-26 15:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 14:11 git 565ebbf79f61873042c22a7126d002c104e056f4 broken on OpenBSD Randal L. Schwartz
2005-10-26 14:24 ` Randal L. Schwartz
2005-10-26 15:09 ` Johannes Schindelin
2005-10-26 15:10 ` Randal L. Schwartz [this message]
2005-10-26 15:26 ` Johannes Schindelin
2005-10-26 15:30 ` Randal L. Schwartz
2005-10-26 16:15 ` Jan Harkes
2005-10-26 16:46 ` Johannes Schindelin
2005-10-26 16:55 ` Jan Harkes
2005-10-26 17:03 ` Johannes Schindelin
2005-10-26 17:27 ` Linus Torvalds
2005-10-26 16:11 ` Linus Torvalds
2005-10-26 16:43 ` Johannes Schindelin
2005-10-26 17:22 ` Horst von Brand
2005-10-26 18:50 ` Randal L. Schwartz
2005-10-26 20:08 ` Junio C Hamano
2005-10-26 20:12 ` Randal L. Schwartz
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=86mzkwfh54.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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 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).