From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
alexandre.belloni@bootlin.com
Cc: "Yu, Mingli" <mingli.yu@eng.windriver.com>,
openembedded-core@lists.openembedded.org, Ross.Burton@arm.com
Subject: Re: [OE-core] [PATCH v3] qemu: Add qemu-common package
Date: Wed, 19 Jul 2023 17:39:59 +0800 [thread overview]
Message-ID: <078073d8-60c9-1cdd-e7be-cd3cf63e7dda@windriver.com> (raw)
In-Reply-To: <5ef0c81123f4abb3be2234cd8598cfa0a4cffea5.camel@linuxfoundation.org>
Hi Richard and Ross,
On 7/19/23 17:24, Richard Purdie wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Wed, 2023-07-19 at 11:20 +0200, Alexandre Belloni via
> lists.openembedded.org wrote:
>> On 19/07/2023 17:10:37+0800, Yu, Mingli wrote:
>>> Hi Alex,
>>>
>>> On 7/17/23 20:46, Alexandre Belloni wrote:
>>>> CAUTION: This email comes from a non Wind River email account!
>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>>>>
>>>> On 17/07/2023 15:10:35+0800, Yu, Mingli wrote:
>>>>> Hi Alex,
>>>>>
>>>>> On 7/16/23 19:47, Alexandre Belloni wrote:
>>>>>> CAUTION: This email comes from a non Wind River email account!
>>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> This causes the following meta-mingw error on the AB:
>>>>>>
>>>>>> https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/7501/steps/12/logs/stdio
>>>>>
>>>>> I didn't find the core-image-mingw-sdktest recipe which I noticed in the
>>>>> above log, so I cannot reproduce the issue as you mentioned.
>>>>
>>>> As stated above, this is part of meta-mingw:
>>>>
>>>> https://git.yoctoproject.org/meta-mingw/tree/recipes-core/images?h=master-next
>>>
>>> Thanks for your pointer!
>>>
>>> BTW, the below error which in https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/7501/steps/12/logs/stdio
>>> seems irrelevant to the added nativesdk dependency though I have removed the
>>> nativesdk dependency in https://patchwork.yoctoproject.org/project/oe-core/patch/20230717071114.2734859-1-mingli.yu@eng.windriver.com/.
>>>
>>>> /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/work/i686-nativesdk-mingw32-w64-mingw32/nativesdk-ncurses/6.4-r0/recipe-sysroot-native/usr/bin/i686-w64-mingw32/../../libexec/i686-w64-mingw32/gcc/i686-w64-mingw32/13.1.1/ld:
>>> ../obj_s/lib_kernel.o:lib_kernel.c:(.text+0x5c): undefined reference to
>>> `_nc_mingw_tcflush'
>>>> /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/work/i686-nativesdk-mingw32-w64-mingw32/nativesdk-ncurses/6.4-r0/recipe-sysroot-native/usr/bin/i686-w64-mingw32/../../libexec/i686-w64-mingw32/gcc/i686-w64-mingw32/13.1.1/ld:
>>> ../obj_s/lib_ttyflags.o:lib_ttyflags.c:(.text+0x2c): undefined reference to
>>> `_nc_mingw_tcgetattr'
>>>> /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/work/i686-nativesdk-mingw32-w64-mingw32/nativesdk-ncurses/6.4-r0/recipe-sysroot-native/usr/bin/i686-w64-mingw32/../../libexec/i686-w64-mingw32/gcc/i686-w64-mingw32/13.1.1/ld:
>>> ../obj_s/lib_ttyflags.o:lib_ttyflags.c:(.text+0xbb): undefined reference to
>>> `_nc_mingw_tcsetattr'
>>>
>>
>> It is relevant, this is because of the dependency that this gets built
>> and fails. I've seen v4 but didn't have the time to test it yet.
>
> I've still not seen an answer to Ross' question or mine about why we
> can't just add a couple of dependencies and resolve things that way.
Sorry for delayed respond!
Have added qemu-common to make qemu as meta package to keep backward
compatibility. For user who install qemu rpm such as
qemu-7.2.0-r0.corei7_64.rpm, it still pull in all of things as before.
For user who cares the rpm size, can just choose to install the needed
qemu arch rpms such as qemu-system-aarch64-7.2.0-r0.corei7_64.rpm.
Thanks,
>
> Cheers,
>
> Richard
next prev parent reply other threads:[~2023-07-19 9:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 8:17 [PATCH] qemu: Install the default qemu emulation rpm mingli.yu
2023-06-26 10:28 ` [OE-core] " Richard Purdie
2023-06-27 10:56 ` [PATCH] qemu: Add qemu-common package mingli.yu
2023-07-06 11:36 ` [OE-core] " Ross Burton
2023-07-10 6:55 ` [PATCH v2] " mingli.yu
2023-07-10 10:32 ` [PATCH v3] " mingli.yu
2023-07-10 20:47 ` [OE-core] " Alexandre Belloni
2023-07-12 2:39 ` Yu, Mingli
2023-07-16 11:47 ` Alexandre Belloni
2023-07-17 7:10 ` Yu, Mingli
2023-07-17 12:46 ` Alexandre Belloni
2023-07-19 9:10 ` Yu, Mingli
2023-07-19 9:20 ` Alexandre Belloni
2023-07-19 9:24 ` Richard Purdie
2023-07-19 9:39 ` Yu, Mingli [this message]
2023-07-19 10:08 ` Richard Purdie
2023-07-20 2:39 ` Yu, Mingli
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=078073d8-60c9-1cdd-e7be-cd3cf63e7dda@windriver.com \
--to=mingli.yu@windriver.com \
--cc=Ross.Burton@arm.com \
--cc=alexandre.belloni@bootlin.com \
--cc=mingli.yu@eng.windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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