> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Christopher Faylor
> Sent: Tuesday, 18 July 2006 5:33 AM
> To: cygwin@cygwin.com
> Subject: Re: scp timeout on dual-core processor
>
> On Tue, Jul 18, 2006 at 05:06:07AM +1
trouble? In the past, there have been problems with Dell machines of this
> configuration coming with Embasy software which was really gumming up the
> works. Maybe you can investigate this avenue if you also have this
> software.
>
>
Just to confirm - removing the Embassy Tru
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Dave Korn
> Sent: Saturday, 27 May 2006 4:04 AM
> To: cygwin@cygwin.com
> Subject: RE: Problems with ssh/scp/sftp on a dual core Dell Latitude D820
>
> On 26 May 2006 18:54, Larry Hall (Cygwin) wrote:
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Steve Baldwin
> Sent: Tuesday, 2 May 2006 6:54 AM
> To: cygwin@cygwin.com
> Subject: RE: scp timeout on dual-core processor
>
> > -Original Message-
> > From:
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Harig, Mark
> Sent: Tuesday, 2 May 2006 5:20 AM
> To: cygwin@cygwin.com
> Subject: scp timeout on dual-core processor
>
> The Cygwin version of the openssh utility program, 'scp', appears to
> have a de
Maybe the package maintainer could consider building two packages : a
'clean' fortune and rename the current package to 'fortune-xxx'. I have no
idea how easy or difficult this is, but it would satisfy both camps.
Steve
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem
I do what you would typically do in a *nix environment - i.e. make the
first line of the script "#!/usr/bin/perl -w". Works just fine.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Martin Gainty
> Sent: Wednesday, 17 March 2004 7:57 AM
> To: [EMA
I'm trying to port some Unix software that extensively uses shared
memory, semaphores, and threads. Not sure if I'm pushing sh*t uphill,
but I got cygipc-1.13-2 installed, and the IPC daemon running. I have a
simple case that hopefully shows my error ...
#include
#include
#include
#include
#
Thanks for your reply, and I know I stuffed up my example, but there's
still some weird (in my mind) things going on here. Have a look
at this ...
## Here's where it goes splat ..
##
[cdev]$ cat a.c
#include
#include
extern void fx (void) ;
extern void fx2 (void) ;
extern int *myglobal ;
int
m
OK, I think I've solved this by creating export/import libraries.
Thanks
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Steve Baldwin
Sent: Saturday, 22 February 2003 4:22 PM
To: [EMAIL PROTECTED]
Subject: Accessing global variables causes segfault
I'm having some (further) issues porting some Unix code to cygwin. I
have a
scenario where there are global variables defined in a shared library,
and referenced in the executable. See the example below. Yes I know
it's bad coding practice, but I'm hoping to port the code with the least
amount o
I'm having problems porting some Unix code to cygwin. Here's a small
sample, and the error I'm seeing. Any help appreciated.
Steve
[cdev]$ cat a.c
#include
#include
#include
int
main (int argc, char **argv) {
struct mallinfo mi ;
mi = mallinfo() ;
}
[cdev]$ gcc a.c
12 matches
Mail list logo