From: Eric Blake <ebb9@byu.net>
To: git@vger.kernel.org
Subject: git on cygwin
Date: Sat, 25 Nov 2006 07:38:23 -0700 [thread overview]
Message-ID: <4568555F.8050500@byu.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I found the following patch useful for building git 1.4.4.1 on cygwin. As
of cygwin-1.5.22, C99 format strings are now supported (since I
contributed the newlib patch that added them). As of cygwin-1.5.21, d_ino
is now reliable for all cygwin filesystem accesses (except for some remote
NetApp drives, which have been fixed in cygwin CVS). And while it is true
that native Windows does not support symlinks, making NO_SYMLINK_HEAD a
good idea for native builds; this is not the case for cygwin, and I did
not seem to have any problems with removing it, either.
- --- origsrc/git-1.4.4.1/Makefile 2006-11-22 19:38:07.000000000 -0700
+++ src/git-1.4.4.1/Makefile 2006-11-24 17:51:00.600344000 -0700
@@ -369,11 +369,8 @@
endif
ifeq ($(uname_O),Cygwin)
NO_D_TYPE_IN_DIRENT = YesPlease
- - NO_D_INO_IN_DIRENT = YesPlease
NO_STRCASESTR = YesPlease
- - NO_SYMLINK_HEAD = YesPlease
NEEDS_LIBICONV = YesPlease
- - NO_C99_FORMAT = YesPlease
# There are conflicting reports about this.
# On some boxes NO_MMAP is needed, and not so elsewhere.
# Try uncommenting this if you see things break -- YMMV.
- --
Life is short - so eat dessert first!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFaFVe84KuGfSFAYARAjdrAJ9A+d9/aaEG0V2j8VTs/oycIpUS0wCeL/Ly
70V5CWHOrAKD7kI09gQiTh0=
=C8dP
next reply other threads:[~2006-11-25 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-25 14:38 Eric Blake [this message]
2006-11-25 14:58 ` git on cygwin Jakub Narebski
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=4568555F.8050500@byu.net \
--to=ebb9@byu.net \
--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