Anthony, To restate the obvious, If i choose to, i can use another compiler (say VC++ on Windows - http://httpd.apache.org/docs/1.3/win_compiling.html) and not care about GCC's GPL+Exception.
Let's see if you guys have enough pull with FSF to make at least GPL v3 (http://gplv3.fsf.org/process-definition) compatible with ASL 2.0 as-is. If it's not, a temporary bridge is of no use. no? More seriously, if there is a legal concern about Apache's use of GCC stuff, it should come through the right channels. -- dims On 12/4/05, Anthony Green <[EMAIL PROTECTED]> wrote: > On Sun, 2005-12-04 at 11:14 -0500, Geir Magnusson Jr. wrote: > > That said, I think that to be fair, we need to distinguish between > > "using" in the sense of what GCC is doing - a tool outside the scope > > of effort of the project enabling some behavior in a standard and non- > > intrusive way (just like we don't care about the license of the OS we > > run on), and "using" in the sense of developers of a project making a > > conscious decision to design and implement software with a dependency. > > This is wrong thinking. You aren't simply "using" the libgcc routines, > as you would OS resources. You are linking your application to the > libgcc library and redistributing the resulting combined binary. This > is precisely what the license talks about and enables. > > Whether or not you make a distinction between this kind of GPL+exception > usage and libstdc++ or GNU Classpath usage hardly matters, since the > licenses themselves don't make a distinction. > > AG > > > -- Davanum Srinivas : http://wso2.com/blogs/
