From: merlyn@stonehenge.com (Randal L. Schwartz)
To: git@vger.kernel.org
Subject: Re: git 565ebbf79f61873042c22a7126d002c104e056f4 broken on OpenBSD
Date: 26 Oct 2005 07:24:22 -0700 [thread overview]
Message-ID: <86u0f4fjah.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <86y84gfjv4.fsf@blue.stonehenge.com>
>>>>> "Randal" == Randal L Schwartz <merlyn@stonehenge.com> writes:
Randal> gcc -o sha1_file.o -c -g -O2 -Wall -I/usr/local/include -L/usr/local/lib -Dstrcasestr=gitstrcasestr -DNO_STRCASESTR=1 -DSHA1_HEADER='<openssl/sha.h>' sha1_file.c
Randal> sha1_file.c: In function `move_temp_to_file':
Randal> sha1_file.c:1247: error: `ENOTSUP' undeclared (first use in this function)
Randal> sha1_file.c:1247: error: (Each undeclared identifier is reported only once
Randal> sha1_file.c:1247: error: for each function it appears in.)
Randal> gmake: *** [sha1_file.o] Error 1
got it... a bit messy, but here it is:
Subject: [PATCH] fix for openbsd
---
sha1_file.c | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)
applies-to: b16bae041dfd1c1081873f2e88a5f82858fb2051
28dcc3eaf13856585a81a24f1b4393032f825053
diff --git a/sha1_file.c b/sha1_file.c
index 7fdc469..1079ca5 100644
--- a/sha1_file.c
+++ b/sha1_file.c
@@ -1244,7 +1244,11 @@ int move_temp_to_file(const char *tmpfil
* When this succeeds, we just return 0. We have nothing
* left to unlink.
*/
- if ((ret == EXDEV || ret == ENOTSUP) && !rename(tmpfile, filename))
+ if ((ret == EXDEV
+#ifdef ENOTSUP
+ || ret == ENOTSUP
+#endif
+ ) && !rename(tmpfile, filename))
return 0;
ret = errno;
}
---
0.99.8.GIT
--
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 14:25 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 [this message]
2005-10-26 15:09 ` Johannes Schindelin
2005-10-26 15:10 ` Randal L. Schwartz
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=86u0f4fjah.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--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).