Re: cygwin 1.5.25-7: cygcheck does not work?

2007-12-21 Thread Alexey Lyubimov
Thanks, Brian!
But what would be the final decision? As far as I
understand 1.5.x branch MUST support Win98. Am I
right?
Should I wait for 1.5.25-8 (where hard dependencies on
NT-dll would be removed, I hope) or should I downgrade
to some previous 1.5.25-x?

--
Alexey
 
Brian Dessent wrote:

The problem is that bloda.c calls
NtQuerySystemInformation without using
any kind of autoload.cc-type indirection, and so
cygcheck gets a hard
dependency on ntdll.dll which doesn't exist on 9x/ME.
 We need to do one
of:

- Revert the bloda-check feature on the 1.5 branch
- Check windows version at runtime and only do NT
calls through
LoadLibrary/GetProcAddress
- Use the autoload.cc trick in cygcheck

If we're going to make releases from the 1.5 branch
then I don't think


  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping


--
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 1.5.25-7: cygcheck does not work?

2007-12-21 Thread Dave Korn
On 21 December 2007 12:41, Alexey Lyubimov wrote:

 Thanks, Brian!
 But what would be the final decision? As far as I
 understand 1.5.x branch MUST support Win98. Am I
 right?
 Should I wait for 1.5.25-8 (where hard dependencies on
 NT-dll would be removed, I hope) or should I downgrade
 to some previous 1.5.25-x?

  Possibly the best solution for now would be:

1.  downgrade to working 1.5.25-x
2.  cp /bin/cygcheck.exe /tmp
3.  upgrade back to 1.5.25-7
4.  cp /tmp/cygcheck.exe /bin

i.e. just save the good version of cygcheck from the old version of the install.

cheers,
  DaveK
-- 
Can't think of a witty .sigline today


--
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 1.5.25-7: cygcheck does not work?

2007-12-21 Thread Christopher Faylor
On Fri, Dec 21, 2007 at 02:38:28PM -, Dave Korn wrote:
On 21 December 2007 12:41, Alexey Lyubimov wrote:

 Thanks, Brian!
 But what would be the final decision? As far as I
 understand 1.5.x branch MUST support Win98. Am I
 right?
 Should I wait for 1.5.25-8 (where hard dependencies on
 NT-dll would be removed, I hope) or should I downgrade
 to some previous 1.5.25-x?

  Possibly the best solution for now would be:

1.  downgrade to working 1.5.25-x
2.  cp /bin/cygcheck.exe /tmp
3.  upgrade back to 1.5.25-7
4.  cp /tmp/cygcheck.exe /bin

i.e. just save the good version of cygcheck from the old version of the 
install.

Or, just download a snapshot and extract cygcheck.exe from it.

cgf

--
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 1.5.25-7: cygcheck does not work?

2007-12-20 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Alexey Lyubimov on 12/20/2007 6:38 AM:
 After upgrading to cygwin 1.5.25-7 I get error message
 from BASH every time I want to run cygcheck:
 
 $ cygcheck
 BASH: ./cygcheck: Function not implemented

Odd.  Cygwin's bash does not usually capitalize it's name.  You might have
other competing software in the way (which we would know if you had
cygcheck output ;).  And the fact that it is talking about ./cygcheck
makes me think that you have a script file named cygcheck in the current
directory.  It would be interesting to see the output of 'which cygcheck'.
 Also, try an absolute path: /bin/cygcheck -svr.  Or use Windows'
command.com, browse to the right directory (probably c:\cygwin\bin), and
do .\cygcheck -svr from there.

 
 The OS: Windows 98 SE

Rather old; I hope you're aware that cygwin 1.7.0 won't run on your OS,
and that, as bash maintainer, I no longer have access to Win98 to
investigate any bug reports caused by the brokenness of the older OS.

- --
Don't work too hard, make some time for fun as well!

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

iD8DBQFHanJt84KuGfSFAYARAmkWAKDCDaFNMeqUNtAL8qAPHLbkXVebQwCfYdz2
1PexIxmv7cPXWdhAuQjH4Y4=
=pmyp
-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: cygwin 1.5.25-7: cygcheck does not work?

2007-12-20 Thread Brian Dessent
Eric Blake wrote:

 Odd.  Cygwin's bash does not usually capitalize it's name.  You might have

That's a Win9x oddity.

  The OS: Windows 98 SE
 
 Rather old; I hope you're aware that cygwin 1.7.0 won't run on your OS,
 and that, as bash maintainer, I no longer have access to Win98 to
 investigate any bug reports caused by the brokenness of the older OS.

Fortunately, I have VMware with a Win98 image here.

The problem is that bloda.c calls NtQuerySystemInformation without using
any kind of autoload.cc-type indirection, and so cygcheck gets a hard
dependency on ntdll.dll which doesn't exist on 9x/ME.  We need to do one
of:

- Revert the bloda-check feature on the 1.5 branch
- Check windows version at runtime and only do NT calls through
LoadLibrary/GetProcAddress
- Use the autoload.cc trick in cygcheck

If we're going to make releases from the 1.5 branch then I don't think
it's quite acceptible just yet to shaft 9x users, after all that's the
whole point of the branch.

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: cygwin 1.5.25-7: cygcheck does not work?

2007-12-20 Thread Jeff
On Thu, 20 Dec 2007 06:15:11 -0800,
Brian Dessent brian[at]dessent[dot]net wrote:

Eric Blake wrote:

 Odd.  Cygwin's bash does not usually capitalize it's name.  You might have

That's a Win9x oddity.

  The OS: Windows 98 SE
 
 Rather old; I hope you're aware that cygwin 1.7.0 won't run on your OS,
 and that, as bash maintainer, I no longer have access to Win98 to
 investigate any bug reports caused by the brokenness of the older OS.

Fortunately, I have VMware with a Win98 image here.

The problem is that bloda.c calls NtQuerySystemInformation without using
any kind of autoload.cc-type indirection, and so cygcheck gets a hard
dependency on ntdll.dll which doesn't exist on 9x/ME.

This is exactly why I have 'File Monitor' from Sysinternals on my
system. Whenever I have an app that fails to start and produces some
incomprehensible error message (relative to my setup, current state of
my system, location of files, etc.), I run 'File Monitor' to see if the
app is looking for libraries or other crucial files and not finding
them. (It's also a great utility for discovering where apps are
hiding various settings and information files.) For someone like me
who is only at the level of a moderately knowledgeable user, 'File
Monitor' and a good process viewer are invaluable tools for getting a
head start on troubleshooting problems.

I've found very few apps that are able to tell the user when a library
file is missing-- the SOP of just calling library functions from within
your code and then linking against an import library includes, as far
as I know, no mechanism to do that (unless, perhaps, it is somehow
built into the library). In most cases, if the file is missing, it
would seem that the results are undefined-- in my experience, though,
the app usually exits with some sort of baffling error message.

-- 
Sorry, my life is still in beta, and nowhere near stable enough for a
release.

--
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 1.5.25-7: cygcheck does not work?

2007-12-20 Thread Dave Korn
On 20 December 2007 18:46, Jeff wrote:

 This is exactly why I have 'File Monitor' from Sysinternals on my
 system. Whenever I have an app that fails to start and produces some
 incomprehensible error message (relative to my setup, current state of
 my system, location of files, etc.), I run 'File Monitor' to see if the
 app is looking for libraries or other crucial files and not finding
 them. 

  FYI, cygcheck path/to/exe also does that.


 I've found very few apps that are able to tell the user when a library
 file is missing-- the SOP of just calling library functions from within
 your code and then linking against an import library includes, as far
 as I know, no mechanism to do that (unless, perhaps, it is somehow
 built into the library). In most cases, if the file is missing, it
 would seem that the results are undefined-- in my experience, though,
 the app usually exits with some sort of baffling error message.

  Yep.  It's a limitation of both the LoadLibrary() *and* the dlopen() function 
that
they can't tell you /which/ file was missing.

cheers,
  DaveK
-- 
Can't think of a witty .sigline today   


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