All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH] tests/vm: netbsd: install dtc
Date: Mon, 16 Oct 2023 10:07:42 +0100	[thread overview]
Message-ID: <ZSz9XrOLZPQ2Rm+v@redhat.com> (raw)
In-Reply-To: <ZSz9AFwxPBsoRMih@redhat.com>

On Mon, Oct 16, 2023 at 10:06:11AM +0100, Daniel P. Berrangé wrote:
> On Mon, Oct 16, 2023 at 11:00:14AM +0200, Thomas Huth wrote:
> > On 13/10/2023 17.30, Paolo Bonzini wrote:
> > > Install dtc as it is now a mandatory external dependency in order to build QEMU.
> > > 
> > > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> > > ---
> > >   tests/vm/netbsd | 3 +++
> > >   1 file changed, 3 insertions(+)
> > > 
> > > diff --git a/tests/vm/netbsd b/tests/vm/netbsd
> > > index 939dc1b22a1..3ef1ec2d9cc 100755
> > > --- a/tests/vm/netbsd
> > > +++ b/tests/vm/netbsd
> > > @@ -40,6 +40,9 @@ class NetBSDVM(basevm.BaseVM):
> > >           "gsed",
> > >           "gettext-tools",
> > > +        # libs: basic
> > > +        "dtc",
> > > +
> > >           # libs: crypto
> > >           "gnutls",
> > 
> > Does this work for you? When I run "make vm-build-netbsd", I'm still getting
> > a failure:

snip

> > Library fdt found: NO
> > Initialized empty Git repository in
> > /home/qemu/qemu-test.Li0spd/src/subprojects/dtc/.git/
> > fatal: unable to access 'https://gitlab.com/qemu-project/dtc.git/': SSL
> > certificate problem: unable to get local issuer certificate
> > 
> > ../src/meson.build:3076:4: ERROR: Git command failed: ['/usr/pkg/bin/git',
> > 'fetch', '--depth', '1', 'origin',
> > 'b6910bec11614980a21e46fbccc35934b671bd81']
> > 
> > A full log can be found at
> > /home/qemu/qemu-test.Li0spd/build/meson-logs/meson-log.txt
> > 
> > ERROR: meson setup failed
> > 
> > ... so though the NetBSD people finally upgraded their dtc to a usable
> > level, our meson.build seems to be unable to detect it?
> 
> They claim to have version 1.7.0
> 
>   https://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/sysutils/dtc/index.html
> 
> and we claim to want 1.5.0, so should be OK.
> 
> Suggests that our detection, or test compilation is failing. The
> meson-log.txt might have more info, if you can access that ?
> 
> 
> Also separately it appears we're missing the public CA cert bundle,
> so we should not see a cert error from gitlab.

The latter is presumably solvable with this:

  https://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/security/ca-certificates/index.html


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2023-10-16  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 15:30 [PATCH] tests/vm: netbsd: install dtc Paolo Bonzini
2023-10-16  4:44 ` Philippe Mathieu-Daudé
2023-10-16  9:00 ` Thomas Huth
2023-10-16  9:06   ` Daniel P. Berrangé
2023-10-16  9:07     ` Daniel P. Berrangé [this message]
2023-10-16  9:20     ` Thomas Huth
2023-10-16  9:39       ` Paolo Bonzini

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=ZSz9XrOLZPQ2Rm+v@redhat.com \
    --to=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.