From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: New Git v2.0.4 build to test
Date: Wed, 06 Aug 2014 14:18:00 -0000 [thread overview]
Message-ID: <20140806141841.GM13601@calimero.vinschen.de> (raw)
In-Reply-To: <20140806102147.GB991@dinwoodie.org>
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
Hi Adam,
On Aug 6 11:21, Adam Dinwoodie wrote:
> Hi all,
>
> I'm in the long-running process of producing an up-to-date build of Git
> for Cygwin. I think I'm now (finally) close to having a build ready to
> upload to be installed via the Cygwin setup programs, but in the
> meantime I'd appreciate my new build getting some additional testing.
>
> You can download my latest build of Git v2.0.4 at
> http://tastycake.net/~adam/cygwin/.
>
> To install, download the package(s) you're interested in using, and
> unpack them using `tar -xaC/ -f <tarball-name>` from a Cygwin shell.
> Make sure to check the corresponding setup.hint files to ensure you have
> all the required dependencies first.
>
> This build isn't final, but it does work in at least the mainline use
> cases; I've been using it for a couple of days for my day-to-day work.
> However there are still some problems I'm aware of (no `git grep -P`
> support,
Sounds like libpcre-devel is missing on your machine.
> `git fetch` occasionally hangs in the test suites in 64-bit)
> and there are probably some problems I haven't identified yet.
>
> I'm currently in the process of working through the Git test suite
> output to identify missing features, since it's the best way I've found
> to identify features the Git compile process has quietly skipped since a
> required library wasn't installed.
If the git build system uses autotools, you might have an easier time by
scanning the config.log file created during the configure call.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-06 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 10:21 Adam Dinwoodie
2014-08-06 14:18 ` Corinna Vinschen [this message]
2014-08-06 15:02 ` JonY
2014-08-06 23:15 ` Adam Dinwoodie
2014-08-07 3:08 ` Robert Bu
2014-08-10 21:24 ` Adam Dinwoodie
2014-08-11 1:48 ` Robert Bu
2014-08-11 10:47 ` Corinna Vinschen
2014-08-12 8:15 ` Achim Gratz
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=20140806141841.GM13601@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).