From: dlundy AT primenet DOT com (Dan Lundy) Subject: cygwin.dll 1 Jan 1998 18:34:04 -0800 Message-ID: <001501bd1722$f9d5b0a0$ba32a5ce.cygnus.gnu-win32@primenet.primenet.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01BD16F0.AC61E1E0" To: This is a multi-part message in MIME format. ------=_NextPart_000_0012_01BD16F0.AC61E1E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Upon installing and attempting to execute a .exe put together by the =3D GNUWin32 stuff, I continually receive "STATUS_ACCESS_VIOLATION" from =3D cygwin.dll in the bygwin except handler. So I chalked it up to a crappy .exe, but I thought the GNUWin32 concept = =3D was interesting - having toyed with C++ and such briefly in the past. = =3D As such, I downloaded and installed all the stuff I could gt ahold of. After reading the installation notes, and carefully doing everything =3D described - I ventured into some source, determined to make my own =3D executable, one that worked. The shell seems to work fine, with all functions available (even created = =3D and properly mounted /tmp!). Problem is, when i invoke a ./configure command, the config fails in the = =3D same manner as above (when attempting to call awk.exe). Another oddity = =3D is when I attempt to use make.exe, the same failure occurs in the cygwin = =3D except handler. Since this is occuring in 3 (probably more) independant circumstances, I = =3D am guessing that it is a problem with my install, or the version i have = =3D of cygwin.dll (the original b18 version). All this is occuring on a stand-alone Win95 machine with no other known = =3D problems. Any tips, suggestions, or comments are welcome. Keep up the good work dlundy AT primenet DOT com ------=_NextPart_000_0012_01BD16F0.AC61E1E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
<insert "I am an idiot" disclaimers = here>

Upon=20 installing and attempting to execute a .exe put together by the = =3D
GNUWin32=20 stuff, I continually receive "STATUS_ACCESS_VIOLATION" from=20 =3D
cygwin.dll in the bygwin except handler.

So I chalked it = up to a=20 crappy .exe, but I thought the GNUWin32 concept =3D
was interesting - = having=20 toyed with C++ and such briefly in the past.  =3D
As such, I = downloaded=20 and installed all the stuff I could gt ahold of.

After reading = the=20 installation notes, and carefully doing everything =3D
described - I = ventured=20 into some source, determined to make my own =3D
executable, one that=20 worked.

The shell seems to work fine, with all functions = available (even=20 created =3D
and properly mounted /tmp!).

Problem is, when i = invoke a=20 ../configure command, the config fails in the =3D
same manner as above = (when=20 attempting to call awk.exe).  Another oddity =3D
is when I = attempt to use=20 make.exe, the same failure occurs in the cygwin =3D
except=20 handler.

Since this is occuring in 3 (probably more) independant=20 circumstances, I =3D
am guessing that it is a problem with my = install, or the=20 version i have =3D
of cygwin.dll (the original b18 = version).

All this is=20 occuring on a stand-alone Win95 machine with no other known = =3D
problems. =20 Any tips, suggestions, or comments are welcome.

Keep up the good=20 work
dlundy AT primenet DOT com





------=_NextPart_000_0012_01BD16F0.AC61E1E0-- - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".