From: Claudio Fontana <cfontana@suse.de>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: peter.maydell@linaro.org, david@gibson.dropbear.id.au,
alex.bennee@linaro.org, qemu-devel@nongnu.org, laurent@vivier.eu
Subject: Re: [PATCH] Makefile: libfdt: build only the strict necessary
Date: Wed, 8 Apr 2020 12:09:41 +0200 [thread overview]
Message-ID: <bc7e5ddf-c765-fcd1-bad3-61b957e14a43@suse.de> (raw)
In-Reply-To: <20200408090852.GB1073390@redhat.com>
On 4/8/20 11:08 AM, Daniel P. Berrangé wrote:
> On Wed, Apr 08, 2020 at 09:49:56AM +0200, Claudio Fontana wrote:
>> Hi,
>>
>> On 4/8/20 9:06 AM, no-reply@patchew.org wrote:
>>> Patchew URL: https://patchew.org/QEMU/20200408070231.20265-1-cfontana@suse.de/
>>>
>>>
>>>
>>> Hi,
>>>
>>> This series failed the asan build test. Please find the testing commands and
>>> their output below. If you have Docker installed, you can probably reproduce it
>>> locally.
>>
>> I can't reproduce this here running the commands (TEST SCRIPT) below..
>>
>>>
>>> === TEST SCRIPT BEGIN ===
>>> #!/bin/bash
>>> export ARCH=x86_64
>>> make docker-image-fedora V=1 NETWORK=1
>>> time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1
>>> === TEST SCRIPT END ===
>>>
>>> === OUTPUT BEGIN ===
>>> Makefile:532: dtc/libfdt/Makefile.libfdt: No such file or directory
>>
>> hmm this is the include directive
>>
>> include $(LIBFDT_srcdir)/Makefile.libfdt
>>
>> is this test not getting the dtc submodule for some reason?
>
> Note that this test script did not even get as far as trying to
> build QEMU itself.
>
> Starting from a clean checkout *WITHOUT* having run configure,
> it is trying todo
>
> make docker-image-fedora V=1 NETWORK=1
>
> This should invoke the rules to launch docker, and then run
> configure inside docker. Instead it is trying to build dtc.
>
> So something in your changes has broken the ability to run
> the docker make targets.
Thanks, I can reproduce this now, will correct.
>
>>
>>> cc -nostdlib -o dtc/libfdt/Makefile.libfdt.mo
>>
>> Hmm..
>>
>>> cc: fatal error: no input files
>>> compilation terminated.
>>> make: *** [dtc/libfdt/Makefile.libfdt.mo] Error 4
>>> Makefile:532: dtc/libfdt/Makefile.libfdt: No such file or directory
>>> LD dtc/libfdt/Makefile.libfdt.mo
>>> cc: fatal error: no input files
>>> compilation terminated.
>>> make: *** [dtc/libfdt/Makefile.libfdt.mo] Error 4
>>>
>>> real 0m0.585s
>>> user 0m0.384s
>>>
>>>
>>> The full log is available at
>>> http://patchew.org/logs/20200408070231.20265-1-cfontana@suse.de/testing.asan/?type=message.
>>> ---
>>> Email generated automatically by Patchew [https://patchew.org/].
>>> Please send your feedback to patchew-devel@redhat.com
>>>
>>
>>
>
> Regards,
> Daniel
>
next prev parent reply other threads:[~2020-04-08 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 7:02 [PATCH] Makefile: libfdt: build only the strict necessary Claudio Fontana
2020-04-08 7:06 ` no-reply
2020-04-08 7:49 ` Claudio Fontana
2020-04-08 9:08 ` Daniel P. Berrangé
2020-04-08 10:09 ` Claudio Fontana [this message]
2020-04-08 7:07 ` no-reply
2020-04-08 7:08 ` no-reply
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=bc7e5ddf-c765-fcd1-bad3-61b957e14a43@suse.de \
--to=cfontana@suse.de \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--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).