On 9/5/19 9:26 PM, Eric Blake wrote:
> Rather, go is not passing the command line to CreateProcess in the way
> that is unambiguously parseable in the manner expected by
> CommandLineToArgvW.
The specific example I gave is unambiguous and is parsed correctly by
CommandLineToArgvW, so if the goal i
On Thu, Sep 5, 2019 at 8:23 PM Ken Brown wrote:
> 3.1.0-0.3 had some bugs that were fixed in today's 3.1.0-0.4 release. Please
> report back after trying it.
I'm glad to hear this, because I upgraded to 3.1.0-0.4 at work today
and could not duplicate the problem. I just upgraded at home and was
On 9/5/2019 2:11 PM, Jim Reisert AD1C wrote:
> Since I started using this version, I've been having some strange
> hangs running g++ (called from make). The compilation just hangs
> (probably at the link stage). The .o file is generated but the .exe
> is not. If I remove the .o file and try agai
On 9/5/19 6:45 PM, Stephen Provine via cygwin wrote:
>
> To prove it is not going through cmd.exe, I debugged the Go program
> to the point that it calls the Win32 CreateProcess function, and the
> first two arguments are:
>
> lpApplicationName: "C:\\cygwin64\\bin\\bash.exe"
> lpCommandLine: "C:
On Thu, 5 Sep 2019 23:45:44, "Stephen Provine via cygwin" wrote:
package main
import (
"log"
"os"
"os/exec"
)
func main() {
cmd :=3D exec.Command("C:\\cygwin64\\bin\\bash.exe", "test.sh", "foo",
"ba=
r\"baz", "bat")
cmd.Stdout =3D os.Stdout
cmd.S
On 9/5/19 5:46 PM, Eric Blake wrote:
> If you start a cygwin process from Windows, then cygwin1.dll is given
> only a single string, which it must parse into argv according to windows
> conventions (if it does not produce the same argv[] as a windows process
> using CommandLineToArgvW, then that's
On 9/5/19 5:01 PM, Stephen Provine via cygwin wrote:
> On 9/5/19 2:05 PM, Eric Blake wrote:
>> On 9/5/19 1:31 PM, Stephen Provine via cygwin wrote:
>>> Not expected.
>
>> Why not? That obeyed cmd's odd rules: The moment you have a " in the
>> command line, that argument continues until end of lin
On 9/5/19 2:05 PM, Eric Blake wrote:
> On 9/5/19 1:31 PM, Stephen Provine via cygwin wrote:
> > Not expected.
> Why not? That obeyed cmd's odd rules: The moment you have a " in the
> command line, that argument continues until end of line or the next "
> (regardless of how many \ precede the ").
The following packages have been uploaded to the Cygwin distribution:
* libwx_baseu3.0_0-3.0.4-1
* libwx_baseu3.0-devel-3.0.4-1
* libwx_gtk2u3.0_0-3.0.4-1
* libwx_gtk2u3.0-devel-3.0.4-1
* libwx_gtk3u3.0_0-3.0.4-1
* libwx_gtk3u3.0-devel-3.0.4-1
* wxWidgets3.0-doc-3.0.4-1
wxWidgets is a set of libr
On 9/5/19 1:31 PM, Stephen Provine via cygwin wrote:
> My mistake - I'm very aware of the quoting rules, yet in my test script for
> this
> scenario I forgot to quote the arguments. However, if POSIX rules are being
> implemented, there is still something I didn't expect. Here's my bash script:
>
On 2019-09-04 23:29, Brian Inglis wrote:
> As standard on Unix systems, just add another level of quoting for each level
> of
> interpretation, as bash will process that command line, then bash will process
> the script command line.
My mistake - I'm very aware of the quoting rules, yet in my tes
Since I started using this version, I've been having some strange
hangs running g++ (called from make). The compilation just hangs
(probably at the link stage). The .o file is generated but the .exe
is not. If I remove the .o file and try again, sometimes it works.
I had been running the August
The following packages have been uploaded to the Cygwin distribution:
* dri-drivers-19.1.6-1
* libglapi0-19.1.6-1
* libGL1-19.1.6-1
* libGL-devel-19.1.6-1
* libOSMesa8-19.1.6-1
* libOSMesa-devel-19.1.6-1
* libEGL1-19.1.6-1
* libEGL-devel-19.1.6-1
* libGLESv2_2-19.1.6-1
* libGLESv2-devel-19.1.6-1
*
The following packages have been uploaded to the Cygwin distribution
as test releases:
* cygwin-3.1.0-0.4
* cygwin-devel-3.1.0-0.4
* cygwin-doc-3.1.0-0.4
This release comes with a couple of new features and quite a few
bug fixes.
The most interesting changes:
- A revamp of the old FIFO code. I
Thanks for the tip - I already had logger installed, but without syslog-ng,
it doesn't seem to create windows events.
I also discovered that I had to run passwd -R in order to get createevent
to work from a cygwin mintty session.
On Thu, Sep 5, 2019 at 12:12 AM Brian Inglis <
brian.ing...@systema
Hello,
After installing the latest updates to cygwin, including the new X
server, openGL libraries, and mesa, I'm having issues with a configure
script that was previously working. It no longer finds the openGL
libraries. Additionally, the xwin server refuses to start if more than
one display is p
W dniu 2019-09-05 09:14, Csaba Raduly napisał(a):
Hi Lukasz,
Please don't top-post on this list.
On Thu, Sep 5, 2019 at 8:49 AM Lukasz Swierczewski wrote:
Thanks!
It looks like it works ...
You can tell where I can find:
#include
#include
Have you tried a Linux system ?
Csaba
I use
Hi Lukasz,
Please don't top-post on this list.
On Thu, Sep 5, 2019 at 8:49 AM Lukasz Swierczewski wrote:
>
> Thanks!
>
> It looks like it works ...
>
> You can tell where I can find:
>
> #include
> #include
Have you tried a Linux system ?
Csaba
--
You can get very substantial performance im
18 matches
Mail list logo
