Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Feb 2002 13:29:44 -0500 (EST)
From:      Matthew Emmerton <matt@gsicomp.on.ca>
To:        Mike Meyer <mwm-dated-1015265802.29c1b9@mired.org>
Cc:        Terry Lambert <tlambert2@mindspring.com>, Michael Lucas <mwlucas@blackhelicopters.org>, Patrik Sundberg <ps@radiac.mine.nu>, chat@FreeBSD.ORG
Subject:   Re: valgrind
Message-ID:  <Pine.BSF.4.21.0202271328110.46134-100000@xena.gsicomp.on.ca>
In-Reply-To: <15485.8842.438366.492284@guru.mired.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 27 Feb 2002, Mike Meyer wrote:

> [Moved to -chat from -current *and* -stable. Bleah.]
> 
> Terry Lambert <tlambert2@mindspring.com> types:
> > This is why FreeBSD lets people use GPL'ed components as an
> > "after market" item, but does not distribute them: it is in
> > the ditribution that the clause activates.
> 
> I could *swear* that I got gcc with my distribution of FreeBSD. Or
> does this statement only apply to kernel components?

Since gcc is self-contained, it's no a problem.  It's when you've got a
statically-linked image (an application or a kernel image) that contains
both BSD and GPL code that the problems arise.

--
Matt Emmerton


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-chat" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0202271328110.46134-100000>