I'm working on porting this right now.
Be forewarned, though, that the FreeBSD hacks for this tool will
*never* be allowed into the main distro. Why? Licence. Valgrind
includes some code from the Linux kernel and libc. When we hack it for
FreeBSD, we'll end up putting some BSD-licenced code
On Wed, Feb 27, 2002 at 11:00:14AM -0500, Matthew Emmerton wrote:
I'm working on porting this right now.
great news! what is the current status and have you set up a website
for the project or will it be a simple portsentry with some patches? (I
thought it would require some more rewriting
On Wed, Feb 27, 2002 at 11:00:14AM -0500, Matthew Emmerton wrote:
Be forewarned, though, that the FreeBSD hacks for this tool will
*never* be allowed into the main distro. Why? Licence. Valgrind
includes some code from the Linux kernel and libc. When we hack it for
FreeBSD, we'll end up
Matthew Emmerton wrote:
I'm working on porting this right now.
Be forewarned, though, that the FreeBSD hacks for this tool will
*never* be allowed into the main distro. Why? Licence. Valgrind
includes some code from the Linux kernel and libc. When we hack it for
FreeBSD, we'll end up
Michael Lucas wrote:
Actually, this doesn't cause as many as you might think.
GPL'd code can swallow BSDL'd code. BSDL'd code cannot swallow GPL'd
code. You could probably get your code assimilated into the main
valgrind distro.
No, it can't. You can't change the license on the original
