public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem with trying to build qemu-9.0.2 - it requires dtc for all architectures
Date: Tue, 03 Sep 2024 09:24:53 +0200	[thread overview]
Message-ID: <0DDFA6E0-9323-43EA-8DD9-BB06A9728452@ipfire.org> (raw)
In-Reply-To: <8a284f92-43ca-407f-9750-077b109eaa6d@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

Hello Adolf,

Yes, you can make those changes.

dtc is the device tree compiler and it should be quick to build. We just didn’t do that since we didn’t have any use for it apart from aarch64.

Move it wherever you want. It should not have any further dependencies. We can build it for all architectures.

-Michael

> On 2 Sep 2024, at 19:46, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> I am trying to do an update of the qemu package.
> 
> It is failing for a missing fdt library which it says is required by targets x86_64-softmmu, aarch64-softmmu and riscv64-softmmu.
> 
> The previous version that we currently have, 8.1.2 has a bundled dtc which includes the fdt library. That has been removed, probably with the change to the 9.x branch as it is not in 9.0.2
> 
> We have the dtc package in make but it is after qemu.
> 
> I could move it to before qemu, however I also note that the dtc package is specified only for aarch64 but if we need to have the above softmmu targets specified then qemu is requiring the fdt library for all our architectures.
> 
> Before I move dtc and change it to be for all architectures, I just want to flag this up and confirm that it is the right thing to do.
> 
> Regards,
> 
> Adolf.
> 


  reply	other threads:[~2024-09-03  7:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02 17:46 Adolf Belka
2024-09-03  7:24 ` Michael Tremer [this message]
2024-09-03 13:25   ` Adolf Belka
2024-09-03 19:06     ` Adolf Belka
2024-09-04  6:58       ` Michael Tremer
2024-09-04  7:22         ` Adolf Belka
2024-09-04  9:34           ` Michael Tremer
2024-09-04 13:37             ` Adolf Belka
2024-09-04 19:49               ` Michael Tremer

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=0DDFA6E0-9323-43EA-8DD9-BB06A9728452@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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