From owner-cvs-user Mon Mar 13 17:42:24 1995 Return-Path: cvs-user-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA04778 for cvs-user-outgoing; Mon, 13 Mar 1995 17:42:24 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA04766; Mon, 13 Mar 1995 17:42:18 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id SAA04268; Mon, 13 Mar 1995 18:46:07 -0700 Date: Mon, 13 Mar 1995 18:46:07 -0700 From: Nate Williams Message-Id: <199503140146.SAA04268@trout.sri.MT.net> In-Reply-To: Poul-Henning Kamp "Re: cvs commit: src/release/compat20 libgcc.so.261.0.uu" (Mar 13, 5:36pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Poul-Henning Kamp , rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Subject: Re: cvs commit: src/release/compat20 libgcc.so.261.0.uu Cc: phk@freefall.cdrom.com, CVS-commiters@freefall.cdrom.com, cvs-user@freefall.cdrom.com Sender: cvs-user-owner@freebsd.org Precedence: bulk > > > Added: release/compat20 libgcc.so.261.0.uu > > > This is the shared version of the libgcc which we will need for 2.0 stuff > > > to run on 2.1. > > > > sources and you are not providing the sources to build this binary. > > > > More specifically you are violating section 3 of the GPL by doing this :-(. > > We DO provide the sources. src/gnu/usr.bin/cc/libgcc. But the source code in there is not the same as the source code that built the shlib, so we are still in violation. If we want to be truly safe, we also need to provide the patch that brings the new sources back to the old source state. (And people wonder why I think the GPL is a pain in the butt!) Nate