From: Patrick Williams <patrick@stwcx.xyz>
To: Mahesh Kurapati <mahesh.kurapati@keysight.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: add a new yaml interface definition
Date: Mon, 4 Jan 2021 17:15:07 -0600 [thread overview]
Message-ID: <X/OhexuWrZFhy+v6@heinlein> (raw)
In-Reply-To: <SN6PR17MB2558F662101C2B4AE4A09F5096D20@SN6PR17MB2558.namprd17.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
On Mon, Jan 04, 2021 at 11:05:18PM +0000, Mahesh Kurapati wrote:
> Hello Patrick,
>
> Thank you for the quick reply. Step 3 fails.
>
> 3. `meson subprojects download`
>
> ixia@ubuntu:~/git/development/openbmc/build/fender/workspace/sources/phosphor-dbus-interfaces$ meson subprojects download
> Error during basic setup:
> [Errno 2] No such file or directory: '/home/ixia/git/development/openbmc/build/fender/workspace/sources/phosphor-dbus-interfaces/download'
I'm guessing your Meson version is older than 0.49 then? That is where
the 'download' subcommand was added according to:
https://mesonbuild.com/Subprojects.html#download-subprojects
Can you use 'pip' to install a newer one if your distro doesn't have a
newer version available? The meson.build file in
phosphor-dbus-interfaces requires at least 0.54.1 anyhow, so there
aren't even instructions to otherwise download the subprojects using
meson's build flow (which is what happened before the 'download'
subcommand was added).
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-04 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 21:14 add a new yaml interface definition Mahesh Kurapati
2021-01-04 22:22 ` Patrick Williams
2021-01-04 23:05 ` Mahesh Kurapati
2021-01-04 23:15 ` Patrick Williams [this message]
2021-01-05 0:42 ` Mahesh Kurapati
2021-01-05 14:10 ` Patrick Williams
2021-01-06 0:28 ` Mahesh Kurapati
2021-01-05 17:28 ` Ed Tanous
2021-01-06 0:23 ` Mahesh Kurapati
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=X/OhexuWrZFhy+v6@heinlein \
--to=patrick@stwcx.xyz \
--cc=mahesh.kurapati@keysight.com \
--cc=openbmc@lists.ozlabs.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 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.