From: David Korn <dkorn@pixelpower.com>
To: gcc@gcc.gnu.org
Subject: RE: Removal of support for GCC hosted on UWIN
Date: Tue, 09 Jan 2001 02:15:00 -0000 [thread overview]
Message-ID: <718D38CAB6E0D011B2C90060970C28A564257C@EXCHANGESERVER> (raw)
>-----Original Message-----
>From: Alexandre Oliva [ mailto:aoliva@redhat.com ]
>Sent: 09 January 2001 09:14
>
>On Jan 9, 2001, Mark Mitchell <mark@codesourcery.com> wrote:
>
>> Note that GCC is merely a special case: it is a violation of the GPL
>> to link *any* GPL'd program with the U/WIN support library.
>
>I don't even know what U/WIN is but, AFAIK, the GNU GPL only covers
>the *distribution* of GNU GPLed programs or libraries. Linking with a
>proprietary library is legal, as long as you don't redistribute the
>result of the linking.
>
>I understand the removing support from U/WIN is a form of making it
>harder for someone to violate the GNU GPL, but I thought I'd point out
>that anyone is free to take the patch you're about to remove, install
>it in their own GCC source tree and build GCC for their own use.
>Right?
Wouldn't it be possible to just disable statically linking the shared lib?
Wouldn't that make it impossible to violate the GPL but allow the target
support to be retained ? [Please note that asking this question alas does
not amount to an offer to do the work - sorry!]
DaveK
--
The Boulder Pledge: "Under no circumstances will I ever purchase anything
offered to me as the result of an unsolicited email message. Nor will I
forward chain letters, petitions, mass mailings, or virus warnings to large
numbers of others. This is my contribution to the survival of the online
community."
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
next reply other threads:[~2001-01-09 2:15 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 2:15 David Korn [this message]
2001-01-09 2:19 ` Alexandre Oliva
2001-01-09 2:37 ` Nick Ing-Simmons
2001-01-09 2:41 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2001-01-10 15:45 dewar
2001-01-10 15:44 dewar
2001-01-10 15:23 dewar
2001-01-10 13:32 dewar
2001-01-10 15:09 ` Christopher Faylor
2001-01-10 13:29 dewar
2001-01-10 12:13 dewar
2001-01-10 15:30 ` Chris Faylor
2001-01-10 8:53 dewar
2001-01-10 8:52 dewar
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-09 14:00 dewar
2001-01-10 7:29 ` Christopher Faylor
2001-01-10 8:49 ` Joe Buck
2001-01-09 11:31 dewar
2001-01-09 9:34 Axel Kittenberger
2001-01-09 6:03 dewar
2001-01-09 5:39 dewar
2001-01-09 5:50 ` Nick Ing-Simmons
2001-01-09 5:16 dewar
2001-01-09 5:43 ` Nick Ing-Simmons
2001-01-09 4:09 Axel Kittenberger
2001-01-09 5:00 ` Florian Weimer
2001-01-09 3:55 dewar
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
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
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=718D38CAB6E0D011B2C90060970C28A564257C@EXCHANGESERVER \
--to=dkorn@pixelpower.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).