Thanks, that doesn't surprise me much, I've had many problems between 
Cygwin and git. Commenting out the line in juliarc.jl seems to get rid of 
the error, at least. Thanks.

On Friday, November 13, 2015 at 10:39:57 AM UTC-5, Tony Kelman wrote:
>
> Bummer, it looks like this is a consequence of 
> https://github.com/JuliaLang/julia/pull/13501 which I should have tested 
> more thoroughly. We upgraded the bundled version of command-line git from 
> Git 1.9.x to 2.6.x in the Windows binaries, hoping that it wouldn't cause 
> any problems. I did a bit of testing that Pkg would work properly, but 
> apparently forgot to try running the binaries from inside Cygwin. The 
> reason this is happening is because Git 2.x on Windows is now based on 
> MSYS2, which is a fork of Cygwin. Annoyingly, MSYS2's version of stty.exe 
> is incompatible and errors when you try to run it from within Cygwin. This 
> is why I wish MSYS2 and Cygwin could get along again and upstream all the 
> patches and just have MSYS2 be a runtime mode flag of an unmodified Cygwin, 
> but I may have to do the work on that myself to make it happen.
>
> Back to the point, you can try commenting out the contents of 
> etc/julia/juliarc.jl which adds the bundled version of Git to the path. 
> Beware though, Pkg doesn't really work properly with Cygwin's git if you've 
> got that installed. This might be a relatively easy fix but I haven't 
> really looked into what it would take to fix. What could also work is 
> running Git/git-bash.exe and launching `cygpath -w $PWD`/../bin/julia from 
> there.
>
>
> On Friday, November 13, 2015 at 7:24:02 AM UTC-8, Chris wrote:
>>
>> I just downloaded the 64-bit Windows v0.4.1 binary, but when I try to run 
>> it from Cygwin (my usual environment), I get the following error before it 
>> closes:
>>
>> stty: standard input: Inappropriate ioctl for device
>> ERROR: failed process: Process(`stty raw -echo onlcr -ocrnl opost`, 
>> ProcessExited(1)) [1]
>>  in pipeline_error at process.jl:555
>>
>> Any ideas?
>>
>> Thanks in advance.
>>
>

Reply via email to