From: "D.J. Barrow" <barrow_dj@yahoo.com>
To: Dave Korn <dave.korn@artimi.com>, gdb@sourceware.org
Subject: RE: how to get uptodate vxworks gdb source code
Date: Thu, 02 Mar 2006 15:31:00 -0000 [thread overview]
Message-ID: <20060302153123.51251.qmail@web51109.mail.yahoo.com> (raw)
In-Reply-To: <036201c63dff$45f33780$a501a8c0@CAM.ARTIMI.COM>
Hi Dave,
From my understanding of GPL they have to make the sources freely
available to everyone, the licence is supposed to be infectious
Gnu wouldn't neuter this licence.
The latest gdb available on their website which they is
gdb-5.3 for tornado-2.2.
--- Dave Korn <dave.korn@artimi.com> wrote:
> On 02 March 2006 12:00, D.J. Barrow wrote:
>
> > This is the reply I got from Windriver support
> > you need License / Code Number to get their sources.
>
>
> Yes, of course. The GPL obliges anyone who distributes binaries of a GPL'd
> program to supply (or offer to supply) the sources of those binaries, but
> they're only obliged to do so to those same people who they have shipped
> binaries to. So if you don't have a fully licensed VxWorks development setup,
> they won't have sent you their toolchain, and won't be under any obligation to
> give you binaries; i.e. they are only obliged to give sources to the customers
> who have bought their binaries. If you haven't been given a binary version of
> the toolchain by them, they aren't obliged to you in any way.
>
> And like Steven said, if you want to discuss it in greater depth, approach
> the FSF directly, or discuss it on the lists at
> http://gpl-violations.org/
>
> cheers,
> DaveK
> --
> Can't think of a witty .sigline today....
>
>
D.J. Barrow Linux kernel developer
eMail: dj_barrow@ariasoft.ie
Home: +353-22-47196.
Mobile (IRL) +353-(0)86 1715438
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2006-03-02 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 12:00 D.J. Barrow
2006-03-02 13:43 ` Dave Korn
2006-03-02 15:31 ` D.J. Barrow [this message]
2006-03-02 15:34 ` Daniel Jacobowitz
2006-03-02 15:41 ` Dave Korn
2006-03-02 17:43 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060302153123.51251.qmail@web51109.mail.yahoo.com \
--to=barrow_dj@yahoo.com \
--cc=dave.korn@artimi.com \
--cc=dj_barrow@ariasoft.ie \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox