threads / discuss / 6689

MinGW port now supports native git protocol

Subject: MinGW port now supports native git protocol

## tl;dr

3 messages between Feb 5, 2007 and Feb 6, 2007.

replies: 2people: 3as markdown or json

Johannes Sixt· Feb 5, 2007, 09:03 UTC · lore

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.

If you want to contribute, please consider using the 'mob' branch (see the gitweb summary page). Base your contributions on 'master'.

-- Hannes
Han-Wen Nienhuys· Feb 6, 2007, 14:42 UTC · re: Johannes Sixt · lore

Re: MinGW port now supports native git protocol

Johannes Sixt escreveu:
Show 11 quoted lines
> 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
Johannes Schindelin· Feb 6, 2007, 14:56 UTC · re: Han-Wen Nienhuys · lore

Re: MinGW port now supports native git protocol

Hi,
On Tue, 6 Feb 2007, Han-Wen Nienhuys wrote:
Show 9 quoted lines
> 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
> 
> [snip]
> 
> where are these headers supposed to come from?
>From git's compat/ directory.

As I see you also include sys/mman.h, I'd say that uname_S is probably not correctly set. ;-)

Yes, you found -- again -- that git is not easily cross-compilable.

Ciao, Dscho

← back to recent threads