On Mar 14 09:34, Jun-ya Kato wrote:
> It also depends on query againt VMware's DNS proxy server.
>
> For more analysis, see vmware community site,
> https://communities.vmware.com/thread/518949?start=15&tstart=0
>
>
> I think it is not cygwin's bug at all. but any workaround may be
> implem
$ uname -a
CYGWIN_NT-6.1-WOW HARRYR-PC 2.4.1(0.293/5/3) 2016-01-24 11:24 i686 Cygwin
I have had warnings and errors about fonts ever since - something changed.
I'm looking at the index of Cygwin FAQ and there is not a single question
matching 'font'.
Where do I need to go to match up my font is
On a 32 bit Cygwin installation on a Windows 7 host that is a few years old:
$ uname -a
CYGWIN_NT-6.1-WOW64 DET000-DAC1 1.7.17(0.262/5/3) 2012-10-19 14:39 i686
Cygwin
running ldd on a newly built executable gives:
$ ldd z12.exe
ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x77df)
On 2016-03-14 09:54, Rockefeller, Harry wrote:
I have had warnings and errors about fonts ever since - something changed.
I'm looking at the index of Cygwin FAQ and there is not a single question
matching 'font'.
Where do I need to go to match up my font issue (warning or error) on a
particul
The ctrl-c shortcut doesn't reliably kill applications (anymore?).
It has been that way for at least a year now.
One example is the ruby "rerun" tool (at least when used with a sinatra
app).
The problem can be reproduced usi
The following packages have been uploaded to the Cygwin distribution:
* vim-7.4.1558-1
* vim-common-7.4.1558-1
* vim-minimal-7.4.1558-1
* gvim-7.4.1558-1
* xxd-7.4.1558-1
* vim-doc-7.4.1558-1
Vim (Vi IMproved) is an almost compatible version of the UNIX editor vi.
Almost every possible command c
The following packages have been uploaded to the Cygwin distribution:
* xterm-324-1
The xterm program is a terminal emulator for the X Window System. It
provides DEC VT102 and Tektronix 4014 compatible terminals for programs
that can't use the window system directly. This version implements
IS
Roger Wells writes:
> running ldd on a newly built executable gives:
[…]
> What I really need is a reliable way to get a recursive listing of the
> complete path to all dependencies.
> I tried using Dependency Walker (both 32 & 64 bit) but it does not seem
> to run on W10.
Try cygcheck rather than
On 03/14/2016 01:38 PM, Achim Gratz wrote:
> Roger Wells writes:
>> running ldd on a newly built executable gives:
> […]
>> What I really need is a reliable way to get a recursive listing of the
>> complete path to all dependencies.
>> I tried using Dependency Walker (both 32 & 64 bit) but it does
>-Original Message-
>From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of
>Yaakov Selkowitz
>Sent: Monday, March 14, 2016 10:37 AM
>To: cygwin@cygwin.com
>Subject: Re: font faq
>
>On 2016-03-14 09:54, Rockefeller, Harry wrote:
>> I have had warnings and errors about
Roger Wells writes:
>> Try cygcheck rather than ldd.
>>
> Thanks for responding.
>
> Here's what happens:
>
> $ cygcheck ./z12.exe
> C:\cygwin64\home\roger\src\z12\z12.exe
>
> or
>
> $ cygcheck --verbose ./z12.exe
> C:\cygwin64\home\roger\src\z12\z12.exe (not x86_64 dll)
Then it doesn't seem to b
The _autorebase package has been re-relaesd to fix a packaging error
that resulted in too restricted permissions for the installed script
files. No other changes have been made.
--
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailin
On 03/14/2016 03:09 PM, Achim Gratz wrote:
> Roger Wells writes:
>>> Try cygcheck rather than ldd.
>>>
>> Thanks for responding.
>>
>> Here's what happens:
>>
>> $ cygcheck ./z12.exe
>> C:\cygwin64\home\roger\src\z12\z12.exe
>>
>> or
>>
>> $ cygcheck --verbose ./z12.exe
>> C:\cygwin64\home\roger\sr
On 03/14/2016 03:50 PM, Roger Wells wrote:
> On 03/14/2016 03:09 PM, Achim Gratz wrote:
>> Roger Wells writes:
Try cygcheck rather than ldd.
>>> Thanks for responding.
>>>
>>> Here's what happens:
>>>
>>> $ cygcheck ./z12.exe
>>> C:\cygwin64\home\roger\src\z12\z12.exe
>>>
>>> or
>>>
>>> $
On 14.03.2016 10:18, Björn Stabel wrote:
My eyes blinked there for a second! Nope, not the Xpilot
co-author, Norwegian Bjørn Stabell.
:)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
I have been having this problem with "ping". If I "ping" a location that
doesn't exist, then "ping" just hangs and cannot be killed via "kill -KILL [pid]".
A little digression, so you understand the background ... The workstation I am
doing this from is connected to a Verizon router to their F
> Is anybody here affected by this problem willing to give this a test?
> I can create another Cygwin 2.5.0 test release pretty soon...
I think it's useful workaround for cygwin user under VMware NAT.
I'd like to test it.
From: Corinna Vinschen
Subject: Re: Cygwin unable to resolve hostname
17 matches
Mail list logo