This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Build requirements for the graphite loop optimization passes

From: Mark Mitchell <mark at codesourcery dot com>
To: Daniel Berlin <dberlin at dberlin dot org>
Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>, Sebastian Pop <sebpop at gmail dot com>, gcc at gcc dot gnu dot org, Richard Guenther <richard dot guenther at gmail dot com>, Jakub Jelinek <jakub at redhat dot com>, David Edelsohn <edelsohn at gmail dot com>, "Harle, Christophe" <christophe dot harle at amd dot com>, Tobias Grosser <grosser at fim dot uni-passau dot de>, Konrad Trifunovic <konrad dot trifunovic at gmail dot com>, Albert Cohen <Albert dot Cohen at inria dot fr>, Roberto Bagnara <bagnara at cs dot unipr dot it>, Doran Wilde <wilde at ee dot byu dot edu>
Date: Mon, 04 Aug 2008 09:34:19 -0700
Subject: Re: Build requirements for the graphite loop optimization passes
References: <cb9d34b20808031231l690256a2r918908804397072b@mail.gmail.com> <Pine.LNX.4.64.0808031947270.15922@digraph.polyomino.org.uk> <20080804074738.GA17657@ins.uni-bonn.de> <Pine.LNX.4.64.0808041018040.24095@digraph.polyomino.org.uk> <4aca3dc20808040907w4065d9d1mbd6bbc7a68e0155@mail.gmail.com>

Daniel Berlin wrote:

If we are doing that, we really shouldn't be.
One of the very explicit freedoms in the GPL is to be able to build
versions for internal use that are not publicly distributed.

I completely agree that that is an important freedom guaranteed by the GPL. The GPL requirement that source be available, etc., only applies when distributing the GPL'd application.

However, there's something to be said for making it reasonably hard for users to build versions of GCC that they can't distribute. Otherwise, they could be in legal jeopardy, either from the FSF or from the provider of the GPL-incompatible software. I'd be rather unhappy if I downloaded the GCC source code, configured it for a system explicitly supported by GCC, handed the binary and source to you, and found out I was violating the GPL! For that matter, I'd be unhappy if GCC "tricked" me into violating some other license as well. So, if we have a configuration that we know is undistributable, then making me hack the source code to disable the error, or making me use a configure-time override option seems like a good call.

Thanks,

--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713

References:
- Re: Build requirements for the graphite loop optimization passes
  - From: Joseph S. Myers
- Re: Build requirements for the graphite loop optimization passes
  - From: Ralf Wildenhues
- Re: Build requirements for the graphite loop optimization passes
  - From: Joseph S. Myers
- Re: Build requirements for the graphite loop optimization passes
  - From: Daniel Berlin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]