On Sat, 23 Feb 2019 05:54:18, Doug Henderson wrote:
> On Fri, 22 Feb 2019 at 17:01, Glyn Gowing <> wrote:
> > I have a program (attached) that works correctly on my mac but does
> > not work with Cygwin on Windows 10. I'm running the latest version of
[snip]
> On further analysis, the call to
>
Dear Cygwin,
My name is Lincoln...
If you're using PPC advertising as a major marketing strategy
but the negative customer reactions are already working against you,
it is natural, visit our website and feel free placing your page
on top of search engines.
Let me show you online demo in 3 easy
On 2/24/2019 9:23 PM, Ken Brown wrote:
> On 2/24/2019 2:52 PM, Corinna Vinschen wrote:
>> On Feb 24 20:09, Corinna Vinschen wrote:
>>> On Feb 24 19:55, Corinna Vinschen wrote:
On Feb 24 17:27, Ken Brown wrote:
> I'm seeing sporadic errors like this on 64-bit Cygwin when I first start
On 2/24/2019 2:52 PM, Corinna Vinschen wrote:
> On Feb 24 20:09, Corinna Vinschen wrote:
>> On Feb 24 19:55, Corinna Vinschen wrote:
>>> On Feb 24 17:27, Ken Brown wrote:
I'm seeing sporadic errors like this on 64-bit Cygwin when I first start
emacs:
0 [main] emacs-X11
On Sat, 2019-02-23 at 16:29 -0800, Steven Penny wrote:
> I noticed that "python36" requires "binutils".
This is needed for ctypes.util.find_library(). FWIW, on Linux, not
only binutils is used, but also gcc.
> Further, I noticed this dependency chain:
>
> python36 > libuuid-devel > pkg-conf
On Feb 24 20:09, Corinna Vinschen wrote:
> On Feb 24 19:55, Corinna Vinschen wrote:
> > On Feb 24 17:27, Ken Brown wrote:
> > > I'm seeing sporadic errors like this on 64-bit Cygwin when I first start
> > > emacs:
> > >
> > >0 [main] emacs-X11 864 C:\cygwin64\bin\emacs-X11.exe: *** fatal
On Feb 24 19:55, Corinna Vinschen wrote:
> On Feb 24 17:27, Ken Brown wrote:
> > I'm seeing sporadic errors like this on 64-bit Cygwin when I first start
> > emacs:
> >
> >0 [main] emacs-X11 864 C:\cygwin64\bin\emacs-X11.exe: *** fatal
> > error in
> > forked process - Can't recreate sh
On Feb 24 08:57, Mike Gran via cygwin wrote:
> On Sun, Feb 24, 2019 at 10:18:58AM +0100, Corinna Vinschen wrote:
> > On Feb 23 22:58, Mike Gran via cygwin wrote:
> > > Hi-
> > >
> > > There is an unusual behaviour with setitimer/getitimer and I'm not
> > > sure if it is a bug or not.
> > >
> > >
On Feb 24 17:27, Ken Brown wrote:
> I'm seeing sporadic errors like this on 64-bit Cygwin when I first start
> emacs:
>
>0 [main] emacs-X11 864 C:\cygwin64\bin\emacs-X11.exe: *** fatal error
> in
> forked process - Can't recreate shared timerfd section during fork!
>0 [main] ema
On Sun, Feb 24, 2019 at 10:18:58AM +0100, Corinna Vinschen wrote:
> On Feb 23 22:58, Mike Gran via cygwin wrote:
> > Hi-
> >
> > There is an unusual behaviour with setitimer/getitimer and I'm not
> > sure if it is a bug or not.
> >
> > Basically, if I call setitimer to set an SIGALRM, and then ca
--- jsm
> I want to terminate this discussion, originating from my concern for
> consistency among distribution providers.
>
> Originally I reported on a successful installation of basic Cygwin, i.e.
> without X, followed by a failing attempt to install X. Of course I have
> been aware all the
On Feb 23 22:58, Mike Gran via cygwin wrote:
> Hi-
>
> There is an unusual behaviour with setitimer/getitimer and I'm not
> sure if it is a bug or not.
>
> Basically, if I call setitimer to set an SIGALRM, and then call
> getitimer *after* the alarm goes off, I rather expect the time I
> receive
On Feb 23 22:52, Ken Brown wrote:
> On 2/23/2019 5:11 PM, Corinna Vinschen wrote:
> > On Feb 23 21:24, Ken Brown wrote:
> >> On 2/23/2019 4:01 PM, Corinna Vinschen wrote:
> >>> On Feb 23 20:48, Ken Brown wrote:
> On 2/23/2019 2:15 PM, Corinna Vinschen wrote:
> > Below's the NSSTC I used to
13 matches
Mail list logo
