qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Ed Maste <emaste@freebsd.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Sean Bruno <sbruno@freebsd.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Fix for compile on FreeBSD/i386 (and others?)
Date: Mon, 04 Apr 2016 20:26:46 +0100	[thread overview]
Message-ID: <87r3eltbt5.fsf@linaro.org> (raw)
In-Reply-To: <CAPyFy2A3AHZd0rmws5dog2C3D7Tk33i+nvsa7yr_zUOepm81mg@mail.gmail.com>


Ed Maste <emaste@freebsd.org> writes:

> On 4 April 2016 at 10:35, Alex Bennée <alex.bennee@linaro.org> wrote:
>> Only the first patch has actually changed. Instead of moving the read
>> inside the write seqlock it is now done using the seqlock_read_*
>> primitives.
>>
>> Build tested on a FreeBSB/i386 VM with these applied:
>>
>>   https://github.com/berrange/qemu/tree/freebsd-fixes
>>
>> There are still a ton of unrelated warnings being kicked out of the compiler
>> though. On the VM "make check" fails at ... but as the build was
>
> I'm not sure what the "..." is supposed to be, but FWIW I tried the
> test suite just now and have 3 tests failing on FreeBSD 10.3-STABLE on
> amd64. I've commented them out locally as a temporary workaround.

Oops, I thought I'd filled that in.

>
> The tests (and failures) are:
>
> * tests/test-io-channel-socket
>
> GTESTER tests/test-io-channel-socket
> /tank/emaste/src/qemu/tests/Makefile:650: recipe for target
> 'check-tests/test-io-channel-socket' failed

This is what I saw. Quoth dpb on #qemu:

<danpb> i can reproduce on my bsd box, so lemme have a poke at it
<danpb> stsquad: oh, i see what it is - getaddrinfo is failing for the
    same stupid V4MAPPED issue i alrady sent a patch for

> * tests/test-crypto-pbkdf
>
> Unexpected error in qcrypto_pbkdf2() at crypto/pbkdf-stub.c:41:
> No crypto library supporting PBKDF in this build: Function not implemented
> (and many simliar)
>
> * tests/ipmi-bt-test
>
> qemu-system-i386: Unable to connect character device ipmi0: address
> resolution failed for localhost:40135: Invalid value for ai_flags
> **
> ERROR:tests/ipmi-bt-test.c:320:test_connect: assertion failed: (rv == 1)
> (and three similar errors)

I didn't get this far but I'll re-test once everything is merged. Thanks
for testing on your setup.

--
Alex Bennée

  reply	other threads:[~2016-04-04 19:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04 14:35 [Qemu-devel] [PATCH v2 0/2] Fix for compile on FreeBSD/i386 (and others?) Alex Bennée
2016-04-04 14:35 ` [Qemu-devel] [PATCH v2 1/2] cpus: don't use atomic_read for vm_clock_warp_start Alex Bennée
2016-04-04 14:35 ` [Qemu-devel] [PATCH v2 2/2] include/qemu/atomic: add compile time asserts Alex Bennée
2016-04-04 14:44 ` [Qemu-devel] [PATCH v2 0/2] Fix for compile on FreeBSD/i386 (and others?) Paolo Bonzini
2016-04-04 14:56   ` Peter Maydell
2016-04-04 14:57     ` Paolo Bonzini
2016-04-04 18:10 ` Ed Maste
2016-04-04 19:26   ` Alex Bennée [this message]
2016-04-04 19:38     ` 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=87r3eltbt5.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=emaste@freebsd.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sbruno@freebsd.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).