public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Jonathan Pryor" <jonpryor@vt.edu>
To: "Geoffrey Noer" <noer@cygnus.com>,
	"Mumit Khan" <khan@xraylith.wisc.EDU>,
	"Cygwin Mailing List" <cygwin@sourceware.cygnus.com>
Subject: Re: Compiled executable differences between 9x and NT
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <0ac501be6a83$48632630$e63d2509@jonpryor.raleigh.ibm.com> (raw)
Message-ID: <19990331194500.H7C1JDd_yS5MOEjl8bxoppJi-gseIeXIKyPq1Bq2cR0@z> (raw)

A tarball of the source is available at:

http://www.acm.vt.edu/~jonpryor/Projects/gecl.tgz

Readme.txt (in the tarball) includes directions on
compiling the program, as well as descriptions of 
the observed crash under 95.

<snip>

>9x and NT have different sets of bugs and features.  Cygwin
>checks which OS is running and uses this info to provide the
>a Unix layer that should make Cygwin applications run
>the same under either OS.  (Of course while this is the
>goal, sometimes this doesn't quite happen).


Cygwin isn't there yet, but it's getting close.  Thank you
for the effort.

<snip>

>Ah, you're using mingw.  So Cygwin is probably
>not relevant.  Hmmm, well, I've noticed that Windows
>9x often is more sensitive to buggy exes.  Perhaps
>you're running into a compiler issue?


Actually, I'm trying to use as many compilers as I can.
Thus, I'm compiling with cygwin, mingw32, and MSVC.
(I would also try DJGPP, but I had some configuration
issues I still need to deal with...)

As for compiler issues...  I seem to have run into a fair
number of them trying to develop the program.  I sent out
a prior message detailing 3 template-related bugs to the
cygwin list (as well as to egcs-bugs).  I believe I've
worked around them, but it's possible I missed a few.

>-- 
>Geoffrey Noer Email: noer@cygnus.com
>Cygnus Solutions
>


Thanks,
 - Jon



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


             reply	other threads:[~1999-03-31 19:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-09 15:19 Jonathan Pryor [this message]
     [not found] ` < 0ac501be6a83$48632630$e63d2509@jonpryor.raleigh.ibm.com >
1999-03-09 17:07   ` Mumit Khan
1999-03-31 19:45     ` Mumit Khan
1999-03-31 19:45 ` Jonathan Pryor
  -- strict thread matches above, loose matches on Subject: below --
1999-03-12 11:57 Jonathan Pryor
1999-03-31 19:45 ` Jonathan Pryor
1999-03-12  6:06 Suhaib M. Siddiqi
1999-03-31 19:45 ` Suhaib M. Siddiqi
1999-03-12  5:17 Jonathan Pryor
     [not found] ` < 0f3801be6c8a$9c41d7c0$e63d2509@jonpryor.raleigh.ibm.com >
1999-03-12 10:58   ` Glenn Spell
1999-03-31 19:45     ` Glenn Spell
1999-03-31 19:45 ` Jonathan Pryor
1999-03-11  7:37 Jonathan Pryor
1999-03-31 19:45 ` Jonathan Pryor
1999-03-10  4:59 Jonathan Pryor
1999-03-11  7:03 ` Anders Norlander
     [not found]   ` < 36E7DAFC.7D1AE3AC@hem2.passagen.se >
1999-03-11  7:08     ` Mumit Khan
1999-03-11  7:17       ` neud
1999-03-31 19:45         ` neud
     [not found]       ` < 199903111508.JAA27393@modi.xraylith.wisc.edu >
1999-03-11 19:14         ` Glenn Spell
1999-03-31 19:45           ` Glenn Spell
1999-03-31 19:45       ` Mumit Khan
1999-03-31 19:45   ` Anders Norlander
1999-03-31 19:45 ` Jonathan Pryor
1999-03-09  5:43 Jonathan Pryor
1999-03-31 19:45 ` Jonathan Pryor
1999-03-08 18:37 N8TM
1999-03-31 19:45 ` N8TM
1999-03-08  6:21 Jonathan Pryor
     [not found] ` < 088201be696e$f2867650$e63d2509@jonpryor.raleigh.ibm.com >
1999-03-09 12:20   ` Geoffrey Noer
1999-03-31 19:45     ` Geoffrey Noer
1999-03-09 12:27   ` Mumit Khan
1999-03-31 19:45     ` Mumit Khan
1999-03-31 19:45 ` Jonathan Pryor

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='0ac501be6a83$48632630$e63d2509@jonpryor.raleigh.ibm.com' \
    --to=jonpryor@vt.edu \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=khan@xraylith.wisc.EDU \
    --cc=noer@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).