The following packages have been updated:
- poco-1.4.6p3-1
- libpoco-devel-1.4.6p3-1
- libpoco-doc-1.4.6p3-1
- libpoco16-1.4.6p3-1
- poco-debuginfo-1.4.6p3-1
This release contains a security fix in the X509 certificate handling
code, but is otherwise identical to poco-1.4.6p2.
DESCRI
On 4/2/2014 5:03 PM, Colin wrote:
> Hi Team,
Team? This is a user's forum.
[snip]
> The problem I have can be reduced to this: I compile a simple "Hello
> World" console mode c program. I copy the .exe file and cygwin1.dll onto
> an embedded PC, open a console window, and run the program. The
Corinna Vinschen wrote:
Could you please send the link to the PR to this thread?
Obviosly... I just hope I did everything right.
This should be PR binutils/16807, i.e.
https://sourceware.org/bugzilla/show_bug.cgi?id=16807
Ciao,
Angelo.
--
Problem reports: http://cygwin.com/problems.
Hi Team,
I'm new here, but have dabbled in Cygwin for a few years. I hope someone
more knowledgeable than myself can help with with this issue which is
quite frankly baffling me for the past few weeks.
The problem I have can be reduced to this: I compile a simple "Hello
World" console mode c p
On Wed, Apr 02, 2014 at 04:39:07PM +, Will Lucas wrote:
> Not sure if this is the correct forum but I did not see find much besides
>
> emacs-X11.exe.stackdump (not helpful)
>
> Stack trace:
>
> End of stack trace
This sounds like an X-related question, therefore per
http://cygwin.com/list
Not sure if this is the correct forum but I did not see find much besides
emacs-X11.exe.stackdump (not helpful)
Stack trace:
FrameFunctionArgs
0420F50 0018006F6D3 (0008004345D, 030, 001802DE638, 04212E0)
00B 00180070B8A (0018013354D, 000, 59C
On Apr 3 13:08, Angelo Graziosi wrote:
> Corinna Vinschen wrote:
> >It's pretty easy.
>
> OK, "Mum"... ;-)
>
> I will try this evening.
Thanks! Could you please send the link to the PR to this thread?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwi
Le Wed, 02 Apr 2014 00:07:12 +0200, Jean-Pierre Flori a écrit :
> Dear all,
>
> It's amazing to see how well Cygwin64 is going.
> Thanks for your hard work.
>
> While preparing the new MPIR release, which will be the first one to
> support Cygwin4, we encountered problems running MPIR testsuite
Corinna Vinschen wrote:
It's pretty easy.
OK, "Mum"... ;-)
I will try this evening.
Ciao,
Angelo.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.c
On Apr 3 11:13, Angelo Graziosi wrote:
> Ciao Corinna,
>
> Corinna Vinschen wrote:
> >I can reproduce the issue, but it's
> >pretty unclear what happens.
>
> Indeed.. In my original Fortran application what triggered the issue
> was the code about the "Time interval" dialogue. For example
> comm
Ciao Corinna,
Corinna Vinschen wrote:
I can reproduce the issue, but it's
pretty unclear what happens.
Indeed.. In my original Fortran application what triggered the issue was
the code about the "Time interval" dialogue. For example commenting out
the "DEFPUSHBUTTON" line under TTOT, the iss
Hi Angelo,
On Apr 2 18:54, Angelo Graziosi wrote:
> It seems that the attached test case does not work rightly with
> current binutils.
>
> The Help menu contains two About items and About2 is created from
> About1 with Copy/Paste. Now, while clicking on About1 works as
> expected, the click on
On Apr 2 16:26, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> > there's really no reason to quote that at all
>
> Maybe, but how would I know that you did not need that?
That's why I said "for the records" :)
> > It means the pointer to the "signal_arrived" event object is invalid.
> > "signal_
13 matches
Mail list logo
