From: Felipe Contreras <felipe.contreras@gmail.com>
To: Marat Radchenko <marat@slonopotamus.org>,
Felipe Contreras <felipe.contreras@gmail.com>
Cc: Marat Radchenko <marat@slonopotamus.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Sebastian Schuberth <sschuberth@gmail.com>,
Heiko Voigt <hvoigt@hvoigt.net>,
git@vger.kernel.org,
msysGit Mailinglist <msysgit@googlegroups.com>
Subject: RE: [NOT_A_PATCH] A naive attempt to cross-build Linux->mingw64 Git
Date: Mon, 21 Apr 2014 18:59:10 -0500 [thread overview]
Message-ID: <5355b0ce562b8_6c39e772f0cb@nysa.notmuch> (raw)
In-Reply-To: <1398118479-7731-1-git-send-email-marat@slonopotamus.org>
Marat Radchenko wrote:
> config.mak.uname: provide a way to explicitely request MinGW build.
> This is required to perform Linux->MinGW crosscompilation.
> ---
>
> > Personally I don't see why ideally I shouldn't be able to build upstream Git
> > for Windows with mingw without leaving my Linux system.
>
> One day you might be able, but as of today...
>
> 1. Obtain x86_64-w64-mingw32 compiler for your *nix distro
> * [Gentoo] emerge crossdev && crossdev -t x86_64-w64-mingw32
> * [Debian/Ubuntu] apt-get install mingw-w64
Note that I didn't say 64-bit. Baby steps, first the tried-and-true 32-bit compiler.
> 2. Apply patch from this email to Git sources (git/git or msysgit/git - doesn't matter)
Funny I came with almost exactly the same patch.
> 3. `make CC=x86_64-w64-mingw32-gcc MINGW=1`
I did:
% make CC=i486-mingw32-gcc NO_OPENSSL=1 NO_GETTEXT=1
But ideally it should be:
% make CROSS_COMPILE=i486-mingw32-
(or whatever the name of the suite)
> 4. Observe errors [1]
I see those errors with a 64-bit compiler, but not with the old 32-bit one.
> I would be happy to find out I'm doing something wrong -- Johannes says building
> mingw64 Git is dirt-easy.
I get the same error. I've been cross-compiling since basically all my
professional life, so I don't think you are doing something wrong, it just
doesn't work.
--
Felipe Contreras
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "msysGit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2014-04-22 0:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 13:35 [ANNOUNCE] WinGit - native x86/x64 Git for Windows Marat Radchenko
2014-04-19 17:01 ` Thomas Braun
2014-04-19 17:37 ` Johannes Schindelin
2014-04-19 18:42 ` Heiko Voigt
2014-04-19 21:12 ` Sebastian Schuberth
2014-04-20 22:10 ` [msysGit] " Johannes Schindelin
2014-04-20 22:12 ` Johannes Schindelin
2014-04-21 18:37 ` Sebastian Schuberth
2014-04-21 18:56 ` Johannes Schindelin
2014-04-21 18:56 ` Felipe Contreras
2014-04-21 22:14 ` [NOT_A_PATCH] A naive attempt to cross-build Linux->mingw64 Git Marat Radchenko
2014-04-21 23:59 ` Felipe Contreras [this message]
2014-04-22 0:06 ` Felipe Contreras
2014-04-22 13:36 ` Marat Radchenko
2014-04-22 16:08 ` Felipe Contreras
2014-04-22 13:36 ` Johannes Schindelin
2014-04-22 13:14 ` Re: Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows Johannes Schindelin
2014-04-22 14:17 ` David Kastrup
2014-04-22 16:00 ` Re: " Felipe Contreras
2014-04-22 16:14 ` Johannes Schindelin
2014-04-19 20:56 ` Sebastian Schuberth
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=5355b0ce562b8_6c39e772f0cb@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=marat@slonopotamus.org \
--cc=msysgit@googlegroups.com \
--cc=sschuberth@gmail.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).