Closed Bug 423906 Opened 16 years ago Closed 16 years ago

COPYING file for Dehydra

Categories

(Developer Infrastructure :: Source Code Analysis, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: taras.mozilla, Unassigned)

References

Details

My plan is to just copy the GPL v2 one from the GCC tree. Is that reasonable?
We're building against GCC4.3 which is GPLv3.
Thanks for clarifying the GCC license mess. I'll copy COPYING3 file from GCC since it's v3 now.
Taras

Just checking -- 

this is code that exists quite separately from the code we build and ship as Mozilla technology?

Is it actually required that your work be licensed under the GPL? Or is it that this seems to make sense given GCC?

Mitchell
This code is separate from Mozilla.

It has to be GPLv3, because it is including headers and linking functions from GCC.
OK, thanks, that sounds pretty clear.

mitchell
Benjamin is suggesting that we should use GPLv2&later since we'll also be compiling against gcc 4.2
Pushed README, COPYING files. I would rather not pollute the source files, unless someone can provide me with a 1-2line lawyerspeak header.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: Core → Firefox Build System
Product: Firefox Build System → Developer Infrastructure
You need to log in before you can comment on or make changes to this bug.