From: Ramsay Jones <ramsay@ramsay1•demon.co.uk>
To: Junio C Hamano <gitster@pobox•com>
Cc: Johannes Sixt <j.sixt@viscovery•net>,
GIT Mailing-list <git@vger•kernel.org>,
Marius Storm-Olsen <mstormo@gmail•com>
Subject: Re: [PATCH 1/4] MSVC: Fix an "unresolved symbol" linker error on cygwin
Date: Wed, 04 Nov 2009 20:20:13 +0000 [thread overview]
Message-ID: <4AF1E1FD.1050102@ramsay1.demon.co.uk> (raw)
In-Reply-To: <7veiogt4g8.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> How does Cygwin-ness of the build environment affect the end result when
> you build with MSVC?
Not at all. This is an MSVC/NO_MMAP combo problem. (The "problem" also exists
with the msvc build on msysGit[1])
> I am not a Windows person, so I am only guessing,
> but I suspect that the result does not pull any library nor crt0 from what
> people usually consider "Cygwin environment". It feels that the "default
> configuration of Cygwin" that insists on NO_MMAP is the guilty party here.
>
See patch #3.
> Shouldn't this be solved by teaching the Makefile about this new "Cygwin
> but using MSVC as compiler toolchain" combination?
Yes. Err... see patch #3 :-P
> [Footnote]
>
> *1* Notice "if" at the beginning of this sentence---I am not qualified to
> make a judgement without help from area experts here. Is it a sane thing
> to run Cygwin and still use MSVC as the compiler toolchain?
About as sane as running msysGit and still use MSVC as the compiler! :D
> Is it
> commonly done? I have no idea.
>
Nor me. I just tried it, and it works (after applying these patches!); for
exactly the same reason, and to the same extent, that it works on msysGit.
[Footnote]
*1* I admit to sometimes being a bit sloppy with naming (and maybe confused
also!). Now, IIUC, MinGW is basically gcc + binutils, MSYS is bash + some
unix tools and msysGit is MinGW + MSYS + some additional packages needed to
build and run git (eg perl). So, the "MinGW build" should really be called the
msysGit build ;-) (but the config section specifically picks out the MINGW string
from uname_S)
Also, the "msvc build on MinGW" should really be the "msvc build on msysGit".
Or something like that!
ATB,
Ramsay Jones
next prev parent reply other threads:[~2009-11-04 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 19:03 [PATCH 1/4] MSVC: Fix an "unresolved symbol" linker error on cygwin Ramsay Jones
2009-11-03 7:21 ` Johannes Sixt
2009-11-03 8:09 ` Junio C Hamano
2009-11-04 20:20 ` Ramsay Jones [this message]
2009-11-05 7:55 ` Johannes Sixt
2009-11-05 19:37 ` Junio C Hamano
2009-11-04 19:19 ` Ramsay Jones
2009-11-05 7:35 ` Johannes Sixt
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=4AF1E1FD.1050102@ramsay1.demon.co.uk \
--to=ramsay@ramsay1$(echo .)demon.co.uk \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=j.sixt@viscovery$(echo .)net \
--cc=mstormo@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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