From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Win2k host problem with {get,free}{addr,name}info()
Date: Mon, 20 Sep 2010 15:21:41 -0500 [thread overview]
Message-ID: <4C97C255.2020106@codemonkey.ws> (raw)
In-Reply-To: <AANLkTi=wL19g=o12yEXMjhFs-_iFdGSJgRtL2rkA_zEp@mail.gmail.com>
On 09/20/2010 03:03 PM, Blue Swirl wrote:
> On Mon, Sep 20, 2010 at 6:41 PM, Blue Swirl<blauwirbel@gmail.com> wrote:
>
>> On Mon, Sep 20, 2010 at 6:26 PM, Anthony Liguori<anthony@codemonkey.ws> wrote:
>>
>>> On 09/19/2010 11:16 AM, Blue Swirl wrote:
>>>
>>>> On Wed, Sep 15, 2010 at 7:25 PM, Anthony Liguori<anthony@codemonkey.ws>
>>>> wrote:
>>>>
>>>>
>>>>> On 09/15/2010 02:11 PM, Blue Swirl wrote:
>>>>>
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I tried to test QEMU on Win2k, but there are run time errors because
>>>>>> of missing {get,free}{addr,name}info() functions. After adding dummy
>>>>>> defines in place, there are no more errors.
>>>>>>
>>>>>> I found a similar case, where a compatibility patch was proposed:
>>>>>> http://trac.filezilla-project.org/ticket/1532
>>>>>>
>>>>>> The patch is a bit heavy, consisting of run time detection of Win2k
>>>>>> and full replacements for the functions. Are there any alternative
>>>>>> solutions? I'm by no means a Windows expert.
>>>>>>
>>>>>>
>>>>>>
>>>>> Win2k is EOL so I don't think it's useful for us to support it as a host.
>>>>> So any type of patch is just going to add additional complexity for very
>>>>> little real gain.
>>>>>
>>>>>
>>>> I made a compatibility patch based on the FileZilla patch. The impact
>>>> is very low, outside of the new files added, only Makefiles are
>>>> changed.
>>>>
>>>>
>>> Does gnulib have a similar replacement function?
>>>
>> Very similar, in fact that must be the source.
>>
>>
>>> The nice thing about gnulib is that in the long term, we could potentially
>>> use gnulib for compatibility and make sure to get updated code.
>>>
>> One problem is that the current versions use GPLv3.
>>
> Sorry, I made too hasty conclusions based on a few files.
> getaddrinfo.c and inet_ntop.c are both GPLv2+.
>
Perfect, that works out very well then.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-09-20 20:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 19:11 [Qemu-devel] Win2k host problem with {get,free}{addr,name}info() Blue Swirl
2010-09-15 19:25 ` Anthony Liguori
2010-09-19 16:16 ` Blue Swirl
2010-09-20 18:26 ` Anthony Liguori
2010-09-20 18:41 ` Blue Swirl
2010-09-20 20:03 ` Blue Swirl
2010-09-20 20:21 ` Anthony Liguori [this message]
2010-09-21 18:32 ` Blue Swirl
2010-09-21 19:06 ` Anthony Liguori
2010-09-22 17:36 ` Blue Swirl
2010-09-22 13:40 ` [Qemu-devel] Re: Win2k host problem with {get, free}{addr, name}info() Paolo Bonzini
2010-09-22 13:40 ` Paolo Bonzini
2010-09-22 13:42 ` Anthony Liguori
2010-09-22 14:04 ` Paolo Bonzini
2010-09-22 15:27 ` malc
2010-09-22 16:36 ` Paolo Bonzini
2010-09-22 16:38 ` malc
2010-09-22 16:53 ` Anthony Liguori
2010-09-22 17:16 ` Blue Swirl
2010-09-23 11:22 ` Paolo Bonzini
2010-09-21 8:09 ` Paolo Bonzini
2010-09-21 9:49 ` Bastien ROUCARIES
2010-09-20 4:16 ` [Qemu-devel] Win2k host problem with {get,free}{addr,name}info() Joe Ross
2010-09-20 17:56 ` Blue Swirl
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=4C97C255.2020106@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--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).