From: Johannes Sixt <j.sixt@viscovery.net>
To: dhruva <dhruvakm@gmail.com>
Cc: Git <git@vger.kernel.org>, msysGit <msysgit@googlegroups.com>
Subject: Re: git build on msys fails (and fix)
Date: Mon, 01 Dec 2008 10:06:42 +0100 [thread overview]
Message-ID: <4933A922.7080300@viscovery.net> (raw)
In-Reply-To: <e3f230850811300302y68992b9doe4897d97d513de3a@mail.gmail.com>
dhruva schrieb:
> Hello,
> I build git on msys environment regularly. With the recent changes to
> add cache preload facility (commit ID:
> 671c9b7e315db89081cc69f83a8f405e4aca37bc) brings in dependency on
> pthreads. This is not available in the msys distribution which was
> part of the git build distro. I installed libpthread for mingw to get
> the related headers and libraries. I had to make some minor changes to
> libpthread installation. I copied the 'setjmp.h' from my other mingw
> installation and had to had edit it to remove some mingw specific
> macros.
>
> @:/e/users/dhruva/stub/repo/git/git
> [520]$ diff -u /e/tools/gnu/include/setjmp.h /mingw/include/setjmp.h
> --- /e/tools/gnu/include/setjmp.h Sun Oct 5 04:01:15 2008
> +++ /mingw/include/setjmp.h Sun Nov 30 16:18:00 2008
> @@ -36,7 +36,7 @@
> * The function provided by CRTDLL which appears to do the actual work
> * of setjmp.
> */
> -_CRTIMP int __cdecl __MINGW_NOTHROW _setjmp (jmp_buf);
> +int __cdecl _setjmp (jmp_buf);
>
> #define setjmp(x) _setjmp(x)
>
> @@ -44,7 +44,7 @@
> * Return to the last setjmp call and act as if setjmp had returned
> * nVal (which had better be non-zero!).
> */
> -_CRTIMP void __cdecl __MINGW_NOTHROW longjmp (jmp_buf, int)
> __MINGW_ATTRIB_NORETURN;
> +void __cdecl longjmp (jmp_buf, int);
>
> #ifdef __cplusplus
> }
>
> Also,
> had to copy a pthread library with a dfferent name to the standard name:
> $cp libpthreadGC2.a libpthread.a
>
> The build went fine and am using the new binaries.
Would you please push your addition to the mob branch of
git://repo.or.cz/msysgit.git? The push URL is repo.or.cz:/srv/git/msysgit.git
(But notice that some commits are on the mob branch currently that are not
in any other branch; hence, you better build on top of them so that they
are not lost when you push to mob.)
-- Hannes
next prev parent reply other threads:[~2008-12-01 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-30 11:02 git build on msys fails (and fix) dhruva
2008-11-30 11:52 ` dhruva
2008-12-01 9:06 ` Johannes Sixt [this message]
2008-12-01 9:32 ` dhruva
2008-12-01 10:52 ` dhruva
2008-12-01 11:48 ` dhruva
2008-12-01 11:57 ` Johannes Sixt
2008-12-01 12:02 ` dhruva
2008-12-01 13:07 ` dhruva
2008-12-01 13:30 ` [msysGit] " dhruva
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=4933A922.7080300@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=dhruvakm@gmail.com \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
/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).