public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Dan Lundy" <dlundy@primenet.com>
To: <gnu-win32@cygnus.com>
Subject: cygwin.dll
Date: Thu, 01 Jan 1998 18:15:00 -0000	[thread overview]
Message-ID: <001501bd1722$f9d5b0a0$ba32a5ce@primenet.primenet.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]

<insert "I am an idiot" disclaimers here> Upon 
installing and attempting to execute a .exe put together by the = GNUWin32 
stuff, I continually receive "STATUS_ACCESS_VIOLATION" from 
= cygwin.dll in the bygwin except handler. So I chalked it up to a 
crappy .exe, but I thought the GNUWin32 concept = was interesting - having 
toyed with C++ and such briefly in the past.  = As such, I downloaded 
and installed all the stuff I could gt ahold of. After reading the 
installation notes, and carefully doing everything = described - I ventured 
into some source, determined to make my own = executable, one that 
worked. The shell seems to work fine, with all functions available (even 
created = and properly mounted /tmp!). Problem is, when i invoke a 
./configure command, the config fails in the = same manner as above (when 
attempting to call awk.exe).  Another oddity = is when I attempt to use 
make.exe, the same failure occurs in the cygwin = except 
handler. Since this is occuring in 3 (probably more) independant 
circumstances, I = am guessing that it is a problem with my install, or the 
version i have = of cygwin.dll (the original b18 version). All this is 
occuring on a stand-alone Win95 machine with no other known = problems.  
Any tips, suggestions, or comments are welcome. Keep up the good 
work dlundy@primenet.com

             reply	other threads:[~1998-01-01 18:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-01 18:15 Dan Lundy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-26 13:55 cygwin.dll Cserveni Akos
2000-01-25  8:27 cygwin.dll Nguyen, Dien
2000-01-25  9:22 ` cygwin.dll Randall R Schulz
     [not found] <3AC9A1611DF4D211AA8E00105AA56D8A0493CF@IIS000.microdata.fr>
1999-04-27  9:44 ` cygwin.dll Bruce Seely
1999-04-30 18:32   ` cygwin.dll Bruce Seely
1999-04-27  4:50 cygwin.dll Earnie Boyd
1999-04-30 18:32 ` cygwin.dll Earnie Boyd
1999-04-26 18:01 cygwin.dll Bruce Seely
1999-04-30 18:32 ` cygwin.dll Bruce Seely
1998-01-02  9:02 cygwin.dll Earnie Boyd
1997-10-29 17:07 cygwin.dll Tommy Reilly
1997-09-04 21:18 cygwin.dll marta
1997-02-12 16:36 cygwin.dll Who cares...

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001501bd1722$f9d5b0a0$ba32a5ce@primenet.primenet.com' \
    --to=dlundy@primenet.com \
    --cc=gnu-win32@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).