From: Stefan Weil <sw@weilnetz.de>
To: Sascha Silbe <silbe@linux.vnet.ibm.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developer <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH for-2.7] wxx: Fix broken build (mkdtemp unavailable)
Date: Mon, 29 Aug 2016 19:51:01 +0200 [thread overview]
Message-ID: <92b7dd7e-ecd7-6c1d-95b9-49d62c9aa45f@weilnetz.de> (raw)
In-Reply-To: <87k2ezioj7.fsf@oc4731375738.ibm.com>
On 08/29/16 17:27, Sascha Silbe wrote:
> Dear Peter,
>
> Peter Maydell <peter.maydell@linaro.org> writes:
>
>> On 25 August 2016 at 10:36, Peter Maydell <peter.maydell@linaro.org> wrote:
>>> On 23 August 2016 at 16:01, Sascha Silbe <silbe@linux.vnet.ibm.com> wrote:
>>>> Glad to hear. It would be possibly to support the combination of glib <
>>>> 2.30.0 AND windows, but only by copying a considerable amount of code
>>>> from glib. I'd prefer to avoid that if we can help it.
>>>
>>> If we want to raise the minimum glib version requirement for
>>> Windows we need to enforce this in configure. (We have had
>>> a higher minimum for Windows hosts in the past, so there's
>>> precedent for doing it.)
>>
>> Or we could arrange to skip this test if we're on windows
>> with an old glib I guess.
>
> In general I agree with you. In practice test-logging was completely
> broken on Windows since 2.6.0 (it hard-coded /tmp) and I don't have a
> suitable environment to test a Windows build, so I'd feel uncomfortable
> submitting patches addressing this issue myself.
>
> However that shouldn't stop anyone else (Stefan perhaps? :) ) from
> fixing the tests on Windows. I'll gladly review the effects of the
> corresponding patches on the POSIX side.
>
> Sascha
For 2.7, I think we don't need this patch nor any other solution,
because the problem is less critical than I thought initially: only
builds with old versions of glib are affected.
For 2.8, raising the minimum glib version to 2.30.0 would avoid the
build problem for normal builds targeting Windows. IMHO it is the
simplest and also an acceptable solution, and it also allows removing
some conditional code.
Fixing the tests for builds targeting Windows is a different issue.
Ideally "make test" should work for such builds, no matter whether they
run as cross build on Linux (my usual environment) or native on Windows.
To simplify things, some tests which are difficult to fix for Windows
and which don't test Windows specific code could be omitted. I cannot
promise that I'll work on test support for Windows in the near future –
if anybody else does that job, I'll be happy, too.
Stefan
next prev parent reply other threads:[~2016-08-29 17:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 18:11 [Qemu-devel] [PATCH for-2.7] wxx: Fix broken build (mkdtemp unavailable) Stefan Weil
2016-08-23 19:00 ` Sascha Silbe
2016-08-23 19:23 ` Stefan Weil
2016-08-23 20:01 ` Sascha Silbe
2016-08-25 14:36 ` Peter Maydell
2016-08-25 14:46 ` Peter Maydell
2016-08-29 15:27 ` Sascha Silbe
2016-08-29 17:51 ` Stefan Weil [this message]
2016-08-30 11:01 ` Peter Maydell
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=92b7dd7e-ecd7-6c1d-95b9-49d62c9aa45f@weilnetz.de \
--to=sw@weilnetz.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=silbe@linux.vnet.ibm.com \
/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).