From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Bin Meng <bin.meng@windriver.com>, Stefan Weil <sw@weilnetz.de>,
QEMU Developers <qemu-devel@nongnu.org>,
Biswapriyo Nath <nathbappai@gmail.com>
Subject: Re: MSYS2 and libfdt
Date: Tue, 24 Jan 2023 10:20:08 +0100 [thread overview]
Message-ID: <2bce671f-d91a-72ab-d38f-2e284d9d3ee2@redhat.com> (raw)
In-Reply-To: <Y860hPT+o15BGQYq@redhat.com>
On 23/01/2023 17.23, Daniel P. Berrangé wrote:
> On Fri, Jan 20, 2023 at 05:57:29PM +0400, Marc-André Lureau wrote:
>> Hi Thomas
>>
>> On Fri, Jan 20, 2023 at 12:31 PM Thomas Huth <thuth@redhat.com> wrote:
>>>
>>> On 19/01/2023 09.56, Marc-André Lureau wrote:
>>>> Hi
>>>>
>>>> On Thu, Jan 19, 2023 at 12:31 PM Thomas Huth <thuth@redhat.com> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> in some spare minutes, I started playing with a patch to try to remove the
>>>>> dtc submodule from the QEMU git repository - according to
>>>>> https://repology.org/project/dtc/versions our supported build platforms
>>>>> should now all provide the minimum required version.
>>>>>
>>>>> However, I'm hitting a problem with Windows / MSYS2 in the CI jobs: The
>>>>> libfdt is packaged as part of the dtc package there:
>>>>>
>>>>> https://packages.msys2.org/package/dtc
>>>>>
>>>>> ... meaning that it is added with a usr/include and usr/lib path prefix
>>>>> instead of mingw64/include and mingw64/lib like other packages are using
>>>>> (see e.g.
>>>>> https://packages.msys2.org/package/mingw-w64-x86_64-zlib?repo=mingw64). Thus
>>>>> the compiler does not find the library there. Also there does not seem to be
>>>>> a difference between a i686 (32-bit) and x86_64 (64-bit) variant available
>>>>> here? Does anybody know how libfdt is supposed to be used with MSYS2 ?
>>>>
>>>> The msys environment is a bit special, it's not an environment for a
>>>> particular build target, my understanding is that it holds common
>>>> files/tools.
>>>>
>>>> dtc should be added to https://github.com/msys2/MINGW-packages for it
>>>> to be available as a target dependency.
>>>
>>> Do you have already any experience in requesting a new package there? Could
>>> you maybe do it? ... since I don't have a proper MinGW installation here, it
>>> would be very cumbersome for me right now.
>>>
>>
>> Here you go (although let see what CI has to say):
>> https://github.com/msys2/MINGW-packages/pull/15168
>>
>> The msys2 maintainers are usually very quick and helpful, in my experience.
Great, I just gave it a try, and it seems to be working, indeed:
https://gitlab.com/thuth/qemu/-/jobs/3649509495#L668
Thank you very much Marc-André and Biswapriyo!
> And it merged 1 day after you posted it. So yes, the msys2 maintainers
> are indeed very quick & helpful :-)
>
> So in theory we can try to drop the submodule for dtc now
Ok, I'll give my patch another try to see whether all the other systems have
a usable version of libfdt available, too.
Thomas
next prev parent reply other threads:[~2023-01-24 9:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 8:14 MSYS2 and libfdt Thomas Huth
2023-01-19 8:55 ` Stefan Weil via
2023-01-19 12:30 ` Thomas Huth
2023-01-19 8:56 ` Marc-André Lureau
2023-01-20 8:31 ` Thomas Huth
2023-01-20 13:57 ` Marc-André Lureau
2023-01-23 16:23 ` Daniel P. Berrangé
2023-01-24 9:20 ` Thomas Huth [this message]
2023-01-24 11:27 ` NetBSD and libfdt (was: Re: MSYS2 and libfdt) Thomas Huth
2023-01-25 11:36 ` Nick Hudson
2023-01-25 11:59 ` NetBSD and libfdt Thomas Huth
2023-01-24 14:43 ` MinGW and libfdt (was: Re: MSYS2 and libfdt) Thomas Huth
2023-01-24 15:08 ` Daniel P. Berrangé
2023-01-24 19:10 ` Marc-André Lureau
2023-01-25 10:26 ` Thomas Huth
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=2bce671f-d91a-72ab-d38f-2e284d9d3ee2@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=bin.meng@windriver.com \
--cc=marcandre.lureau@gmail.com \
--cc=nathbappai@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).