Re: Cygwin 1.7.8 on Windows 7 Pro x64 Doesn't See Programs Added to C:\Windows\System32 Directory

[marco atzeri]

On Sat, Apr 16, 2011 at 5:40 AM, Leon Vanderploeg  wrote:
> Greetings,
>
> I recently loaded Windows 7 Pro x64 on my laptop, and installed Cygwin
> 1.7.8.  I run a (GCC Compiled) backup program that calls diskshadow.exe --
> which I added to the C:\Windows\System32 directory.  The program faults
> because the shell call can't find the program.
>
> The Path variable is set with C:\Windows\System32 as the first entry, and
> there are no errors.  I've started new command prompts each time I edited
> the Windows PATH variable, and even tried rebooting.
>
> Opening an elevated command prompt, windows finds the program just fine from
> the path variable.  Running Bash, the which command doesn't find
> diskshadow.exe, even though it is there (in C:\Windows\System32).

less than 10 days ago
http://cygwin.com/ml/cygwin/2011-04/msg00098.html

that refers to
http://cygwin.com/ml/cygwin/2006-01/msg00444.html


>
> While still in the bash window (from an elevated command prompt), If I cd to
> /cygdrive/c/Windows/System32 and do "ls -la disk*", it finds other disk
> programs such as diskpart.exe, but not diskshadow.exe, even though I know it
> is there!  This is also true of libcurl-3.dll that I added to
> C:\Windows\System32.    Windows sees it fine, but not bash.
>
> I have been reading documentation and googling till I can't see straight.
>
> Can anyone please help me understand what is happening?
>
> Thanks in advance!
> Leon
>

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

'Cygwin FAQ' translation

[Bohdan Zograf]

Hi!

I'm willing to translate publication located at 
http://cygwin.com/faq.html to the Belorussian language (my mother 
tongue). What I'm asking for is your written permission, so you don't 
mind after I'll post the translation to my blog. The translation is 
intended only for web, no print copies planned.
Visitors of your website, who come from Minsk (Belorussia) will be the 
ones, who will read this blogpost, that's the only way to spread them, 
no additional instruments we can use. Every translation we ever do does 
not costs a penny for the webpage, which is translated. All we ask is to 
link back in whatever way you feel confident about it.


Thank you for the article.
You can leave a voice message and I will call you back, if you prefer a 
call instead of emails.


Sincerely,
Bohdan Zograf
+(360) 488-0303

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

Bad HTML on http://cygwin.com/mirrors.html

[Jens Schweikhardt]

Dear Cygwin Web Site Maintainer,

the bulleted list of mirrors on http://cygwin.com/mirrors.html
looks like it has a problem.


  Africa:

  South Africa: ftp://ftp.is.co.za/mirrors/cygwin/";>ftp.is.co.za(ftp)
<--- this  should not be there.

  Asia:


The same goes for the other continents. You might want to check
proper HTML syntax with a validator, e.g.
http://validator.w3.org/check?uri=http%3A%2F%2Fcygwin.com%2Fmirrors.html&charset=%28detect+automatically%29&doctype=Inline&group=0

Regards,

Jens
-- 
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)

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

Interaction between GDB and python in cygwin - sys.stderr/sys.stdout broken

[Arkadiy Belousov]

Hello All!

I was trying to debug a C module I wrote for Python, and I've
discovered a nasty surprise: Python's sys.stderr.write(...) and
sys.stdout.write(...) do not work when Python is running under GDB.

As you can see from GDB session transcript below, calls to write()
result in  no output, while "print" statement works. When I surround
write() with try/except, I get the following:

IOError: [Errno 9] Bad file descriptor


The results of fileno() calls of stdout/stderr are correct - 1 and 2.

When I run Python in regular cygwin, outside of gdb, it works.

I am not at all sure if this is Python or GDB, but one of them is
doing something that the other can't cope with.

I'll keep looking to find out the difference between Python's use of
file descriptor in sys.stdout.write() and "print" - that's where the
problem must be.

GDB trancript follows:



$ gdb python
GNU gdb 6.8.0.20080328-cvs (cygwin-special)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-cygwin"...
(no debugging symbols found)
(gdb) r
Starting program: /usr/bin/python
[New thread 7180.0x15c8]
Error: dll starting at 0x772d not found.
Error: dll starting at 0x75ea not found.
Error: dll starting at 0x772d not found.
Error: dll starting at 0x773f not found.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New thread 7180.0x1c34]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
>>> (no debugging symbols found)


>>> import sys
import sys
>>> sys.stderr.write("here\n!")
sys.stderr.write("here\n!")
>>> import traceback
import traceback
>>> try:
try:
... sys.stderr.write("here\n!")
sys.stderr.write("here\n!")
... except:
except:
... print traceback.format_exc()
print traceback.format_exc()
...

Traceback (most recent call last):
  File "", line 2, in 
IOError: [Errno 9] Bad file descriptor

>>> stdout.write("success\n")
stdout.write("success\n")
>>> print "success"
print "success"
success
>>>

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

How is setup.ini generated these days?

[Jens Schweikhardt]

hello, world\n

I'm trying to make a package server as described on
http://sourceware.org/cygwin-apps/package-server.html

I've rsynced the complete "release" tree (skipping *-legacy). However,
running

  genini release/* > setup.ini

with genini 1.13 from
http://cygwin.com/cgi-bin/cvsweb.cgi/genini/?cvsroot=cygwin-apps)
produces a lot of errors and warnings and the resulting setup.ini
is much smaller than the official one that comes with rsyncing
(300k vs 1300k).

So the question is: how is the official setup.ini created
from a release directory?


Regards,

Jens
-- 
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)

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

RE: Bad HTML on http://cygwin.com/mirrors.html

[Buchbinder, Barry (NIH/NIAID) [E]]

Jens Schweikhardt sent the following at Saturday, April 16, 2011 11:48 AM
>the bulleted list of mirrors on http://cygwin.com/mirrors.html looks
>like it has a problem.
>  Africa:
>  South Africa:  href="ftp://ftp.is.co.za/mirrors/cygwin/";>ftp.is.co.za(ftp)
>  Asia:
>
>   <--- this  should not be there.  
>
>The same goes for the other continents. You might want
>to check proper HTML syntax with a validator, e.g.
>http://validator.w3.org/check?uri=http%3A%2F%2Fcygwin.com%2Fmirrors.html
>&charset=%28detect+automatically%29&doctype=Inline&group=0

I think that the problem is the order, not the existence.


  Africa:

  South Africa: ftp://ftp.is.co.za/mirrors/cygwin/";>ftp.is.co.za(ftp)
   <-- this ends the  started just before "Africa".
   <-- this ends the  started between "Africa" and "South Africa".

I believe that a new list can be within a list element.

So I would flip the  and  for each continent.


  Africa:

  South Africa: ftp://ftp.is.co.za/mirrors/cygwin/";>ftp.is.co.za(ftp)



Does that work for you?

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.



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

Re: Bad HTML on http://cygwin.com/mirrors.html

[Jens Schweikhardt]

On Sat, Apr 16, 2011 at 04:14:15PM -0400, Buchbinder, Barry (NIH/NIAID) [E] 
wrote:
...
# Does that work for you?

I can't test this easily. The file identifies itself as "DTD XHTML 1.0
Strict" but doesn't conform. All that's needed is to make it proper
XHTML. The web maintainer can verify this with the validator I provided.

Regards,

Jens
-- 
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)

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

Re: Python Configuration for Cygwin

[Yaakov (Cygwin/X)]

On Fri, 2011-04-15 at 11:32 -0700, Gary Furash wrote:
> Given that I've installed python via the (excellent) Cygwin exe, and
> it seems to be working fine:
> 1. what else do I need to setup and how 

Nothing.

> (e.g., how should PYTHONPATH look on Cygwin)

Unset.

> 2. does Cygwin include the easy setup tools thing for python like it
> does for Perl (I think it's called setuptools)? If not, we probably
> should, as it makes it easy for newbies to install egg packages.

Not currently, but it is available in Ports (as python-setuptools).


Yaakov



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

Re: How is setup.ini generated these days?

[Yaakov (Cygwin/X)]

On Sat, 2011-04-16 at 21:01 +0200, Jens Schweikhardt wrote:
> I'm trying to make a package server as described on
> http://sourceware.org/cygwin-apps/package-server.html
> 
> I've rsynced the complete "release" tree (skipping *-legacy). However,
> running
> 
>   genini release/* > setup.ini
> 
> with genini 1.13 from
> http://cygwin.com/cgi-bin/cvsweb.cgi/genini/?cvsroot=cygwin-apps)
> produces a lot of errors and warnings and the resulting setup.ini
> is much smaller than the official one that comes with rsyncing
> (300k vs 1300k).

Many packages are in subdirectories of release.  Try this instead:

genini --output=setup.ini `find release/ -name setup.hint | sed 
's|/setup\.hint$||g'`


Yaakov



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