public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Alain Magloire" <alain@qnx.com>
To: gcc@gcc.gnu.org
Subject: Re: Removal of support for GCC hosted on UWIN
Date: Tue, 09 Jan 2001 13:12:00 -0000	[thread overview]
Message-ID: <200101092056.PAA24663@qnx.com> (raw)
In-Reply-To: <200101092056.MAA09350@racerx.synopsys.com>

> 
> 
> > Why? On a U/WIN host the Uwin library is a system library (because U/WIN is the
> > system), and the GPL allows linking with proprietary system libraries.
> 
> A user of U/WIN would be puzzled at the concept "a U/WIN host".
> Furthermore when a GPLed application is built for U/WIN, the result
> is not "a U/WIN application"; it is a Windows application, and can
> be used in the normal Windows environment and not just the U/WIN
> environment (ksh).
> 
> U/WIN is marketed as a package that runs on Windows systems that brings
> extra functionality to WIN32 applications.  I challenge anyone to find
> anything on
> 
> http://www.research.att.com/sw/tools/uwin/
> 
> that implies in any way that U/WIN is an OS.

Is not U/Win in the same category as CygWin ?  Or DJGPP for that matter ?


-- 
au revoir, alain
----
Aussi haut que l'on soit assis, on n'est toujours assis que sur son cul !!!

  reply	other threads:[~2001-01-09 13:12 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09  0:32 Mark Mitchell
2001-01-09  1:14 ` Alexandre Oliva
2001-01-09 10:00   ` Mark Mitchell
2001-01-09  3:33 ` Andi Kleen
2001-01-09 10:03   ` Mark Mitchell
2001-01-09 10:37     ` Mumit Khan
2001-01-09 10:47       ` Mark Mitchell
2001-01-09 11:11         ` Christopher Faylor
2001-01-09 11:18       ` Jeffrey A Law
2001-01-09 12:36       ` Joe Buck
2001-01-09 14:46     ` Joseph S. Myers
2001-01-09 15:38       ` Mark Mitchell
     [not found]         ` <mailpost.979083538.10676@postal.sibyte.com>
2001-01-09 16:23           ` Chris G. Demetriou
2001-01-09 17:05             ` Mark Mitchell
2001-01-09 21:11               ` Mumit Khan
2001-01-10  2:10                 ` Joseph S. Myers
2001-01-10  7:32                 ` Christopher Faylor
2001-01-09 17:51             ` Joe Buck
2001-01-09 22:33             ` Richard Stallman
2001-01-09 12:57   ` Joe Buck
2001-01-09 13:12     ` Alain Magloire [this message]
2001-01-09 13:21       ` Joe Buck
2001-01-09 22:24       ` Laurynas Biveinis
2001-01-09  3:52 ` Michael Widenius
2001-01-09  9:07   ` Alexandre Oliva
2001-01-09 10:06   ` Mark Mitchell
2001-01-09 10:24     ` Jeffrey A Law
2001-01-09  2:15 David Korn
2001-01-09  2:19 ` Alexandre Oliva
2001-01-09  2:37   ` Nick Ing-Simmons
2001-01-09  2:41     ` Alexandre Oliva
2001-01-09  3:55 dewar
2001-01-09  4:09 Axel Kittenberger
2001-01-09  5:00 ` Florian Weimer
2001-01-09  5:16 dewar
2001-01-09  5:43 ` Nick Ing-Simmons
2001-01-09  5:39 dewar
2001-01-09  5:50 ` Nick Ing-Simmons
2001-01-09  6:03 dewar
2001-01-09  9:34 Axel Kittenberger
2001-01-09 11:31 dewar
2001-01-09 14:00 dewar
2001-01-10  7:29 ` Christopher Faylor
2001-01-10  8:49   ` Joe Buck
2001-01-10  7:43 dewar
2001-01-10 11:18 ` Chris Faylor
2001-01-10 13:15 ` Geoff Keating
2001-01-10  7:43 dewar
2001-01-10  8:52 dewar
2001-01-10  8:53 dewar
2001-01-10 12:13 dewar
2001-01-10 15:30 ` Chris Faylor
2001-01-10 13:29 dewar
2001-01-10 13:32 dewar
2001-01-10 15:09 ` Christopher Faylor
2001-01-10 15:23 dewar
2001-01-10 15:44 dewar
2001-01-10 15:45 dewar

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=200101092056.PAA24663@qnx.com \
    --to=alain@qnx.com \
    --cc=gcc@gcc.gnu.org \
    /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).