[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PROPOSAL: Move to git, now that bzr is no longer a req.

From: Eli Zaretskii
Subject: Re: PROPOSAL: Move to git, now that bzr is no longer a req.
Date: Fri, 03 Jan 2014 23:11:23 +0200

> From: Óscar Fuentes <address@hidden>
> Date: Fri, 03 Jan 2014 21:37:08 +0100
> > I invoked 'make' from the Bash that was installed by msysgit.  That
> > 'make' hang.  The same command runs just fine from the MSYS Bash I use
> > for configuring and building packages.  That's a fact.  I think I know
> > the reasons, but if you want to disagree and live dangerously, that's
> > fine by me.
> IIUC you invoked MSYS `make' from MSYSGit `bash'. As I said multiple
> times, that's not expected to work.

Right, and that's why I keep the two segregated.  That was all I was
saying from day one: it's a PITA to have two similar, but incompatible
environments.  E.g., I cannot build a package from the same shell
where I "git pull" it.

> >> It would be quick enough to run some common git commands from MSYS shell
> >> to see if it works: clone, pull, status, log...
> >
> > I already tried, see above.
> No, you didn't. As git.exe does not depend on MSYS.dll, the problems you
> experienced with `make' shouldn't happen. And, indeed, invoking MSYSGit
> git.exe from a MSYS terminal worked fine for the commands I mentioned
> above.

Until that git.exe invokes a sub-command that needs Bash or Perl, and
will then invoke its own Bash pr Perl that need an incompatible
msys.dll (and other DLLs, like libiconv).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]