On 2011-09-20 10:51Z, toto titi wrote:
I sent a few years ago a question to the libc project ports mailing
list (http://cygwin.com/ml/libc-ports/) without knowing this email
would be stored and made available to everyone on the internet. My
name and main email address clearly appears in it
On Tue, Sep 20, 2011 at 11:31:55AM +, Greg Chicares wrote:
On 2011-09-20 10:51Z, toto titi wrote:
I sent a few years ago a question to the libc project ports mailing
list (http://cygwin.com/ml/libc-ports/) without knowing this email
would be stored and made available to everyone on the
On Wed, Sep 01, 2010 at 08:33:02PM +0100, Andy Moreton wrote:
Hi,
I've noticed that the info files for libc and libm get installed twice:
~ cygcheck -f /usr/share/info/libm.info
cygwin-1.7.7-1
~ cygcheck -f /usr/share/info/libm.info.gz
cygwin-doc-1.7-1
~ cygcheck -f /usr/share/info/libc.info
On Sep 1 16:36, Christopher Faylor wrote:
On Wed, Sep 01, 2010 at 08:33:02PM +0100, Andy Moreton wrote:
Hi,
I've noticed that the info files for libc and libm get installed twice:
~ cygcheck -f /usr/share/info/libm.info
cygwin-1.7.7-1
~ cygcheck -f /usr/share/info/libm.info.gz
Corinna Vinschen wrote:
[snip]
I'll drop the info dir entirely for the next release.
Please don't do that, there is useful information there from many
packages that explicitly put a short version on the man page, and the
full documentation in the info file(s), for instance read the last page
of
On 09/01/2010 04:31 PM, René Berber wrote:
Corinna Vinschen wrote:
[snip]
I'll drop the info dir entirely for the next release.
Please don't do that, there is useful information there from many
packages that explicitly put a short version on the man page, and the
full documentation in the
Eric Blake wrote:
On 09/01/2010 04:31 PM, René Berber wrote:
Corinna Vinschen wrote:
[snip]
I'll drop the info dir entirely for the next release.
Please don't do that, there is useful information there from many
packages that explicitly put a short version on the man page, and the
full
On 9/17/05, Corinna Vinschen [EMAIL PROTECTED] wrote:
On Sep 17 15:08, Hiroki Sakagami wrote:
Hi,
I have two questions about libc include headers.
1. Is there any reason socklen_t is defined as a macro
instead of typedef in cygwin/socket.h?
Is this a problem for you? The
On Sep 17 15:08, Hiroki Sakagami wrote:
Hi,
I have two questions about libc include headers.
1. Is there any reason socklen_t is defined as a macro
instead of typedef in cygwin/socket.h?
Is this a problem for you? The reasons are plain historical. I don't
see that converting it
Darryl Scott wrote:
Hi!
I cannot find any reference to a problem with this in the Cygwin docs,
redhat site etc.
Libc has as a standard catgets. But catgets and catopen are absent from
the cygwin implementation and gencat and nl_types are not to be found.
So where can I find either the source
Libc has as a standard catgets. But catgets and catopen are absent from the
cygwin implementation and gencat and nl_types are not to be found.
So where can I find either the source for these or a technical spec?
Switched to the main cygwin list.
Cygwin uses newlib.
-Original Message-
From: cygwin-owner On Behalf Of Richard Campbell
Sent: 19 April 2004 15:12
Libc has as a standard catgets. But catgets and catopen are
absent from the
cygwin implementation and gencat and nl_types are not to be found.
So where can I find either the source for
12 matches
Mail list logo
