Re: where the streets and servers have no name, cyglwres-xx.dll?

2010-09-21 Thread mike marchywka
On 9/21/10, David Sastre  wrote:
> On Tue, Sep 21, 2010 at 04:43:25PM -0500, mike marchywka wrote:
>> On 9/21/10, David Sastre wrote:
>> > On Tue, Sep 21, 2010 at 02:38:37PM -0500, mike marchywka wrote:
>> >> Hi,
>>
>> > Can you please attach it, as described here?
>> >
>> >> Problem reports:   http://cygwin.com/problems.html
>> >
>> attached, thanks. I seem to recall the install
>> went well so this is a bit surprising but I have reported
>> isolated bizarre things on Windoze 7 multicore 64 bit...
>> It looked like it got some -50 dlls with same name.
>
> I couldn't find the dll in your cygcheck.out...
> Do you have liblwres60 installed?
> Try cygcheck -c liblwres60. If you already have it, try reinstalling
> it.
>
... arrgh I ended up reinstalling everything, still doing post install
scripts. There was no indication the dll was there, just
the -50 instead of -60 version it wanted. I'll have to
see if everything still works, reboot, etc and then get
back to this. I think it may be fine if I could just
copy the dll instead of actually installing anything.





> This is the output of cygcheck $(which nslookup) in a 32bits Win7
>
> C:\cygwin\bin\nslookup.exe
>   C:\cygwin\bin\cygbind9-60.dll
> C:\cygwin\bin\cygdns-66.dll
>   C:\cygwin\bin\cygisc-60.dll
> C:\cygwin\bin\cyggcc_s-1.dll
>   C:\cygwin\bin\cygwin1.dll
> C:\Windows\system32\ADVAPI32.DLL
>   C:\Windows\system32\msvcrt.dll
> C:\Windows\system32\KERNELBASE.dll
>   C:\Windows\system32\ntdll.dll
> C:\Windows\system32\API-MS-Win-Core-Console-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-DateTime-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-Interlocked-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
>
> C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
>
> C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
>   C:\Windows\system32\API-MS-WIN-Service-Core-L1-1-0.dll
>   C:\Windows\system32\API-MS-WIN-Service-winsvc-L1-1-0.dll
>   C:\Windows\system32\API-MS-WIN-Service-Management-L1-1-0.dll
>   C:\Windows\system32\API-MS-WIN-Service-Management-L2-1-0.dll
>   C:\Windows\system32\API-MS-Win-Core-LocalRegistry-L1-1-0.dll
>   C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
>   C:\Windows\system32\KERNEL32.dll
> C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
> C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
>   C:\Windows\system32\RPCRT4.dll
> C:\Windows\system32\API-MS-Win-Core-DelayLoad-L1-1-0.dll
> C:\cygwin\bin\cygxml2-2.dll
>   C:\cygwin\bin\cygz.dll
>   C:\cygwin\bin\cygiconv-2.dll
>   C:\cygwin\bin\cygcrypto-0.9.8.dll
> C:\cygwin\bin\cygisccfg-60.dll
>   C:\cygwin\bin\cyglwres-60.dll <-
> C:\Windows\system32\IPHLPAPI.DLL
>   C:\Windows\system32\NSI.dll
>   C:\Windows\system32\WINNSI.DLL
>   C:\cygwin\bin\cygidn-11.dll
> C:\cygwin\bin\cygintl-8.dll
>
>>

--
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: where the streets and servers have no name, cyglwres-xx.dll?

2010-09-21 Thread David Sastre
On Tue, Sep 21, 2010 at 04:43:25PM -0500, mike marchywka wrote:
> On 9/21/10, David Sastre wrote:
> > On Tue, Sep 21, 2010 at 02:38:37PM -0500, mike marchywka wrote:
> >> Hi,
> 
> > Can you please attach it, as described here?
> >
> >> Problem reports:   http://cygwin.com/problems.html 
> >
> attached, thanks. I seem to recall the install
> went well so this is a bit surprising but I have reported
> isolated bizarre things on Windoze 7 multicore 64 bit...
> It looked like it got some -50 dlls with same name.

I couldn't find the dll in your cygcheck.out...
Do you have liblwres60 installed?
Try cygcheck -c liblwres60. If you already have it, try reinstalling
it.

This is the output of cygcheck $(which nslookup) in a 32bits Win7 

C:\cygwin\bin\nslookup.exe
  C:\cygwin\bin\cygbind9-60.dll
C:\cygwin\bin\cygdns-66.dll
  C:\cygwin\bin\cygisc-60.dll
C:\cygwin\bin\cyggcc_s-1.dll
  C:\cygwin\bin\cygwin1.dll
C:\Windows\system32\ADVAPI32.DLL
  C:\Windows\system32\msvcrt.dll
C:\Windows\system32\KERNELBASE.dll
  C:\Windows\system32\ntdll.dll
C:\Windows\system32\API-MS-Win-Core-Console-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-DateTime-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Interlocked-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll

C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
  C:\Windows\system32\API-MS-WIN-Service-Core-L1-1-0.dll
  C:\Windows\system32\API-MS-WIN-Service-winsvc-L1-1-0.dll
  C:\Windows\system32\API-MS-WIN-Service-Management-L1-1-0.dll
  C:\Windows\system32\API-MS-WIN-Service-Management-L2-1-0.dll
  C:\Windows\system32\API-MS-Win-Core-LocalRegistry-L1-1-0.dll
  C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
  C:\Windows\system32\KERNEL32.dll
C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
  C:\Windows\system32\RPCRT4.dll
C:\Windows\system32\API-MS-Win-Core-DelayLoad-L1-1-0.dll
C:\cygwin\bin\cygxml2-2.dll
  C:\cygwin\bin\cygz.dll
  C:\cygwin\bin\cygiconv-2.dll
  C:\cygwin\bin\cygcrypto-0.9.8.dll
C:\cygwin\bin\cygisccfg-60.dll
  C:\cygwin\bin\cyglwres-60.dll <-
C:\Windows\system32\IPHLPAPI.DLL
  C:\Windows\system32\NSI.dll
  C:\Windows\system32\WINNSI.DLL
  C:\cygwin\bin\cygidn-11.dll
C:\cygwin\bin\cygintl-8.dll

> --
> 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


-- 
Huella de clave primaria: 0FDA C36F F110 54F4 D42B  D0EB 617D 396C 448B 31EB


signature.asc
Description: Digital signature


Re: where the streets and servers have no name, cyglwres-xx.dll?

2010-09-21 Thread David Sastre
On Tue, Sep 21, 2010 at 02:38:37PM -0500, mike marchywka wrote:
> Hi,
> I've been having a problem with name lookups but it only seems to
> effect a few things. I think lynx is ok, but then I tried to ftp and
> couldn't find host name . I had first seen this
> with nslookup but ignored it at the time,
> 
> $ nslookup google.com
> /usr/bin/nslookup.exe: error while loading shared libraries: cyglwres-60.dll: 
> ca
> nnot open shared object file: No such file or directory

You could try 

ldd /usr/bin/nslookup 

and/or 

cygcheck -c $(cygcheck -f $(which nslookup)) 

to find out if cyglwres-60.dll is really missing. It should give you 
the full path where the dll is supposed to be found. You can check
that path to see if it's there, permissions, ...

(Sorry, I don't have a cygwin installation around ATM)

> I got this result from cygcheck, wasn't sure if there was something obvious
> I did or easiest way to fix. Thanks.
> 
> $ cygcheck -s > cygcheckout

Can you please attach it, as described here?

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

Regards.

-- 
Huella de clave primaria: 0FDA C36F F110 54F4 D42B  D0EB 617D 396C 448B 31EB


signature.asc
Description: Digital signature


where the streets and servers have no name, cyglwres-xx.dll?

2010-09-21 Thread mike marchywka
Hi,
I've been having a problem with name lookups but it only seems to
effect a few things. I think lynx is ok, but then I tried to ftp and
couldn't find host name . I had first seen this
with nslookup but ignored it at the time,

$ nslookup google.com
/usr/bin/nslookup.exe: error while loading shared libraries: cyglwres-60.dll: ca
nnot open shared object file: No such file or directory

I got this result from cygcheck, wasn't sure if there was something obvious
I did or easiest way to fix. Thanks.

$ cygcheck -s > cygcheckout

$ grep wres cygcheckout
   88k 2009/06/16 C:\cygwin\bin\cyglwres-50.dll
   88k 2009/06/16 C:\cygwin\bin\cyglwres-50.dll
liblwres-devel 9.7.1-1
liblwres50 9.6.0_p1-1
liblwres60 9.7.1-1
viewres1.0.2-1

--
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