public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Colin Peters <colin@bird.fu.is.saga-u.ac.jp>
To: "'GNU-Win32'" <gnu-win32@cygnus.com>
Subject: RE: Default compiler behaviour for b19
Date: Wed, 10 Sep 1997 22:54:00 -0000	[thread overview]
Message-ID: <01BCBEC1.983C8580@gbird0> (raw)

Fergus Henderson[SMTP:fjh@cs.mu.OZ.AU] wrote:
>Geoffrey Noer <noer@cygnus.com> writes:
>
>>Anthony Wesley wrote:
>>> 
>>> Perhaps I am misreading the comments on the gnuwin32 home page, but it
>>> looks like Cygnus are proposing to have "gcc -o foo foo.c" generate
>>> native win32 binaries by default and not link with cygwin.dll. To
>>> compile UNIX-ish tools and link with the cygwin.dll library you will
>>> have to supply an extra command line option.
>>
>>Yes, and this may still happen at some point down the road.
>
>I have to agree with Anthony Wesley that this would be a Bad Idea.

At first I was going to say that either default would be fine if
you could override the default with an environment variable, and
override the environment variable or default with a command line
option. This would give the user maximum flexibility and
convenience.

However, I thought about it a bit, and I have to agree that
'gcc' should by default have the compatibility layer enabled. I
still think you should be able to override the default in the
way above though.

The reason I think gcc should, by default, be UNIX is simply
that all extant shell scripts which call gcc, without any
other options, are basically UNIX-centric. If you are running
one of these shell scripts then you are running in a UNIX-like
environment. The shell script will no doubt include other UNIX
isms. New scripts written with the Win32 port in mind can
include an option to behave natively, but making gcc act
differently by default can only break older scripts and offer
very little benefit to new programmers.

Of course one can, and should, be able to recompile gcc to
target Win32 native with no UNIX compatibility layer, with
the understanding that this retargeted gcc, like any gcc
targeted at a non-UNIX machine, will not always behave as
expected by UNIX scripts or when compiling UNIX code.

Well, that's my opinion, for what it's worth. :-/

Colin.

-- Colin Peters - Saga Univ. Dept. of Information Science
-- colin@bird.fu.is.saga-u.ac.jp - finger for PGP public key
-- http://www.fu.is.saga-u.ac.jp/~colin/index.html
-- http://www.geocities.com/Tokyo/Towers/6162/

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

             reply	other threads:[~1997-09-10 22:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-10 22:54 Colin Peters [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-09-09  3:50 Sonic Junior
1997-09-04 21:18 Anthony Wesley
1997-09-09  3:50 ` Geoffrey Noer
1997-09-09 23:33   ` Fergus Henderson
1997-09-11  9:20     ` Christian Soeller
1997-09-09 23:33 ` Andrey A. Kulaga
1997-09-11 10:10   ` AECEULA, QUEST Team
1997-09-12  9:32     ` Earnie Boyd
1997-09-12 12:07     ` M. Halpin

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=01BCBEC1.983C8580@gbird0 \
    --to=colin@bird.fu.is.saga-u.ac.jp \
    --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).