Re: [Qemu-devel] [PATCH v2 0/2] Fix for compile on FreeBSD/i386 (and others?)

[Peter Maydell <peter.maydell@linaro.org>]

On 4 April 2016 at 20:26, Alex Bennée <alex.bennee@linaro.org> wrote:
> 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

Dan's v2 patch: http://patchwork.ozlabs.org/patch/605911/

>> * 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)

Try http://patchwork.ozlabs.org/patch/605897/ ? That should skip
this test if configure didn't find the pbkdf support.

>> * tests/ipmi-bt-test
>>
>> qemu-system-i386: Unable to connect character device ipmi0: address
>> resolution failed for localhost:40135: Invalid value for ai_flags

This is almost certainly the same V4MAPPED issue as above.

thanks
-- PMM