RE: Automake version 1.4 in CygWin vs. current Automake 1.9.2 ...

[Herb Martin]

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Brian Dessent
> Sent: Friday, September 30, 2005 12:54 AM
> To: cygwin@cygwin.com
> Subject: Re: Automake version 1.4 in CygWin vs. current 
> Automake 1.9.2 ...
> 
> Herb Martin wrote:
> 
> > > Your automake is too old. These are the recommended 
> minimum version
> > requirements:
> > 
> > > # autoconf (GNU Autoconf) 2.59
> > > # ltmain.sh (GNU libtool) 1.5.6
> > > # automake (GNU automake) 1.9.2
> > 
> > Automake in CygWin seems to be quite old compared to the current 
> > version -- is there a significant impediment to upgrade?
> > 
> > Automake 1.9.2 completed make but "make check"
> > failed:
> 
> The current packaged version of automake in Cygwin is 1.9.6, 
> which is contained in the "automake1.9" package.  You should 
> install that if you need a more recent version.  The packages 
> named "automake", "automake-devel", and "automake-stable" are 
> all empty obsolete packages from before the changeover.  You 
> should remove them if you have them installed, since they 
> serve no purpose any more.
> 
> Brian

Thanks -- my version was installed from "setup" and is 
(theorectically) up to date but shows:

$ automake --version
automake (GNU automake) 1.4-p6

I have never installed another version manually; until
today I had never even tried.

(Investigating setup...)

In setup there were 5 versions listed as installed, the
1.4 and 1.6.x, 1.7.x, 1.8.x, 1.9.6-2

I told it to uninstall all but the latter and to re-install
that one.

It gave me a warning about 1.4 being required by the stable
version -- re-running version gives the same results:

$ automake --version
automake (GNU automake) 1.4-p6

Since automake was a like to 1.4, I removed the link and
re-added it to point to 1.9.6.

This portion of my problem is solved but I thought 
the explanation might help others.

Thanks for the help.

--
Herb


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Automake version 1.4 in CygWin vs. current Automake 1.9.2 ...

[Brian Dessent]

Herb Martin wrote:

> > Your automake is too old. These are the recommended minimum version
> requirements:
> 
> > # autoconf (GNU Autoconf) 2.59
> > # ltmain.sh (GNU libtool) 1.5.6
> > # automake (GNU automake) 1.9.2
> 
> Automake in CygWin seems to be quite old compared
> to the current version -- is there a significant
> impediment to upgrade?
> 
> Automake 1.9.2 completed make but "make check"
> failed:

The current packaged version of automake in Cygwin is 1.9.6, which is
contained in the "automake1.9" package.  You should install that if you
need a more recent version.  The packages named "automake",
"automake-devel", and "automake-stable" are all empty obsolete packages
from before the changeover.  You should remove them if you have them
installed, since they serve no purpose any more.

Brian

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: date function: daylight savings

[Pagano, Tom - Portland, OR]

 
I see, so the issue is whether "1 day" is defined as 24 hours or the same 
hour/minute/second on the previous day. 
 
And this would apply to things on the front end of the season like 
 
$ date -d "2001-04-01 -1 day"
Sat Mar 31 00:00:00 PST 2001
$ date -d "2001-04-02 -2 day"
Fri Mar 30 23:00:00 PST 2001
 
as well. My workaround since I don't need the hours (just the year, month, day) 
might be to set the time to noon instead of midnight. 
 
$ date -d "12:00:00 2001-04-01 -1 day"
Sat Mar 31 11:00:00 PST 2001
$ date -d "12:00:00 2001-04-02 -2 day"
Sat Mar 31 11:00:00 PST 2001
 
Good info, lightning response, thanks. 
 
Tom
 

-Original Message- 
From: Eric Blake [mailto:[EMAIL PROTECTED] 
Sent: Thu 9/29/2005 9:49 PM 
To: Pagano, Tom - Portland, OR 
Cc: cygwin@cygwin.com 
Subject: Re: date function: how many days in october are there?



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Pagano, Tom - Portland, OR on 9/29/2005 9:41 PM:
> I've noticed that the date function does something strange trying to 
access October 31st in a statement like
> 
> $ date -d "1970-10-01 +1 month -1 day"
> as opposed to something like
> $ date -d "1970-11-01 -1 day"
> which (I think??) should be functionally equivalent. The actual 
results of the 2nd are obviously preferrable to the 1st... but I do note 
something squirrly going on with the hours in both (daylight savings time?)

Indeed it is daylight savings.  date has no cygwin-specific patches, but
the brand new coreutils 5.90 has been released upstream that has some
patches in date parsing.  Once I can get that packaged, you may want to
rerun your tests - if the bug is still present at that time, then report
it upstream.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
volunteer cygwin coreutils maintainer
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDPLW084KuGfSFAYARAso1AJ4ia3ivMy0zj2hSJFqHJp6wK3ZwSgCg0wKD
2rBt20yYxwrSG1sxLaqbTHU=
=0bxZ
-END PGP SIGNATURE-

Automake version 1.4 in CygWin vs. current Automake 1.9.2 ...

[Herb Martin]

In trying to configure/make DSpam on CygWin
1.5.18 (and failing) I was informed by the
DSpam author:

> Your automake is too old. These are the recommended minimum version
requirements: 

> # autoconf (GNU Autoconf) 2.59
> # ltmain.sh (GNU libtool) 1.5.6
> # automake (GNU automake) 1.9.2

Automake in CygWin seems to be quite old compared 
to the current version -- is there a significant
impediment to upgrade?

Automake 1.9.2 completed make but "make check"
failed:

=
20 of 514 tests failed
(34 tests were not run)
Please report to bug-automake@gnu.org
=

(reported to suggested address) 

--
Herb Martin


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: date function: how many days in october are there?

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Pagano, Tom - Portland, OR on 9/29/2005 9:41 PM:
> I've noticed that the date function does something strange trying to access 
> October 31st in a statement like 
>  
> $ date -d "1970-10-01 +1 month -1 day"
> as opposed to something like 
> $ date -d "1970-11-01 -1 day"
> which (I think??) should be functionally equivalent. The actual results of 
> the 2nd are obviously preferrable to the 1st... but I do note something 
> squirrly going on with the hours in both (daylight savings time?) 

Indeed it is daylight savings.  date has no cygwin-specific patches, but
the brand new coreutils 5.90 has been released upstream that has some
patches in date parsing.  Once I can get that packaged, you may want to
rerun your tests - if the bug is still present at that time, then report
it upstream.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
volunteer cygwin coreutils maintainer
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDPLW084KuGfSFAYARAso1AJ4ia3ivMy0zj2hSJFqHJp6wK3ZwSgCg0wKD
2rBt20yYxwrSG1sxLaqbTHU=
=0bxZ
-END PGP SIGNATURE-

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

date function: how many days in october are there?

[Pagano, Tom - Portland, OR]

I've noticed that the date function does something strange trying to access 
October 31st in a statement like 
 
$ date -d "1970-10-01 +1 month -1 day"
as opposed to something like 
$ date -d "1970-11-01 -1 day"
which (I think??) should be functionally equivalent. The actual results of the 
2nd are obviously preferrable to the 1st... but I do note something squirrly 
going on with the hours in both (daylight savings time?) 
 
When I run date -d "$i-10-01 +1 month -1 day" I get 
Tue Oct 31 00:00:00 PST 1950
Wed Oct 31 00:00:00 PST 1951
Fri Oct 31 00:00:00 PST 1952
Sat Oct 31 00:00:00 PST 1953
Sun Oct 31 00:00:00 PST 1954
Mon Oct 31 00:00:00 PST 1955
Wed Oct 31 00:00:00 PST 1956
Thu Oct 31 00:00:00 PST 1957
Fri Oct 31 00:00:00 PST 1958
Sat Oct 31 00:00:00 PST 1959
Mon Oct 31 00:00:00 PST 1960
Tue Oct 31 00:00:00 PST 1961
Wed Oct 31 00:00:00 PST 1962
Thu Oct 31 00:00:00 PST 1963
Sat Oct 31 00:00:00 PST 1964
Sun Oct 31 00:00:00 PST 1965
Mon Oct 31 00:00:00 PST 1966
Tue Oct 31 00:00:00 PST 1967
Thu Oct 31 00:00:00 PST 1968
Fri Oct 31 00:00:00 PST 1969
Fri Oct 30 23:00:00 PST 1970
Sun Oct 31 00:00:00 PDT 1971
Mon Oct 30 23:00:00 PST 1972
Tue Oct 30 23:00:00 PST 1973
Wed Oct 30 23:00:00 PST 1974
Thu Oct 30 23:00:00 PST 1975
Sun Oct 31 00:00:00 PDT 1976
Sun Oct 30 23:00:00 PST 1977
Tue Oct 30 23:00:00 PST 1979
Thu Oct 30 23:00:00 PST 1980
Fri Oct 30 23:00:00 PST 1981
Sun Oct 31 00:00:00 PDT 1982
Sun Oct 30 23:00:00 PST 1983
Tue Oct 30 23:00:00 PST 1984
Wed Oct 30 23:00:00 PST 1985
Thu Oct 30 23:00:00 PST 1986
Fri Oct 30 23:00:00 PST 1987
Sun Oct 30 23:00:00 PST 1988
Mon Oct 30 23:00:00 PST 1989
Tue Oct 30 23:00:00 PST 1990
Wed Oct 30 23:00:00 PST 1991
Fri Oct 30 23:00:00 PST 1992
Sun Oct 31 00:00:00 PDT 1993
Sun Oct 30 23:00:00 PST 1994
Mon Oct 30 23:00:00 PST 1995
Wed Oct 30 23:00:00 PST 1996
Thu Oct 30 23:00:00 PST 1997
Fri Oct 30 23:00:00 PST 1998
Sun Oct 31 00:00:00 PDT 1999
Mon Oct 30 23:00:00 PST 2000
Tue Oct 30 23:00:00 PST 2001
Wed Oct 30 23:00:00 PST 2002
Thu Oct 30 23:00:00 PST 2003
Sun Oct 31 00:00:00 PDT 2004
Sun Oct 30 23:00:00 PST 2005
Mon Oct 30 23:00:00 PST 2006
Tue Oct 30 23:00:00 PST 2007
Thu Oct 30 23:00:00 PST 2008
Fri Oct 30 23:00:00 PST 2009
Sun Oct 31 00:00:00 PDT 2010
Sun Oct 30 23:00:00 PST 2011
Tue Oct 30 23:00:00 PST 2012
Wed Oct 30 23:00:00 PST 2013
Thu Oct 30 23:00:00 PST 2014
Fri Oct 30 23:00:00 PST 2015
 
as opposed to date -d "$i-11-01 -1 day"
Tue Oct 31 00:00:00 PST 1950
Wed Oct 31 00:00:00 PST 1951
Fri Oct 31 00:00:00 PST 1952
Sat Oct 31 00:00:00 PST 1953
Sun Oct 31 00:00:00 PST 1954
Mon Oct 31 00:00:00 PST 1955
Wed Oct 31 00:00:00 PST 1956
Thu Oct 31 00:00:00 PST 1957
Fri Oct 31 00:00:00 PST 1958
Sat Oct 31 00:00:00 PST 1959
Mon Oct 31 00:00:00 PST 1960
Tue Oct 31 00:00:00 PST 1961
Wed Oct 31 00:00:00 PST 1962
Thu Oct 31 00:00:00 PST 1963
Sat Oct 31 00:00:00 PST 1964
Sun Oct 31 00:00:00 PST 1965
Mon Oct 31 00:00:00 PST 1966
Tue Oct 31 00:00:00 PST 1967
Thu Oct 31 00:00:00 PST 1968
Fri Oct 31 00:00:00 PST 1969
Sat Oct 31 00:00:00 PST 1970
Sun Oct 31 01:00:00 PDT 1971
Tue Oct 31 00:00:00 PST 1972
Wed Oct 31 00:00:00 PST 1973
Thu Oct 31 00:00:00 PST 1974
Fri Oct 31 00:00:00 PST 1975
Sun Oct 31 01:00:00 PDT 1976
Mon Oct 31 00:00:00 PST 1977
Wed Oct 31 00:00:00 PST 1979
Fri Oct 31 00:00:00 PST 1980
Sat Oct 31 00:00:00 PST 1981
Sun Oct 31 01:00:00 PDT 1982
Mon Oct 31 00:00:00 PST 1983
Wed Oct 31 00:00:00 PST 1984
Thu Oct 31 00:00:00 PST 1985
Fri Oct 31 00:00:00 PST 1986
Sat Oct 31 00:00:00 PST 1987
Mon Oct 31 00:00:00 PST 1988
Tue Oct 31 00:00:00 PST 1989
Wed Oct 31 00:00:00 PST 1990
Thu Oct 31 00:00:00 PST 1991
Sat Oct 31 00:00:00 PST 1992
Sun Oct 31 01:00:00 PDT 1993
Mon Oct 31 00:00:00 PST 1994
Tue Oct 31 00:00:00 PST 1995
Thu Oct 31 00:00:00 PST 1996
Fri Oct 31 00:00:00 PST 1997
Sat Oct 31 00:00:00 PST 1998
Sun Oct 31 01:00:00 PDT 1999
Tue Oct 31 00:00:00 PST 2000
Wed Oct 31 00:00:00 PST 2001
Thu Oct 31 00:00:00 PST 2002
Fri Oct 31 00:00:00 PST 2003
Sun Oct 31 01:00:00 PDT 2004
Mon Oct 31 00:00:00 PST 2005
Tue Oct 31 00:00:00 PST 2006
Wed Oct 31 00:00:00 PST 2007
Fri Oct 31 00:00:00 PST 2008
Sat Oct 31 00:00:00 PST 2009
Sun Oct 31 01:00:00 PDT 2010
Mon Oct 31 00:00:00 PST 2011
Wed Oct 31 00:00:00 PST 2012
Thu Oct 31 00:00:00 PST 2013
Fri Oct 31 00:00:00 PST 2014
Sat Oct 31 00:00:00 PST 2015

Re: A problem with the patch utility and windows paths.

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Bob Rundle on 9/29/2005 8:27 AM:
> Greetings,
> 
> I've having a few issues with the patch utility.  It is not working with
> windows paths.  I am using Windows XP and the latest cygwin patch.  Any help
> is appreciated.  Attached is the cygcheck file.
> 
> If I have two directories "oldversion" and "newversion"
> 
> $ diff -u oldversion newversion >1.tm
> $ patch <1.tm

What error message are you getting that you think is not right?  Did you
use the -p option?  We need a reproducible test case.  Also, it may help
to follow these directions:

> Problem reports:   http://cygwin.com/problems.html

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDPLOf84KuGfSFAYARAis3AJ47wWQGByGFW0i3LgTGm24o40eRUgCeJgLg
7+47tGs/9ihiEy4FVReVxwo=
=7eZ1
-END PGP SIGNATURE-

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: Starting cygwin processess at reduced priority?

[Herb Martin]

> > I have no renice.  Did you compile this yourself?
> 
> POSIX requires renice, but so far, no one has contributed a 
> renice to coreutils.  If I can ever get my employer to sign 
> my copyright disclaimer, that is one of the projects on my 
> todo list.  Meanwhile, util-linux
> (http://freshmeat.net/releases/72929) apparently provides a 
> renice, but it has not yet been ported to cygwin.

Is snice the same (or very similar) thing?

--
Herb Martin



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: on the road to 1.5.19 - snapshot testing needed

[Gary R. Van Sickle]

A cvs pull of wxWindows configured and built fine here.

-- 
Gary R. Van Sickle
 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Faylor
> Sent: Thursday, September 29, 2005 6:13 PM
> To: cygwin@cygwin.com
> Subject: on the road to 1.5.19 - snapshot testing needed
> 
> The latest snapshot is chock full of developer goodness and 
> needs to be tested.
> 
> Both Corinna and I spent a lot of time trying to track down 
> the reported
> fork() problems.  We didn't fix them* but this snapshot 
> contains better fork error reporting.
> 
> This snapshot also contains a rewrite of cygwin's method for 
> interprocess communication.  This means that /proc/NNN stuff 
> (where NNN is a pid) and fifos could be affected.  procps 
> seems to work for me and my simple fifo tests show that they 
> are working as well as they ever did (which means that they 
> aren't fully implemented) but please report any new problems there.
> 
> There is also a fix for LD_PRELOAD.  A problem crept in when 
> I introduced the ability for cygwin to detect when it is 
> running a non-cygwin process.
> 
> Corinna revamped cygwin's "raw device" handling, so reading 
> from raw hard drives and floppies should be improved.  She 
> cleaned up POSIX semaphore handling a little and fixed the 
> creation of some of cygwin's shared memory regions so that 
> they are globablly accessible.  She also finally added a 
> WinMainCRTStartup entry point to cygwin after eight years.
> 
> I took a stab at speeding up fork slightly by eliminating 
> some expensive calls to the OS.
> 
> Yitzchak Scott-Thoeness introduced the ability to use 
> 'siginfo' style signal handlers.
> 
> Oh, and Corinna also fixed the rmdir foo/. (and similar 
> mkdir) problem although there are still other interesting 
> problems with paths that end in /. or /..
> 
> So, once again, I'd like to finally release this thing and so 
> I'm asking for testing help.  You all should know the drill 
> by now but, just in case you don't:
> 
>   * * *
> 
> I'm asking, once again, for people to test the latest cygwin snapshot.
> The snapshot that is currently available should be very close 
> to an official release of cygwin version 1.5.19.
> 
> Please report success or failure to this thread.  Please 
> don't change the subject.  Please don't start a new 
> discussion.  If you have a problem please report it using the 
> guidelines found at .
>  
> If you think you've found an error, please indicate whether 
> this is a regression from 1.5.18 and, if possible, indicate 
> regressions from previous snapshots.  Regression from other 
> past versions are worth reporting, but are only mildly 
> useful.  There are no guarantees that we will fix a problem 
> for 1.5.19 unless it is a regression from 1.5.18.
> 
> In general, just remember that we need *details*.  So, when 
> reporting a problem, report the exact steps that you took to 
> cause the problem to occur.  If there is anything "unusual" 
> about your environment (firewalls, virus checkers, etc.) 
> please report that too.
> 
> Snapshots are located here: .
> 
> Thanks.
> 
> cgf
> 
> *http://sources.redhat.com/ml/cygwin/2005-09/msg00945.html
> 
> --
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:   http://cygwin.com/problems.html
> Documentation: http://cygwin.com/docs.html
> FAQ:   http://cygwin.com/faq/
> 


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: on the road to 1.5.19 - snapshot testing needed

[Yitzchak Scott-Thoennes]

On Thu, Sep 29, 2005 at 07:13:21PM -0400, Christopher Faylor wrote:
> I'm asking, once again, for people to test the latest cygwin snapshot.
> The snapshot that is currently available should be very close to an
> official release of cygwin version 1.5.19.
>
> Please report success or failure to this thread.  Please don't change
> the subject.  Please don't start a new discussion.  If you have a
> problem please report it using the guidelines found at
> <http://cygwin.com/problems.html>.

Development version of perl builds fine with this snapshot, and passes
all tests (2 tests had failed with 1.5.18).  It detects and uses
readdir_r (which wasn't exported in 1.5.18).

I'm happy to see some new include files over what was in 1.5.18,
and the removal of some redundant info files:

$ perl snapfiles.pl cygwin-inst-20050929.tar.bz2
cygwin:
   all but /usr/share/info/configure.info-1 /usr/share/info/libc.info-1
no package:
   /usr/include/byteswap.h
   /usr/include/elf.h
   /usr/include/fts.h
   /usr/include/ftw.h
   /usr/include/sys/elf32.h
   /usr/include/sys/elf64.h
   /usr/include/sys/elf_common.h
   /usr/include/sys/elf_generic.h

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

on the road to 1.5.19 - snapshot testing needed

[Christopher Faylor]

The latest snapshot is chock full of developer goodness and needs to
be tested.

Both Corinna and I spent a lot of time trying to track down the reported
fork() problems.  We didn't fix them* but this snapshot contains better
fork error reporting.

This snapshot also contains a rewrite of cygwin's method for
interprocess communication.  This means that /proc/NNN stuff (where NNN
is a pid) and fifos could be affected.  procps seems to work for me and
my simple fifo tests show that they are working as well as they ever did
(which means that they aren't fully implemented) but please report any
new problems there.

There is also a fix for LD_PRELOAD.  A problem crept in when I introduced
the ability for cygwin to detect when it is running a non-cygwin process.

Corinna revamped cygwin's "raw device" handling, so reading from raw
hard drives and floppies should be improved.  She cleaned up POSIX
semaphore handling a little and fixed the creation of some of cygwin's
shared memory regions so that they are globablly accessible.  She also
finally added a WinMainCRTStartup entry point to cygwin after eight
years.

I took a stab at speeding up fork slightly by eliminating some expensive
calls to the OS.

Yitzchak Scott-Thoeness introduced the ability to use 'siginfo' style
signal handlers.

Oh, and Corinna also fixed the rmdir foo/. (and similar mkdir) problem
although there are still other interesting problems with paths that end
in /. or /..

So, once again, I'd like to finally release this thing and so I'm asking
for testing help.  You all should know the drill by now but, just in case
you don't:

  * * *

I'm asking, once again, for people to test the latest cygwin snapshot.
The snapshot that is currently available should be very close to an
official release of cygwin version 1.5.19.

Please report success or failure to this thread.  Please don't change
the subject.  Please don't start a new discussion.  If you have a
problem please report it using the guidelines found at
.
 
If you think you've found an error, please indicate whether this is a
regression from 1.5.18 and, if possible, indicate regressions from
previous snapshots.  Regression from other past versions are worth
reporting, but are only mildly useful.  There are no guarantees that we
will fix a problem for 1.5.19 unless it is a regression from 1.5.18.

In general, just remember that we need *details*.  So, when reporting a
problem, report the exact steps that you took to cause the problem to
occur.  If there is anything "unusual" about your environment
(firewalls, virus checkers, etc.) please report that too.

Snapshots are located here: .

Thanks.

cgf

*http://sources.redhat.com/ml/cygwin/2005-09/msg00945.html

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: cygssl-0.9.7 and python

[Yitzchak Scott-Thoennes]

On Thu, Sep 29, 2005 at 08:41:54AM -0700, Brian Dessent wrote:
> Jacek Pop?awski wrote:
> 
> > You will notice error "unable to remap", everything is fixed after removing
> > that file!
> 
> This just means that you need to install rebase and run rebaseall from
> an ash prompt.

After putting back the dll you deleted.

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Starting cygwin processess at reduced priority?

[Eric Blake]

> >> You can also use renice to re-prioritize a running process 
> >
> 
> I have no renice.  Did you compile this yourself?

POSIX requires renice, but so far, no one has contributed
a renice to coreutils.  If I can ever get my employer to sign
my copyright disclaimer, that is one of the projects on my
todo list.  Meanwhile, util-linux
(http://freshmeat.net/releases/72929) apparently provides
a renice, but it has not yet been ported to cygwin.

--
Eric Blake
volunteer cygwin coreutils maintainer



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: Tasking not implemented on this configuration

[Williams, Gerald S \(Jerry\)]

I wrote:
>> 3. Unzip them in cygwin installed directory. Remember to keep
>> the directory structure intact when Unzipping. In addition,
>> select over all when prompted by WinZip.
>
> This sounds dangerous to me.

Anh Vo wrote:
> It is not all. What it does is to replace the Ada compiler
> (GNAT) without tasking run-time support with the that does.
> Every thing else remains the same.

Perhaps, but I personally wouldn't want to blindly overwrite
parts of my compiler system. Even if I were going to install
it in the Cygwin area, I'd remove the old one with setup.exe
and then unzip WITHOUT overwrite.

> I put some thing like Ada compiler or GNAT on the subject. It
> was quite a while ago. If you search my name, Anh Vo, you may have
> seen it. 

I remember seeing and responding to the following one:

  http://sourceware.org/ml/cygwin/2005-05/msg00408.html

although that didn't mention either in the subject.

gsw


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: Starting cygwin processess at reduced priority?

[Herb Martin]

> "Herb Martin" <[EMAIL PROTECTED]> writes:
> 
> >> You can also use renice to re-prioritize a running process
> >
> 
> I have no renice.  Did you compile this yourself?
> 
> Dave

The quoting was screwed up (somewhere along the line)
and I am not the original poster but was thanking him.

I have no renice either -- and my CygWin is a 'complete'
install.

And searching the GNU site didn't turn it up either, but
I did find the CygWin "snice" which seems to do the task
described for renice.


--
Herb Martin

> 
> 
> --
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:   http://cygwin.com/problems.html
> Documentation: http://cygwin.com/docs.html
> FAQ:   http://cygwin.com/faq/
> 


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: Starting cygwin processess at reduced priority?

[Herb Martin]

> "Herb Martin" <[EMAIL PROTECTED]> writes:
> 
> >> You can also use renice to re-prioritize a running process
> >
> 
> I have no renice.  Did you compile this yourself?
> 
> Dave

The quoting was screwed up (somewhere along the line)
and I am not the original poster but was thanking him.

I have no renice either -- and my CygWin is a 'complete'
install.

And searching the GNU site didn't turn it up either, but
I did find the CygWin "snice" which seems to do the task
described for renice.


--
Herb Martin

> 
> 
> --
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:   http://cygwin.com/problems.html
> Documentation: http://cygwin.com/docs.html
> FAQ:   http://cygwin.com/faq/
> 


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Starting cygwin processess at reduced priority?

[J. David Boyd]

"Herb Martin" <[EMAIL PROTECTED]> writes:

>> You can also use renice to re-prioritize a running process 
>

I have no renice.  Did you compile this yourself?

Dave


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Tasking not implemented on this configuration

[Anh Vo]

>>> "Williams, Gerald S (Jerry)" <[EMAIL PROTECTED]> 9/29/2005 7:56:52 AM >>>
<< Anh Vo wrote:
> If you need both Ada compiler with run-time support and cygwin, do
> the following. 
...
> 3. Unzip them in cygwin installed directory. Remember to keep
> the directory structure intact when Unzipping. In addition,
> select over all when prompted by WinZip.

This sounds dangerous to me. Doesn't it interfere with other
Cygwin compilations? Plus, I wouldn't expect this version of
the compiler to create Cygwin executables (e.g., that would
understand Cygwin paths, etc.). If not, why interfere with
the Cygwin installation at all? >>

It is not all. What it does is to replace the Ada compiler (GNAT) without 
tasking run-time support with the that does. Every thing else remains the sam. 

<< I took the approach recommended at mingw.org and installed it
into C:/MinGW. Then I created a script that would put it in
the beginning of my path when I wanted to use it. You could
do this automatically if you only want the MinGW version. >>

Sure, it works, too.

<< A search of the mailing list doesn't reveal any messages from
the maintainer containing the word "tasking" both "task" and
"ada". Perhaps the question should be restated with a subject
of "GCC-ADA:" or "Attn: gcc-ada maintainer"? >>

I put some thing like Ada compiler or GNAT on the subject. It was quite a while 
ago. If you search my name, Anh Vo, you may have seen it.

AV



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: Starting cygwin processess at reduced priority?

[Herb Martin]

> You can also use renice to re-prioritize a running process 

Cool. Thanks.

> remember, lower numbers mean higher priority.  

Thank you -- got that from man/help/info etc.

Opposite to Win32 but that's ok since it is documented.

It was driving me crazy to have to go find the
PID and use TaskManager each time I started some
low-priority CPU intensive task.

> If it works 
> exactly like on linux of course.

I learned 'Linux' mostly from CygWin 
although I do know bits and piece from Unix
(long time ago) and TiVo.  


--
Herb Martin



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: change the font size of rxvt

[HopeSeekr of xMule]

Simple:  -fn "fixedsys-12"


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: IP_MULTICAST_IF et. all / Winsock[2] value conflict

[Brian Ford]

On Thu, 29 Sep 2005, Corinna Vinschen wrote:

> On Sep 29 11:27, Brian Ford wrote:
> > I'm having a problem with IP_MULTICAST_IF not working on Cygwin.  While
> > investigating, I came across this MS KB article that might describe my
> > problem:
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;257460
> >
> > IP_MULTICAST_IF can have two values (2 or 9) depending on whether you're
> > linking to Winsock 1 or 2.  By preprocessing my source and looking in
> > /usr/include/cygwin/socket.h, I see we are using the value 2 which means
> > it will only work if we link to Winsock 1?
> >
> > IIRC, Cygwin dynamically loads which ever library is present or version 2
> > if both are available?  I assume we are loading version 2 on my system
> > given it is WinXP?
> >
> > I don't understand the Cygwin magic to do this well enough to supply a
> > patch.  I also don't understand how including Winsock2.h followed by
> > Ws2tcpip.h is supposed to allow you to link against either library.
> >
> > Here's hoping that Corinna or someone else is less confused and can supply
> > a fix to either Cygwin or my limited understanding.  Thanks.
>
> There's no easy fix right now.  We have to drop all traces of Winsock1
> in Cygwin and change the headers accordingly.

Can't we just translate these based on a flag indicating what version we
dynamically loaded?

> Since you didn't say what problem you had, I assume that IP_MULTICAST_IF
> just didn't do what you wanted.

Correct.  It did not send out the interface I requested.

> Did you try to use just the value 9 instead of IP_MULTICAST_IF?

Not yet, but I will this afternoon.  Thanks.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Bug in dd ?? at EOM

[Corinna Vinschen]

On Sep 29 18:10, Bengt-Arne Fjellner wrote:
> Reading /dev/fd0 fails :-(
> $ dd if=/dev/fd0 of=kk bs=512 conv=noerror,sync
> dd: opening `/dev/fd0': Invalid request code
> 
> with snapshot cygwin1-20050928.dll

Thanks for the report.  I've applied a fix.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: IP_MULTICAST_IF et. all / Winsock[2] value conflict

[Corinna Vinschen]

On Sep 29 11:27, Brian Ford wrote:
> I'm having a problem with IP_MULTICAST_IF not working on Cygwin.  While
> investigating, I came across this MS KB article that might describe my
> problem:
> 
> http://support.microsoft.com/default.aspx?scid=kb;en-us;257460
> 
> IP_MULTICAST_IF can have two values (2 or 9) depending on whether you're
> linking to Winsock 1 or 2.  By preprocessing my source and looking in
> /usr/include/cygwin/socket.h, I see we are using the value 2 which means
> it will only work if we link to Winsock 1?
> 
> IIRC, Cygwin dynamically loads which ever library is present or version 2
> if both are available?  I assume we are loading version 2 on my system
> given it is WinXP?
> 
> I don't understand the Cygwin magic to do this well enough to supply a
> patch.  I also don't understand how including Winsock2.h followed by
> Ws2tcpip.h is supposed to allow you to link against either library.
> 
> Here's hoping that Corinna or someone else is less confused and can supply
> a fix to either Cygwin or my limited understanding.  Thanks.

There's no easy fix right now.  We have to drop all traces of Winsock1
in Cygwin and change the headers accordingly.  Since you didn't say
what problem you had, I assume that IP_MULTICAST_IF just didn't do what
you wanted.  Did you try to use just the value 9 instead of IP_MULTICAST_IF?


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

IP_MULTICAST_IF et. all / Winsock[2] value conflict

[Brian Ford]

I'm having a problem with IP_MULTICAST_IF not working on Cygwin.  While
investigating, I came across this MS KB article that might describe my
problem:

http://support.microsoft.com/default.aspx?scid=kb;en-us;257460

IP_MULTICAST_IF can have two values (2 or 9) depending on whether you're
linking to Winsock 1 or 2.  By preprocessing my source and looking in
/usr/include/cygwin/socket.h, I see we are using the value 2 which means
it will only work if we link to Winsock 1?

IIRC, Cygwin dynamically loads which ever library is present or version 2
if both are available?  I assume we are loading version 2 on my system
given it is WinXP?

I don't understand the Cygwin magic to do this well enough to supply a
patch.  I also don't understand how including Winsock2.h followed by
Ws2tcpip.h is supposed to allow you to link against either library.

Here's hoping that Corinna or someone else is less confused and can supply
a fix to either Cygwin or my limited understanding.  Thanks.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Bug in dd ?? at EOM

[Bengt-Arne Fjellner]

Corinna Vinschen skrev:
> On Sep 26 12:08, Dave Korn wrote:
>> Original Message
>> >From: Bengt-Arne Fjellner
>> >Sent: 26 September 2005 11:43
>>
>> > When using dd with flags conv=noerror,sync
>> > It tries reading after the disc ends.
>> >
>> > This line in cygwin tries reading past end of media:
>> >  dd if=/dev/sdd of=kk bs=512 skip=156280250 conv=noerror,sync
>> > dd: reading `/dev/sdd': Input/Output error
>> > 21120+0 records in
>> > 21120+0 records out
>> > 10813440 bytes (11 MB) copied, 1.151 seconds, 9.4 MB/s
>> > dd: reading `/dev/sdd': Input/Output error
>> > 21120+1 records in
>> > 21121+0 records out
>> > repeats "forever"
>> >
>>
>> > Stops at end of disk. Whos wrong?
>>
>>   There is very definitely a problem with cygwin vs. dd, which I'm
>> investigating.  I've seen the same thing with CF%20memory cards, and 
>> initially
thought it was directly related to the memcard driver, but I was becoming
convinced it's a generic problem with cygwin's readv, and since you've found it
shows up on hard drives as well, that confirms it for me.  I'll get round to it
late tonight.
>
> I've applied a patch which tries to workaround the strange behaviour of Win32
ReadFile when reading beyond EOF.  Please give the next developers snapshot a 
try.
>
>
> Corinna
>

That works for me now with latest snapshot.
Havent tested yet with a failing disk though.

Reading /dev/fd0 fails :-(
$ dd if=/dev/fd0 of=kk bs=512 conv=noerror,sync
dd: opening `/dev/fd0': Invalid request code

with snapshot cygwin1-20050928.dll

-- 
Bengt-Arne Fjellner



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: cygssl-0.9.7 and python

[Brian Dessent]

Jacek Pop³awski wrote:

> You will notice error "unable to remap", everything is fixed after removing
> that file!

This just means that you need to install rebase and run rebaseall from
an ash prompt.

Brian

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: 1.5.x: Windows 2003 - no console output

[Brian Dessent]

Igor Kalders wrote:

> I thought the non-cygwin sshd apps were just making use of cygwin in a
> custom way, without the need of installing cygwin itself. At least, when
> they get installed, you end up with some command-line tools, among which a
> cygwin dll. That made me assume these apps are just a partial cygwin with
> some handy auto-configuration. But your remark makes me think I see that
> wrong.

You are on extremely shakey ground with this.  Having more than one copy
of cygwin1.dll on your system is a VERY bad idea unless you know exactly
what you're doing.  I strongly recommend that you stick to official
Cygwin packages.  If you must use something packaged by a third party,
then delete any cygwin1.dll that it installs and make sure that the one
in \cygwin\bin is in the path.

> Still, mustn't I be able to launch a shell with the cygwin.bat that comes
> with a fresh cygwin install? And subsequently be able to call any command
> (like ls, man, ...). That's what I'm able to do on my XP box anyway.

Yes, you should be able to do that.  But your cygcheck seems to indicate
that your installation is seriously broken.  For one thing, the bash,
ls, etc. binaries that are being found in your path are not the Cygwin
ones but whatever junk is under \Program Files\copssh.  And you have an
empty mount table!  And your PATH is set to an invalid value (Path =
`Path=C:\Progr...).  And you apparently have no package database.

I have no idea what this copssh thing is, but it's not supported by this
list and it's obvious that it doesn't coexist peacefully with Cygwin at
all.

Brian

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: setup.exe 2.510.2.2, 2.427 and 2.457 consistently failing, on win2000, sp4

[Luke Kenneth Casson Leighton]

On Thu, Sep 29, 2005 at 10:43:59AM -0400, Igor Pechtchanski wrote:
> How are your permissions on c:\cygwin and c:\cygwin\etc?
 
 running as admin, and it was same with FAT32.


> > > It would be interesting to see what the log looks like for a real
> > > install -- download from internet, etc.
> >
> >  that's going to hammer my network for an hour: any suggestions on
> >  minimum package (singular!) which will get info into the logs?
> 
> There's no single package -- many things in the Base category are
> inter-dependent.  However, if you switch back to the original mirror you
> used to download the packages, setup won't re-download stuff it already
> has in the cache.

 ah, then i can do that, no problem.



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Setup error: "URL Scheme not registered!"

[Joshua Daniel Franklin]

On 9/24/05, wrote:
> I'm setting up Cygwin. I downloaded files to one machine, and I want
> to install over the network to another machine (I don't have enough
> space for both the pre- and post-install files on the target machine).
> However, when I run setup on the other machine, as soon as it starts
> copying files, I get this error:
>
> Fatal Error: Uncaught Exception
> Thread: install
> Type: St16invalid_argument
> Message: URL Scheme not registered!
>
> I Googled for previous information about this. It seems that I needed
> to move the setup.ini file aside. I tried this, but that wipes out the
> list of packages when I re-run setup.exe. What gives? Thanks in
> advance for any help.

You really haven't provided much information here. What are the options
you choose with setup.exe? What does your network path look like
(\\server\share\ or X:\)? Is there anything else in setup.log? See

http://cygwin.com/faq/faq.setup.html#faq.setup.setup-fails

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: ./configure and pthreads

[Herb Martin]

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Brian Ford
> Sent: Thursday, September 29, 2005 10:26 AM
> > Sure I would love someone to just 'solve' this for me but 
> what is the 
> > most useful way to diagnose (or learn to diagnose) this problem so 
> > that I may create a more useful report?
> >
> > (Although a developer, I admit to being mostly ignorant of 
> > make/configure issues...but I can learn.)
> 
> Look in the build directory for the file config.log, search 
> for pthreads, and find out what failed.
> 
> Sounds like their pthread detection macro is broken.  I have 
> one that works fine on Cygwin.

Apparently (from a separate message on the DSPAM list)
they added -ldl and FreeBSD and (maybe) CygWin don't
have/use this?

Going to check now

--
Herb 


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: Starting cygwin processess at reduced priority?

[Herb Martin]

> From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] 

> Herb:
> > It would be better to have a way to just start a CygWin job 
> in reduced 
> > priority.
> >
> > I am betting this is just ignorance on my part -- there is 
> a command 
> > right?
> 
> Yes, and a very nice one... :-)  See "man nice".

Yes it is very nice.  And so are you for helping.

BTW:  It' default value -n 10 (nice factor) produces
a "belownormal" setting which is exactly what I wanted.

Presumably, -n 19 (the max) would give "idle" priority
or at max "low".

--
Herb Martin


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: ./configure and pthreads

[Brian Ford]

On Thu, 29 Sep 2005, Herb Martin wrote:

> I am attempting to ./configure 'dspam' for make
> on CygWin 1.5.18 (release with most all updates).
>
> ./configure --version
>   dspam configure 3.6.rc3
>   generated by GNU Autoconf 2.59
>
> ./configure gives this pthreads related error message:
>
>   checking how you like your pthreads... unknown
>   configure: error: Unable to determine how to compile with pthreads
>
> Sure I would love someone to just 'solve' this for me
> but what is the most useful way to diagnose (or learn
> to diagnose) this problem so that I may create a more
> useful report?
>
> (Although a developer, I admit to being mostly
> ignorant of make/configure issues...but I can learn.)

Look in the build directory for the file config.log, search for pthreads,
and find out what failed.

Sounds like their pthread detection macro is broken.  I have one that
works fine on Cygwin.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

./configure and pthreads

[Herb Martin]

I am attempting to ./configure 'dspam' for make
on CygWin 1.5.18 (release with most all updates).

./configure --version
  dspam configure 3.6.rc3
  generated by GNU Autoconf 2.59

./configure gives this pthreads related error message:

  checking how you like your pthreads... unknown
  configure: error: Unable to determine how to compile with pthreads

Sure I would love someone to just 'solve' this for me
but what is the most useful way to diagnose (or learn
to diagnose) this problem so that I may create a more
useful report?

(Although a developer, I admit to being mostly 
ignorant of make/configure issues...but I can learn.)

--
Herb Martin


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Starting cygwin processess at reduced priority?

[Igor Pechtchanski]

On Thu, 29 Sep 2005, Herb Martin wrote:

> I tried the naive approach of running copy of cmd.exe to get "start
> /belownormal" but that didn't work and isn't realy what I want anyway.
> It would be better to have a way to just start a CygWin job in reduced
> priority.
>
> I am betting this is just ignorance on my part -- there is a command
> right?

Yes, and a very nice one... :-)  See "man nice".
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Starting cygwin processess at reduced priority?

[Herb Martin]

I tried the naive approach of running copy
of cmd.exe to get "start /belownormal" but
that didn't work and isn't realy what I want
anyway.  It would be better to have a way to
just start a CygWin job in reduced priority.

I am betting this is just ignorance on my
part -- there is a command right?

--
Herb Martin


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: Tasking not implemented on this configuration

[Williams, Gerald S \(Jerry\)]

Anh Vo wrote:
> If you need both Ada compiler with run-time support and cygwin, do
> the following. 
...
> 3. Unzip them in cygwin installed directory. Remember to keep
> the directory structure intact when Unzipping. In addition,
> select over all when prompted by WinZip.

This sounds dangerous to me. Doesn't it interfere with other
Cygwin compilations? Plus, I wouldn't expect this version of
the compiler to create Cygwin executables (e.g., that would
understand Cygwin paths, etc.). If not, why interfere with
the Cygwin installation at all?

I took the approach recommended at mingw.org and installed it
into C:/MinGW. Then I created a script that would put it in
the beginning of my path when I wanted to use it. You could
do this automatically if you only want the MinGW version.

A search of the mailing list doesn't reveal any messages from
the maintainer containing the word "tasking" both "task" and
"ada". Perhaps the question should be restated with a subject
of "GCC-ADA:" or "Attn: gcc-ada maintainer"?

-Jerry


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: setup.exe 2.510.2.2, 2.427 and 2.457 consistently failing, on win2000, sp4

[Igor Pechtchanski]

On Thu, 29 Sep 2005, Luke Kenneth Casson Leighton wrote:

> On Thu, Sep 29, 2005 at 10:19:58AM -0400, Igor Pechtchanski wrote:
>
> > >  http://hands.com/~lkcl/cygwin
> >
> > Umm, doesn't look like you actually tried to install anything...  Did you
> > simply switch to partial view and then cancel?
>
>  no - i didn't!!
>
>  it's a minimum install which i downloaded earlier.

Hmm, weird.

>  btw - when it says the files aren't there (fopen failed) it's because
>  the files _aren't_ there!!
>
>  should they be?

Yes.

>  should they have been created?

Yes, but possibly after a successful install.  I just noticed the way the
install database is managed in setup, and it's ghastly.  I'll see if I can
write something more sensible when I get a round tuit.

>  maybe this is something as weird as fopen() with create flags being
>  ignored...

How are your permissions on c:\cygwin and c:\cygwin\etc?

> > It would be interesting to see what the log looks like for a real
> > install -- download from internet, etc.
>
>  that's going to hammer my network for an hour: any suggestions on
>  minimum package (singular!) which will get info into the logs?

There's no single package -- many things in the Base category are
inter-dependent.  However, if you switch back to the original mirror you
used to download the packages, setup won't re-download stuff it already
has in the cache.
HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

[ADMINISTRIVIA] cygwin.com/sourceware.org/gcc.gnu.org/sources.redhat.com server downtime

[Christopher Faylor]

The machine running all the cygwin project services, cygwin.com (aka
sourceware.org aka sources.redhat.com aka etc.) will be down this
weekend, Saturday 2005-10-01.  Its services are being transferred to a
new larger and faster machine.

Hopefully it will only be down for a few hours, but it would be wise not 
to expect it back until Sunday. Obviously we will try to minimise the 
downtime.

While the system is down there will be no web service, mailing lists,
CVS, or FTP.  setup.exe will also not work since it relies on the
ability to contact sourceware.org.

FYI.
--
Christopher Faylor  spammer? -> [EMAIL PROTECTED]
Cygwin Co-Project Leader[EMAIL PROTECTED]
TimeSys, Inc.

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: setup.exe 2.510.2.2, 2.427 and 2.457 consistently failing, on win2000, sp4

[Luke Kenneth Casson Leighton]

On Thu, Sep 29, 2005 at 10:19:58AM -0400, Igor Pechtchanski wrote:

> >  http://hands.com/~lkcl/cygwin
> 
> Umm, doesn't look like you actually tried to install anything...  Did you
> simply switch to partial view and then cancel?  

 no - i didn't!!

 it's a minimum install which i downloaded earlier.

 btw - when it says the files aren't there (fopen failed) it's because
 the files _aren't_ there!!

 should they be?

 should they have been created?

 maybe this is something as weird as fopen() with create flags being
 ignored...

> It would be interesting to
> see what the log looks like for a real install -- download from internet,
> etc.

 that's going to hammer my network for an hour: any suggestions on
 minimum package (singular!) which will get info into the logs?

 ta,

 l.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

A problem with the patch utility and windows paths.

[Bob Rundle]

Greetings,

I've having a few issues with the patch utility.  It is not working with
windows paths.  I am using Windows XP and the latest cygwin patch.  Any help
is appreciated.  Attached is the cygcheck file.

If I have two directories "oldversion" and "newversion"

$ diff -u oldversion newversion >1.tm
$ patch <1.tm

Should work.  The following does work

$ diff -u a.cpp b.cpp >1.tm
$ patch <1.tm

This is what makes me think it is the windows paths.
 
Regards,
Bob Rundle



cygcheck.out
Description: Binary data
--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: setup.exe 2.510.2.2, 2.427 and 2.457 consistently failing, on win2000, sp4

[Igor Pechtchanski]

On Thu, 29 Sep 2005, Luke Kenneth Casson Leighton wrote:

> On Tue, Sep 27, 2005 at 09:42:08PM -0400, Igor Pechtchanski wrote:
> > On Tue, 27 Sep 2005, Luke Kenneth Casson Leighton wrote:
> >
> > > On Tue, Sep 27, 2005 at 10:09:44AM -0400, Igor Pechtchanski wrote:
> > > > On Tue, 27 Sep 2005, Luke Kenneth Casson Leighton wrote:
> > > >
> > > > > On Mon, Sep 26, 2005 at 08:43:06PM -0400, Igor Pechtchanski wrote:
> > > > > > On Mon, 26 Sep 2005, Luke Kenneth Casson Leighton wrote:
> > > > > >
> > > > > > > i check c:\cygwin\var\log\setup.log and it is full of
> > > > > > > io_stream_cygfile: fopen failed 2 No such file or directory,
> > > > > >
> > > > > > What about c:\cygwin\var\log\setup.log.full?  It should have more
> > > > > > information (in particular, the io_stream_cygfile messages should be
> > > > > > preceded by the names of the files they correspond to).
> >
> > Ok, I was wrong -- setup didn't print the filenames to the log, period.
> > The version I'm going to ask you to try, however, does.  Please post the
> > resulting log file in the same web location (and thanks for being
> > considerate).
>
>  done.
>
>  http://hands.com/~lkcl/cygwin

Umm, doesn't look like you actually tried to install anything...  Did you
simply switch to partial view and then cancel?  It would be interesting to
see what the log looks like for a real install -- download from internet,
etc.

>  good _god_ that's possibly the largest compression ratio i've ever seen.
>  385k down to 1316 bytes.

It's *VERY* repetitive. :-)

>  now why didn't i compress that _before_ scp'ing it...

:-)
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Bug in dd ?? at EOM

[Bengt-Arne Fjellner]

Corinna Vinschen skrev:
> On Sep 26 12:08, Dave Korn wrote:
>> Original Message
>> >From: Bengt-Arne Fjellner
>> >Sent: 26 September 2005 11:43
>>
>> > When using dd with flags conv=noerror,sync
>> > It tries reading after the disc ends.
>> >
>> > This line in cygwin tries reading past end of media:
>> >  dd if=/dev/sdd of=kk bs=512 skip=156280250 conv=noerror,sync
>> > dd: reading `/dev/sdd': Input/Output error
>> > 21120+0 records in
>> > 21120+0 records out
>> > 10813440 bytes (11 MB) copied, 1.151 seconds, 9.4 MB/s
>> > dd: reading `/dev/sdd': Input/Output error
>> > 21120+1 records in
>> > 21121+0 records out
>> > repeats "forever"
>> >
>>
>> > Stops at end of disk. Whos wrong?
>>
>>   There is very definitely a problem with cygwin vs. dd, which I'm
>> investigating.  I've seen the same thing with CF memory cards, and initially
>> thought it was directly related to the memcard driver, but I was becoming
>> convinced it's a generic problem with cygwin's readv, and since you've found
>> it shows up on hard drives as well, that confirms it for me.  I'll get round
>> to it late tonight.
>
> I've applied a patch which tries to workaround the strange behaviour of
> Win32 ReadFile when reading beyond EOF.  Please give the next developers
> snapshot a try.
>
>
> Corinna
>

Works for me now with latest snapshot.
Havent test yet with a failing disk though.
Thanks.

-- 
Bengt-Arne Fjellner



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: bug in rmdir(2)

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Corinna Vinschen on 9/29/2005 6:31 AM:
> 
> Try the actual call rmdir(2) and especially read the rmdir entry in SUSv3:
> http://www.opengroup.org/onlinepubs/009695399/functions/rmdir.html

That's exactly what I did before first raising my report.

> 
> There's no text restricting the behaviour in case of "dir/", there's just
> this:
> 
>   If the path argument refers to a path whose final component is either
>   dot or dot-dot, rmdir() shall fail.

But the confusion in POSIX comes from the overriding requirement that for
all functions, unless otherwise specified, a filename with a trailing
slash has . implicitly appended:
http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap04.html#tag_04_11
And since rmdir(2) does not specify otherwise, the strict reading says it
should treat "dir/" as "dir/.", which must fail.

> 
> On Linux, rmdir(2) consequentially allows removing "dir/".

So Linux is not strictly compliant, because it strips the trailing slash
instead of appending . (although my argument to the Austin group is that
Linux's behavior is desirable, and the spec is buggy and should be fixed;
not that Linux should be changed).  So that same argument applies to
cygwin - let rmdir("dir/") continue to work as though it had been
rmdir("dir"), and hope that the POSIX folks agree on a fix to the standard
that allows the reasonable existing behavior.

You are still left, however, with a decision of whether rmdir("symlink/")
would fail with ENOTDIR or remove the referrant directory.  If I
understood the coreutils thread correctly (I don't have access to the
various kernels myself to verify), Linux 2.4.x removes the referrant, but
Linux 2.6.x fails with ENOTDIR.  I would lean towards the latter, as it
can be rather confusing when the referrant directory is removed, leaving a
dangling symlink.

> 
> The "path/.." case is also already covered by returning ENOTEMPTY or
> EBUSY, whatever Windows returns.  So there's only the "path/." case
> left to check.

True - ENOTEMPTY or EBUSY are both allowed by POSIX in that case (cygwin
actually gets ENOTEMPTY).

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDO+hA84KuGfSFAYARAitbAJ40X0SPZBJVowMgmlrxiseLNPJqSgCgnm0t
KcRwGS+BNI6saKppoU+3vLU=
=YRz8
-END PGP SIGNATURE-

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

cygssl-0.9.7 and python

[Jacek Popławski]

Hi!

This bug really annoys me, because I need to remove library to use my Python
script, and lots of applications (like lftp) uses that library...

Problem is related to /bin/cygssl-0.9.7.dll file.

try following steps:

1) run python
2) write: 'import subprocess'
3) write: 'subprocess.Popen("ls")' (or any other command)

You will notice error "unable to remap", everything is fixed after removing
that file!

-- 
Free Software - find interesting programs and change them
NetHack - meet interesting creatures, kill them and eat their bodies
Usenet - meet interesting people from all over the world and flame them
Decopter - unrealistic helicopter simulator, get it from http://decopter.sf.net

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Socket operation on non-socket with rsync/ssh

[Pablo Halpern]

Larry Hall  cygwin.com> writes:

> 
> At 11:14 PM 9/26/2005, Pablo Halpern wrote:
> >I'm having a similar problem.  The results of cygcheck.svr are at the end of
> >this message.
> >
> >The symptoms are this:
> >1. ssh-add gives these messages when trying to set a passphrase:
> >bash% eval $(ssh-agent -s)
> >Agent pid 908
> >bash% ssh-add
> >Enter passphrase for /home/Pablo/.ssh/id_dsa:
> >Error reading response length from authentication socket.
> >Error writing to authentication socket.
> >Could not add identity: /home/Pablo/.ssh/id_dsa
> 
> I don't see that, although I'm using an RSA(2) key.  Do you see the same
> thing with RSA keys?  Also, I notice that your home directory is mounted as 
> text.  You might want to try mounting at least your .ssh directory as 
> binary.  It's not clear to me that either of these two things are very 
> significant but they are differences between our two environments.  If you 
> do go the binary mount route, make sure you run 'd2u' on the text files in 
> the affected directories.

I tried different key types and different mounting modes.  No help.

I figured out the problem (at last) by digging into the LSP stack
using Microsoft Anti-spyware.  The problem was caused by part of the
Earthlink Total-Access package I installed so that I could dial up
while away from home.  Most likely, it was the Anti-spyware part of
the package, although I wasn't able to do a partial un-install.  I
would guess that one of the following is happening:

1. Earthlink's Anti-Spyware LSP is badly written (most likely)
2. Earthlink's Anti-Spyware believes rsync and ssh-agent to be spyware but
   isn't telling me.
3. Earthlink's Anti-Spyware doesn't coexist peacefully with Microsoft
   Antispyware.

> >2. rsync hangs at random.  Most hangs appear to be with either
> >large files (15-20MB) or zero-length files.  If it hangs on a file
> >once, it will probably hang on the same file on the next try.  If I
> >delete or manually sync the file, rsync moves on and transfers more
> >files before succeeding or hanging again.  Intrestingly, it hangs
> >MORE often with local transfers than over ssh.
> 
> This sounds to me like the age-old rsync problems.  You can read about them 
> in the email archives.

Yes.  This problem also went away when I uninstalled Earthlink.  We can add
Earthlink Total-Access to the list of packages that are not compatible with
Cygwin.  (Is there such a list anywhere?)  When I get around to it, I'll try
re-installing Earthlink WITHOUT the anti-spyware component and see if it still
interferes.

I can't tell you how relieved I am to be able to do automatic synchronization
between my home PC and my laptop again.

[snip]
> >> That said, did you read and follow the following thread to it's 
> >> resolution?
> >> 
> >> 

This is the thread that got me wondering about what had installed
itself into my LSP stack.  I was fearing that it was Norton Antivirus
(which I would have been loath to abandon), but had an Aha! moment
when I saw the Earthlink entries.  The incompatible program was not
Aventail, as mentioned in the thread, but the concept was the same.  I
read that thread before posting but read it again after your response.
Thanks for the help.

> >Now, the result of cygcheck -svr:
> 
> We ask that you *attach* this to any problem reports you send to the list.
> Please don't embed it.

I couldn't figure out a way to create an attachment using the web interface to
this newsgroup.  Sorry.



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: bug in rmdir(2)

[Corinna Vinschen]

On Sep 29 06:17, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> According to Corinna Vinschen on 9/29/2005 1:50 AM:
> >>The fix to rmdir(2) is easy - check for a trailing / or /. or /..
> >>before handing the name off to the complex path processing
> >>code, and fail with EINVAL if so.  rmdir(2) isn't called often
> >>enough for this to slow down everything else, and there are
> >>no Windows API calls in this failure mode, and in return you
> >>get POSIX compliance.
> > 
> > 
> > Just a trailing slash is fine, btw.  Try this on any POSIXy system.
> 
> It is still inconsistent on POSIXy systems - compare Solaris 8 vs. Solaris 10:
> 
> 8> mkdir a
> 8> ln -s a b
> 8> rmdir b/
> rmdir: directory "b/": Path component not a directory
> 
> 10> mkdir a
> 10> ln -s a b
> 10> rmdir b/
> 10> ls ?
> b
> 
> However, I'm not sure in Solaris 8 whether the trailing slash was removed
> by rmdir(1) before calling rmdir(2), or whether rmdir(2) errored out with
> ENOTDIR.  But Solaris 10 certainly removed the referrant directory,
> leaving the symlink dangling.

Try the actual call rmdir(2) and especially read the rmdir entry in SUSv3:
http://www.opengroup.org/onlinepubs/009695399/functions/rmdir.html

There's no text restricting the behaviour in case of "dir/", there's just
this:

  If the path argument refers to a path whose final component is either
  dot or dot-dot, rmdir() shall fail.

On Linux, rmdir(2) consequentially allows removing "dir/".

The "path/.." case is also already covered by returning ENOTEMPTY or
EBUSY, whatever Windows returns.  So there's only the "path/." case
left to check.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: bug in rmdir(2)

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Corinna Vinschen on 9/29/2005 1:50 AM:
>>The fix to rmdir(2) is easy - check for a trailing / or /. or /..
>>before handing the name off to the complex path processing
>>code, and fail with EINVAL if so.  rmdir(2) isn't called often
>>enough for this to slow down everything else, and there are
>>no Windows API calls in this failure mode, and in return you
>>get POSIX compliance.
> 
> 
> Just a trailing slash is fine, btw.  Try this on any POSIXy system.

It is still inconsistent on POSIXy systems - compare Solaris 8 vs. Solaris 10:

8> mkdir a
8> ln -s a b
8> rmdir b/
rmdir: directory "b/": Path component not a directory

10> mkdir a
10> ln -s a b
10> rmdir b/
10> ls ?
b

However, I'm not sure in Solaris 8 whether the trailing slash was removed
by rmdir(1) before calling rmdir(2), or whether rmdir(2) errored out with
ENOTDIR.  But Solaris 10 certainly removed the referrant directory,
leaving the symlink dangling.

Further discussion on the coreutils list pointed out that POSIX has some
holes in this area (a strict reading of "rm -R symlink/", for example,
would remove the contents of the referrant directory, then fail with
EINVAL, but obviously no system does that - they just remove symlink and
leave the referrant directory intact).  In light of the misunderstandings
in interpreting POSIX, and the various behaviors on different POSIXy
platforms, I'm now in the process of asking the Austin group for
clarification (with a goal of mandating, or at least allowing, existing
behavior, where it is different from a strict reading of the
specification).  So for now I agree that you only need to check for
explicit trailing . or .., and don't worry about trailing / until the next
version of POSIX better defines what can/should be done.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDO9tt84KuGfSFAYARAmuTAKDQSxOctFpFJW5mukyYCdzIlNy1owCgvsLJ
f0wQVl/Go1ToSGYy+TOm4/0=
=WY/e
-END PGP SIGNATURE-

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: 1.5.x: Windows 2003 - no console output

[Igor Kalders]

> You are running non-Cygwin programs in a Cygwin tty (because you have
> 'tty' in $CYGWIN.)  Non-Cygwin programs do not know what a Cygwin tty
> is, and think they are writing to a pipe.  This causes the output to be
> buffered, so you only see output in large chunks when the buffer fills
> enough to be flushed.

Hmmm... you're explanation may be right, but I find it hard to believe that
relates to my problem, for:
1. The exit code is not 0
2. An ls -R on my C: also yields nothing 


> The reason it works when you launch them from strace is because strace
> is not a Cygwin binary (that is, it's compiled with mingw and doesn't
> use cygwin1.dll) and so when it launches the child process a
> normal/native console is used.

That sounds plausible ;)


> - Don't try to run non-Cygwin programs from a Cygwin tty.  Why in the
> world are you not using the Cygwin-packaged openssh?  It will not suffer
> from this.

I thought the non-cygwin sshd apps were just making use of cygwin in a
custom way, without the need of installing cygwin itself. At least, when
they get installed, you end up with some command-line tools, among which a
cygwin dll. That made me assume these apps are just a partial cygwin with
some handy auto-configuration. But your remark makes me think I see that
wrong.

Still, mustn't I be able to launch a shell with the cygwin.bat that comes
with a fresh cygwin install? And subsequently be able to call any command
(like ls, man, ...). That's what I'm able to do on my XP box anyway.


> - Remove 'tty' from $CYGWIN (and don't use rxvt/xterm) in which case
> Cygwin will not use a pseudoterminal but instead use the native windows
> console.

I tried both "SET CYGWIN=tty" and "SET CYGWIN=notty" from my command prompt
and then call bash (within the same cmd session of course). This does not
make any difference. Should I try to force the tty setting in another way?

Igor



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: 1.5.x: Windows 2003 - no console output

[Brian Dessent]

Igor Kalders wrote:

> - Start the console with "C:\WINDOWS\system32\cmd.exe"
> - CD to the cygwin installation directory ("C:\Program Files\OpenSSH",
> "C:\Program Files\CopSSH" or "C:\cygwin")
> - Execute any command (ls, ps, man, bash, ...)
> - Getting no console output

You are running non-Cygwin programs in a Cygwin tty (because you have
'tty' in $CYGWIN.)  Non-Cygwin programs do not know what a Cygwin tty
is, and think they are writing to a pipe.  This causes the output to be
buffered, so you only see output in large chunks when the buffer fills
enough to be flushed.

The reason it works when you launch them from strace is because strace
is not a Cygwin binary (that is, it's compiled with mingw and doesn't
use cygwin1.dll) and so when it launches the child process a
normal/native console is used.

The solution is probably one of:

- Don't try to run non-Cygwin programs from a Cygwin tty.  Why in the
world are you not using the Cygwin-packaged openssh?  It will not suffer
from this.

- Remove 'tty' from $CYGWIN (and don't use rxvt/xterm) in which case
Cygwin will not use a pseudoterminal but instead use the native windows
console.

Brian

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

1.5.x: Windows 2003 - no console output

[Igor Kalders]

After installing OpenSSHD, CopSSH or just the latest cygwin setup, I cannot
get any console output at the Windows command prompt (cmd.exe).

What I'm doing:
- Start the console with "C:\WINDOWS\system32\cmd.exe"
- CD to the cygwin installation directory ("C:\Program Files\OpenSSH",
"C:\Program Files\CopSSH" or "C:\cygwin")
- Execute any command (ls, ps, man, bash, ...)
- Getting no console output

Checking the errorlevel gives me 128.

When I strace any of the commands, they work fine, like if they have a
problem getting hold of the console. While bash won't start in "normal"
mode, it will while stracing (and calling commands then also works, though
output is of course mixed with the strace output).

I run cygwin on w2k3 and have not only tried the abovementioned packages,
while using CopSSH, I also reverted the cygwin files ranging 1.5.11-1.5.18.
To no avail.

Am I missing something (cygceck should be attached) ?
 
Igor

Cygwin Configuration Diagnostics
Current System Time: Thu Sep 29 09:38:35 2005

Windows 2003 Server Ver 5.2 Build 3790 Service Pack 1

Running in Terminal Service session

Path:   Path=C:\Program Files\Windows Resource Kits\Tools\
C:\Program Files\Python23
C:\Program Files\Support Tools\
C:\Perl\bin\
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
C:\Program Files\Microsoft SQL Server\80\Tools\BINN
C:\Program Files\Subversion\bin

SysDir: C:\WINDOWS\system32
WinDir: C:\WINDOWS

CYGWIN = `binmode ntsec tty'
Path = `Path=C:\Program Files\Windows Resource Kits\Tools\;C:\Program 
Files\Python23;C:\Program Files\Support 
Tools\;C:\Perl\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
 Files\Microsoft SQL Server\80\Tools\BINN;C:\Program Files\Subversion\bin'

ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
APPDATA = `C:\Documents and Settings\igor\Application Data'
APR_ICONV_PATH = `C:\Program Files\Subversion\iconv'
CLIENTNAME = `GRIMACE'
ClusterLog = `C:\WINDOWS\Cluster\cluster.log'
CommonProgramFiles = `C:\Program Files\Common Files'
COMPUTERNAME = `AJAX'
ComSpec = `C:\WINDOWS\system32\cmd.exe'
FP_NO_HOST_CHECK = `NO'
HOMEDRIVE = `C:'
HOMEPATH = `\Documents and Settings\igor'
LOGONSERVER = `\\AJAX'
NUMBER_OF_PROCESSORS = `4'
OS = `Windows_NT'
PATHEXT = 
`.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.VBS;.pyc;.pyo;.pyw;.py;.pys'
PROCESSOR_ARCHITECTURE = `x86'
PROCESSOR_IDENTIFIER = `x86 Family 15 Model 2 Stepping 9, GenuineIntel'
PROCESSOR_LEVEL = `15'
PROCESSOR_REVISION = `0209'
ProgramFiles = `C:\Program Files'
PROMPT = `$P$G'
SESSIONNAME = `RDP-Tcp#9'
SystemDrive = `C:'
SystemRoot = `C:\WINDOWS'
TEMP = `C:\DOCUME~1\igor\LOCALS~1\Temp\4'
TMP = `C:\DOCUME~1\igor\LOCALS~1\Temp\4'
USERDOMAIN = `AJAX'
USERNAME = `igor'
USERPROFILE = `C:\Documents and Settings\igor'
windir = `C:\WINDOWS'
POSIXLY_CORRECT = `1'

HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options

c:  hd  NTFS 20002Mb  58% CP CS UN PA FC System
d:  hd  NTFS 40005Mb  86% CP CS UN PA FC Work
e:  hd  NTFS 80168Mb  85% CP CS UN PA FC Data
f:  hd  FAT254Mb  30% CPUN   RAMDisk


Not Found: awk
Found: C:\Program Files\copssh\bin\bash.exe
Found: C:\Program Files\copssh\bin\cat.exe
Found: C:\Program Files\copssh\bin\cp.exe
Not Found: cpp (good!)
Not Found: find
Not Found: gcc
Not Found: gdb
Found: C:\Program Files\copssh\bin\grep.exe
Not Found: ld
Found: C:\Program Files\copssh\bin\ls.exe
Not Found: make
Not Found: mv
Found: C:\Program Files\copssh\bin\rm.exe
Found: C:\Program Files\copssh\bin\sed.exe
Not Found: sh
Found: C:\Program Files\copssh\bin\tar.exe

7k 2003/10/19 C:\Program Files\copssh\bin\cygcrypt-0.dll - os=4.0 img=1.0 
sys=4.0
  "cygcrypt-0.dll" v0.0 ts=2003/10/19 9:57
 1042k 2005/07/07 C:\Program Files\copssh\bin\cygcrypto-0.9.8.dll - os=4.0 
img=1.0 sys=4.0
  "cygcrypto-0.9.8.dll" v0.0 ts=2005/7/7 11:06
  991k 2004/07/06 C:\Program Files\copssh\bin\cygiconv-2.dll - os=4.0 img=1.0 
sys=4.0
  "cygiconv-2.dll" v0.0 ts=2004/7/6 20:10
   22k 2001/12/13 C:\Program Files\copssh\bin\cygintl-1.dll - os=4.0 img=1.0 
sys=4.0
  "cygintl-1.dll" v0.0 ts=2001/12/13 10:28
   37k 2003/08/10 C:\Program Files\copssh\bin\cygintl-2.dll - os=4.0 img=1.0 
sys=4.0
  "cygintl-2.dll" v0.0 ts=2003/8/10 23:50
   54k 2004/07/06 C:\Program Files\copssh\bin\cygintl-3.dll - os=4.0 img=1.0 
sys=4.0
  "cygintl-3.dll" v0.0 ts=2004/7/6 19:51
   21k 2004/10/22 C:\Program Files\copssh\bin\cygminires.dll - os=4.0 img=1.0 
sys=

Re: setup.exe 2.510.2.2, 2.427 and 2.457 consistently failing, on win2000, sp4

[Luke Kenneth Casson Leighton]

On Tue, Sep 27, 2005 at 09:42:08PM -0400, Igor Pechtchanski wrote:
> On Tue, 27 Sep 2005, Luke Kenneth Casson Leighton wrote:
> 
> > On Tue, Sep 27, 2005 at 10:09:44AM -0400, Igor Pechtchanski wrote:
> > > On Tue, 27 Sep 2005, Luke Kenneth Casson Leighton wrote:
> > >
> > > > On Mon, Sep 26, 2005 at 08:43:06PM -0400, Igor Pechtchanski wrote:
> > > > > On Mon, 26 Sep 2005, Luke Kenneth Casson Leighton wrote:
> > > > >
> > > > > > i check c:\cygwin\var\log\setup.log and it is full of
> > > > > > io_stream_cygfile: fopen failed 2 No such file or directory,
> > > > >
> > > > > What about c:\cygwin\var\log\setup.log.full?  It should have more
> > > > > information (in particular, the io_stream_cygfile messages should be
> > > > > preceded by the names of the files they correspond to).
> 
> Ok, I was wrong -- setup didn't print the filenames to the log, period.
> The version I'm going to ask you to try, however, does.  Please post the
> resulting log file in the same web location (and thanks for being
> considerate).

 done.

 http://hands.com/~lkcl/cygwin

 good _god_ that's possibly the largest compression ratio i've ever seen.
 385k down to 1316 bytes.

 now why didn't i compress that _before_ scp'ing it...

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: setup.exe 2.510.2.2, 2.427 and 2.457 consistently failing, on win2000, sp4

[Luke Kenneth Casson Leighton]

hmmm

fopen(/etc/setup/last-action) failed 2 No such ...
fopen(/etc/setup/last-connection) failed 2 No such ...
fopen(/etc/setup/installed.db) failed 2 No such ...

partial view selected, partial view shows all files i previously
downloaded.  this version of setup this time picks up c:\cygfiles
as the "local" install directory.

same set_cyg_drive: "OK" dialog box at end.

On Tue, Sep 27, 2005 at 09:42:08PM -0400, Igor Pechtchanski wrote:
> On Tue, 27 Sep 2005, Luke Kenneth Casson Leighton wrote:
> 
> > On Tue, Sep 27, 2005 at 10:09:44AM -0400, Igor Pechtchanski wrote:
> > > On Tue, 27 Sep 2005, Luke Kenneth Casson Leighton wrote:
> > >
> > > > On Mon, Sep 26, 2005 at 08:43:06PM -0400, Igor Pechtchanski wrote:
> > > > > On Mon, 26 Sep 2005, Luke Kenneth Casson Leighton wrote:
> > > > >
> > > > > > i check c:\cygwin\var\log\setup.log and it is full of
> > > > > > io_stream_cygfile: fopen failed 2 No such file or directory,
> > > > >
> > > > > What about c:\cygwin\var\log\setup.log.full?  It should have more
> > > > > information (in particular, the io_stream_cygfile messages should be
> > > > > preceded by the names of the files they correspond to).
> 
> Ok, I was wrong -- setup didn't print the filenames to the log, period.
> The version I'm going to ask you to try, however, does.  Please post the
> resulting log file in the same web location (and thanks for being
> considerate).
> 
> > > >  rather than irritate the crap out of everybody by dropping a 410k file
> > > >  into thousands of people's mailboxes, i've placed the log at:
> > > >
> > > > http://hands.com/~lkcl/cygwin/setup.log.full
> >
> > > Did you switch to Partial view to verify that you're actually
> > > going to upgrade any packages?
> >
> >  no but i checked the list and it showed package versions: i assume this
> >  means "yes i gonna install these".
> >
> > > If worse comes to worst, I may post a debug version of setup I compiled
> > > and ask you to try it out.  It might give us some clue on what is
> > > happening on your machine.
> >
> >  ack!
> >  happy with that.
> 
> Ok, here goes.  Please use the setup at
> .  This version
> contains a fix for the FTP problem, so ftp mirrors should work too.
> Please switch to the "Partial" view this time, to find out exactly what's
> going to be installed.  The log should tell us exactly which files it
> tries to open.
>   Igor
> -- 
>   http://cs.nyu.edu/~pechtcha/
>   |\  _,,,---,,_  [EMAIL PROTECTED]
> ZZZzz /,`.-'`'-.  ;-;;,_  [EMAIL PROTECTED]
>  |,4-  ) )-,_. ,\ (  `'-' Igor Pechtchanski, Ph.D.
> '---''(_/--'  `-'\_) fL   a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!
> 
> If there's any real truth it's that the entire multidimensional infinity
> of the Universe is almost certainly being run by a bunch of maniacs. /DA

-- 
--
http://lkcl.net";>http://lkcl.net
--

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Which libraries or programs write to /var/log/wtmp ?

[Corinna Vinschen]

On Sep 29 09:16, Jurgen Defurne wrote:
> That is why I am trying to find out by which programs
> this writing to wtmp can be caused.

wtmp is written by all applications calling login(3), logout(3),
logwtmp(3) or updwtmp(3).  These are usually login processes like
login, started from telnet, or sshd.

Just do the same what other systems do, gzip wtmp and create a new,
empty wtmp regulary.  Or shrink it to 0 of you're not interested
in keeping the information.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: Cygwin Load Times and ZoneAlarm (not X)

[Brian Dessent]

Anthony Foglia wrote:

>  Has anyone else experienced long load times for bash/cygwin.bat
> when running ZoneAlarm Security Suite?  And if so, do you have any ideas
> how to speed it up?  With ZoneAlarm shut down, I get a bash prompt in
> under 2 seconds. With ZoneAlarm running, it takes over a full minute.

Horrible.  That's a perfect example of why I can't stand these software
firewalls that put their hooks throughout the whole system.  Try
disabling all the real-time scanning stuff.

> I believe it is the "On-Access" virus scanning.  Are other virus
> scanners as bad?  What software do people recommend for firewall and virus
> protection to use with cygwin?

You might be interested in the thread that starts here:


Brian

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Re: bug in rmdir(2)

[Corinna Vinschen]

On Sep 28 22:26, Eric Blake wrote:
> > At 04:31 PM 9/28/2005, you wrote:
> > >POSIX requires resolving a filename with a trailing slash as
> > >though . were implicitly present, and requires rmdir(2) to fail
> > >with EINVAL if the final component is '.'.  Therefore, both of
> > >these cases should fail rather than removing the directory:
> > >
> > >$ mkdir a b
> > >$ rmdir a/ b/.
> > >$ ls a b  # Oops, rmdir("a/") and rmdir("b/.") incorrectly succeeded
> > >ls: a: No such file or directory
> > >ls: b: No such file or directory
> > 
> > 
> > But that conflicts with Windows semantics, doesn't it?  If this is 
> > important 
> > enough for 'rmdir', I suppose you could patch it to give you the behavior 
> > you describe.  But making Cygwin work this way internally is playing with
> > the already complex path processing code.  I can't see the gain to support 
> > this corner case and slow down everything else.
> 
> The fix to rmdir(2) is easy - check for a trailing / or /. or /..
> before handing the name off to the complex path processing
> code, and fail with EINVAL if so.  rmdir(2) isn't called often
> enough for this to slow down everything else, and there are
> no Windows API calls in this failure mode, and in return you
> get POSIX compliance.

Just a trailing slash is fine, btw.  Try this on any POSIXy system.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Cygwin Load Times and ZoneAlarm (not X)

[Anthony Foglia]

Has anyone else experienced long load times for bash/cygwin.bat 
when running ZoneAlarm Security Suite?  And if so, do you have any ideas 
how to speed it up?  With ZoneAlarm shut down, I get a bash prompt in 
under 2 seconds. With ZoneAlarm running, it takes over a full minute.


	I believe it is the "On-Access" virus scanning.  Are other virus 
scanners as bad?  What software do people recommend for firewall and virus 
protection to use with cygwin?


--Anthony

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

Which libraries or programs write to /var/log/wtmp ?

[Jurgen Defurne]

Hello,

We had a problem induced on Samba by our Cygwin
installation. Our /var/log/wtmp file grew enormously
and made Samba connections flaky. By removing
the wtmp file the flakyness is solved, but we would
like to know the real cause why the wtmp grew
so enormously in such a short time. I am talking about
100'ds of megabytes in a few days.

When I scanned wtmp with 'last', I found out that for
several workstations at certain times of the day
(especially when doing builds) there where peak
accesses (writing probably) in the order of more 
than once per minute.

That is why I am trying to find out by which programs
this writing to wtmp can be caused.

I grepped for wtmp through most files in /bin, /sbin,
/lib, /usr/bin, /usr/sbin and /usr/lib but I do not find
any references to it.

Can anybody help me to look further ?

Regards,

Jurgen

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/