From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: git@vger.kernel.org
Subject: Re: MinGW port now supports native git protocol
Date: Tue, 06 Feb 2007 15:42:15 +0100 [thread overview]
Message-ID: <45C893C7.6050001@xs4all.nl> (raw)
In-Reply-To: <45C6F2F6.ADFE0A13@eudaptics.com>
Johannes Sixt escreveu:
> Thanks to H. Peter Anvin's tips, the MinGW port now also supports clone,
> fetch, pull via the native git protocol. Visit
>
> gitweb: http://repo.or.cz/w/git/mingw.git
> Clone/pull: git://repo.or.cz/git/mingw.git
> A Readme:
> http://repo.or.cz/w/git/mingw.git?a=blob_plain;f=README.MinGW;hb=master
>
> Please try branch 'master' first, and if this does not compile or does
> not work in some way, try branch 'devel', which contains a few extra
> patches that I need on my system to make it work.
Out of curiosity (and probably: repressed masochism), I decided to
give this a whirl inside my cross-building environment.
Trying to build this yields
building package: mingit
*** Stage: compile (mingit)
invoking cd /home/lilydev/vc/gub/target/mingw/build/mingit-master-repo.or.cz-git-mingw.git && make -j2
i686-mingw32-gcc -mwindows -mms-bitfields -o fetch-pack.o -c -g -O2 -DNO_OPENSSL -DNO_D_TYPE_IN_DIRENT -DNO_C99_FORMAT -DNO_IPV6 -Dsockaddr_storage=sockaddr_in -DNO_ICONV -DSHA1_HEADER='"mozilla-sha1/sha1.h"' -DNO_STRCASESTR -DNO_STRLCPY -DNO_SETENV fetch-pack.c
i686-mingw32-gcc -mwindows -mms-bitfields -o blob.o -c -g -O2 -DNO_OPENSSL -DNO_D_TYPE_IN_DIRENT -DNO_C99_FORMAT -DNO_IPV6 -Dsockaddr_storage=sockaddr_in -DNO_ICONV -DSHA1_HEADER='"mozilla-sha1/sha1.h"' -DNO_STRCASESTR -DNO_STRLCPY -DNO_SETENV blob.c
In file included from cache.h:4,
from fetch-pack.c:1:
git-compat-util.h:39:21: error: fnmatch.h: No such file or directory
git-compat-util.h:48:19: error: netdb.h: No such file or directory
git-compat-util.h:49:17: error: pwd.h: No such file or directory
git-compat-util.h:52:17: error: grp.h: No such file or directory
git-compat-util.h:105:22: error: sys/mman.h: No such file or directory
(etc)
Are you sure that this builds with Mingw only? I have
binutils 2.16.1
gcc 4.1.1
regex 2.3.90-1
w32api 3.6
zlib 1.2.2
libtool 1.5.20
mingw-runtime 3.9
where are these headers supposed to come from?
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2007-02-06 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 9:03 MinGW port now supports native git protocol Johannes Sixt
2007-02-06 14:42 ` Han-Wen Nienhuys [this message]
2007-02-06 14:56 ` Johannes Schindelin
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=45C893C7.6050001@xs4all.nl \
--to=hanwen@xs4all.nl \
--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 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.