From: "Dmitry Kakurin" <dmitry.kakurin@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Marius Storm-Olsen" <marius@trolltech.com>, git@vger.kernel.org
Subject: Re: MinGW build environment for Git
Date: Wed, 1 Aug 2007 15:18:41 -0700 [thread overview]
Message-ID: <a1bbc6950708011518n63968dc0see8a022d2934cba8@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708011143180.14781@racer.site>
On 8/1/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Wed, 1 Aug 2007, Dmitry Kakurin wrote:
>
> > On 7/31/07, Marius Storm-Olsen <marius@trolltech.com> wrote:
> > > Dmitry Kakurin said the following on 30.07.2007 01:14:
> > > > I want to be able to build MinGW port of Git on Windows. I've tried
> > > > to follow steps in README.MinGW to setup this environment myself
> > > > (install MinGW, MSys, ZLib etc.) but after wasting a lot of time
> > > > with no result I give up. So, could somebody please just pkzip
> > > > their environment (everything required) and share the zip file with
> > > > me (privately or publicly)? I also think that an even better idea
> > > > is to create a new Git repository with MinGW build environment.
> > > > This will make contributing to MinGW port of Git MUCH easier.
> > >
> > > Aaron has done this, and you can find the link on his blog, here:
> > > http://www.ekips.org/cgi-bin/aaron.cgi/2007/02/27
> >
> > I've downloaded and installed it. But I could not make it work :-(.
> > First I had this problem:
> > $ make
> > GIT_VERSION = 1.5.3.GIT
> > * new build flags or prefix
> > CC convert-objects.o
> > gcc.exe: installation problem, cannot exec `cc1': No such file or directory
> > make: *** [convert-objects.o] Error 1
> >
> > Then I've copied cc1.exe and some others from
> > C:\mingw4git\libexec\gcc\mingw32 into /bin.
> >
> > $ make
> > CC convert-objects.o
> > In file included from cache.h:4,
> > from convert-objects.c:1:
> > git-compat-util.h:51:22: sys/wait.h: No such file or directory
> >
> > Searching entire (downloaded) tree for wait.h gives nothing.
> >
> > 'make configure' does not work:
> > $ make configure
> > GEN configure
> > configure.ac+:4: error: Autoconf version 2.59 or higher is required
> > configure.ac+:4: the top level
> > autom4te: /bin/m4 failed with exit status: 1
> > make: *** [configure] Error 1
> >
> > What do I do now?
>
> This looks like you downloaded git.git. Official releases do not have
> MinGW support yet! You have to get the MinGW port from repo.or.cz:
>
> http://repo.or.cz/w/git/mingw.git
You were right. I was downloading Git under Cygwin and then copied it
to MSys. Somewhere along the way I got confused and copied the wrong
directory.
It works now!
Thank you!
- Dmitry
prev parent reply other threads:[~2007-08-01 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 23:14 MinGW build environment for Git Dmitry Kakurin
2007-08-01 5:15 ` Marius Storm-Olsen
2007-08-01 9:08 ` Dmitry Kakurin
2007-08-01 10:44 ` Johannes Schindelin
2007-08-01 22:18 ` Dmitry Kakurin [this message]
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=a1bbc6950708011518n63968dc0see8a022d2934cba8@mail.gmail.com \
--to=dmitry.kakurin@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=marius@trolltech.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).