Hi Gisle,
Am 19.07.2012 12:04, schrieb Gisle Vanem:
> "Guenter" <lists_at_gknw.net> wrote:
> I have 3 versions of 'sh' here. Only the Cygwin have problems with '\r\n'
> files. And that 'sh' is *newer* than the ones (i686-pc-msys, v. 3.1.17)
> that has no problems with this. A pathetic problem really.
What do you mean with "problems with '\r\n'" ?
Did you actually run an autobuild from GIT with MSYS?
Currently I dont believe that its a problem with the shell itself but
with something else like awk (I had no fun to further analyse which of
the countless tools autoconf/configure invokes excactly fails); the
issue is that autoconf/configure finishes fine but the curlbuild.h seems
then busted, causing the build itself to fail ...
So I would like to hear from you which setup you would suggest which
actually works when building from GIT ? Do you start the msys-git shell
and then mount the MinGW compiler into it?
Here's my (almost) latest script, pls give it a try and tell me how you
get GIT autobuilds flawlessly working *with* CRLF and LF line endings:
http://svwe10.itex.at/downloads/curltest/curl-autobuilds.tar.gz
BTW. this seems only to work on 32-bit; I'm currently testing on Win7
64-bit, and there I see more strange issues: I've added the path to git
to MinGW/MSYS, and although the path is correctly setup - means
MinGW/MSYS comes 1st before MSYS/Git - during autobuild magically mkdir
from MSYS/Git folder is called, causing the build to get hung (I see
that in task manager); once i kill that task build continues ...
so ATM I tend to remove the path to git and work with an alias instead ...
any further help getting autobuilds on Win7 64-bit going greatly
appreciated!

Gün.

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-07-19