-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
> Uh, ok. So this is actually a bug in the application?
To put it mildly, yes.
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iE
On May 5 09:49, Yaakov S wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Corinna Vinschen wrote:
> > AFAICS this is a generic problem with the X11/Xwindows.h file which
> > should be fixed upstream. The definition of sleep as Sleep might be
> > fine for a native X server, but not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
> AFAICS this is a generic problem with the X11/Xwindows.h file which
> should be fixed upstream. The definition of sleep as Sleep might be
> fine for a native X server, but not for the Cygwin X server and should
> be guarded
On May 5 17:28, Chris LeBlanc wrote:
> Hi Dave,
>
> Thanks for the description of the problem, and the workaround. Our
> code is pretty complicated at points, so it might be challenging to be
> sure of the include order, but I'll try.
>
> The other suggestion I saw from Christopher Faylor was t
Hi Dave,
Thanks for the description of the problem, and the workaround. Our
code is pretty complicated at points, so it might be challenging to be
sure of the include order, but I'll try.
The other suggestion I saw from Christopher Faylor was to try Cygwin
commercial support. This was actually
On Tue, May 05, 2009 at 02:57:47PM +1200, Chris LeBlanc wrote:
>I'm trying to migrate our commercial software (we've purchased a
>commercial Cygwin license)
Why aren't you contacting Red Hat for support then? This isn't the
support forum for the commercial Red Hat version of Cygwin.
--
Unsubscri
Chris LeBlanc wrote:
>> gcc-4 test_sleep.c -Wall -lX11 -lcomdlg32 -o test_sleep
> In file included from /usr/include/unistd.h:4,
> from test_sleep.c:4:
> /usr/include/sys/unistd.h:144: error: expected declaration specifiers
> or '...' before '(' token
> /usr/include/sys/unistd.h:1
Hi,
I'm trying to migrate our commercial software (we've purchased a
commercial Cygwin license) thats been running well on Cygwin using gcc
3.x to gcc-4. Its mature Unix/Linux C and Fortran code. We're using
the win32api so we can use native Windows file dialogs. This has been
Attached patch switches to error numbers to handle
various foreign languages.
On Fri Jun 22 05:25:57 2007, demerphq wrote:
> On 6/21/07, Reini Urban via RT at
perl.org> wrote:
> > Sorry 'bout the subject. Please change to
> > "Win32API::File tests language specific&
On 28 May 2007 14:42, Alain Nguyen wrote:
> Hi,
>
> I am a new CYGWIN user.
>
> I actually tried to compile and link a C/C++ program using the 'w32api',
> more exactly, the '/lib/w32api/libws2_32.a' library, with the following
> command:
>
> $gcc -o myprogram -lws2_32-c mypr
Hi,
I am a new CYGWIN user.
I actually tried to compile and link a C/C++ program using the 'w32api',
more exactly, the '/lib/w32api/libws2_32.a' library, with the following
command:
$gcc -o myprogram -lws2_32-c myprogram.c
But, I always got the error messages from the 'ld' l
Hi Ross,
i have the same problem of accessing the registry via Perl. I tried to
compile the libwin32-0.18 module from cpan but it was a desaster.
As a quick solution i used wrapped calls of reg.exe (from the resource
kit) via system() and backticks but that's a very dirty solution.
I don't unde
12 matches
Mail list logo