qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Stefan Weil" <sw@weilnetz.de>,
	"Bin Meng" <bin.meng@windriver.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: MSYS2 and libfdt
Date: Thu, 19 Jan 2023 13:30:03 +0100	[thread overview]
Message-ID: <216fdbe1-edc2-46e9-e867-3b173fa932df@redhat.com> (raw)
In-Reply-To: <d117d4e8-b906-cbde-5efe-43dbb183965c@weilnetz.de>

On 19/01/2023 09.55, Stefan Weil wrote:
> Am 19.01.23 um 09:14 schrieb Thomas Huth:
> 
>>
>>  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 ?
>>
>>  Thomas
> 
> 
> Hi Thomas,
> 
> "dtc" is not the right package for cross builds. We'd require 
> mingw-w64-i686-dtc and mingw-w64-x86_64-dtc packages for the QEMU build, but 
> those packages are currently not provided by MSYS2.

Ok, thanks ... so that basically means we cannot get rid of the dtc 
submodule yet.

  Thomas




  reply	other threads:[~2023-01-19 12:30 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 [this message]
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
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=216fdbe1-edc2-46e9-e867-3b173fa932df@redhat.com \
    --to=thuth@redhat.com \
    --cc=bin.meng@windriver.com \
    --cc=marcandre.lureau@redhat.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).