From: Juan Quintela <quintela@redhat.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Remove HAS_YMF262 conditional code
Date: Sat, 29 Aug 2009 12:06:21 +0200 [thread overview]
Message-ID: <m3skfbue76.fsf@neno.mitica> (raw)
In-Reply-To: <Pine.LNX.4.64.0908291343560.2208@linmac.oyster.ru> (malc's message of "Sat, 29 Aug 2009 13:47:15 +0400 (MSD)")
malc <av1474@comtv.ru> wrote:
> On Sat, 29 Aug 2009, Juan Quintela wrote:
>
>> malc <av1474@comtv.ru> wrote:
>> > On Fri, 28 Aug 2009, Juan Quintela wrote:
>> >
>> >> malc <av1474@comtv.ru> wrote:
>> >> > On Fri, 28 Aug 2009, Juan Quintela wrote:
>> >> >
>> >> >> HAS_YMF262 is not defined anywhere, and use functinos that are not
>> >> >> in the tree.
>> >> >
>> >> > It doesn't hurt anyone, and should stay for those who want OPL3.
>> >> >
>> >> > [..snip..]
>> >>
>> >> We don't have the functions that they protect from.
>>
>>
> [..snip..]
>>
>> I.e. We don't have defined that functions anywhere in the source code.
>> Are I missing something obvious?
>
> It doesn't exist inside the tree due to ymf262.c being under MAME license
> which is [L]GPL incompatible, i.e. the combination is non distributable,
> which does not, however, preclude the user from getting ymf262 elsehwere
> and building QEMU on his/her own.
I am not a Lawyer, but that looks fishy at least.
Later, Juan.
prev parent reply other threads:[~2009-08-29 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 17:49 [Qemu-devel] [PATCH] Remove HAS_YMF262 conditional code Juan Quintela
2009-08-28 18:39 ` [Qemu-devel] " malc
2009-08-28 19:50 ` Juan Quintela
2009-08-28 20:21 ` malc
2009-08-29 0:14 ` Juan Quintela
2009-08-29 9:47 ` malc
2009-08-29 10:06 ` Juan Quintela [this message]
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=m3skfbue76.fsf@neno.mitica \
--to=quintela@redhat.com \
--cc=av1474@comtv.ru \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).