From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: bruce.ashfield@gmail.com
Cc: meta-virtualization <meta-virtualization@lists.yoctoproject.org>
Subject: Re: [meta-virtualization] ceph upgrade
Date: Mon, 11 Mar 2024 17:11:09 -0400 [thread overview]
Message-ID: <CADkTA4M9w2W+7Cio6x2DBsHf+i6TPtrodVB4p5it_oGbh0bO-w@mail.gmail.com> (raw)
In-Reply-To: <17BA0B9342C35A1E.21429@lists.yoctoproject.org>
Hi all,
I'm still looking for help with this.
It's all fine and well that folks have packages that they are
interested in more than others, but it needs to be more than
maintainers that step up and fix the niche packages.
I'm still holding the meta-virt master-next -> master push until Ceph
is upgraded and working.
I know absolutely nothing about CMake, so I'm flailing around in the
build of Ceph and have gotten no further since I last asked for help.
Bruce
On Tue, Mar 5, 2024 at 9:22 PM Bruce Ashfield via
lists.yoctoproject.org
<bruce.ashfield=gmail.com@lists.yoctoproject.org> wrote:
>
> Hi all,
>
> If anyone has experience with Cmake, I could use a hand completing the
> ceph upgrade that is marked as WIP in master-next.
>
> It took me a few hours today, but I managed to get past python3
> detection issues, but now I'm running into a compiler test failure
> during the build.
>
> To me, it looks like our sysroot isn't being passed, which could be
> related to the toolchain.cmake not being used (since the compiler test
> is being launched by a sub component).
>
> I'm inclined to be stubborn about this, and keep working on getting
> the package bumped, as it has missed a few upgrades and is in need of
> some love.
>
> Bruce
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#8604): https://lists.yoctoproject.org/g/meta-virtualization/message/8604
> Mute This Topic: https://lists.yoctoproject.org/mt/104759213/1050810
> Group Owner: meta-virtualization+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
next parent reply other threads:[~2024-03-11 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17BA0B9342C35A1E.21429@lists.yoctoproject.org>
2024-03-11 21:11 ` Bruce Ashfield [this message]
2024-03-12 0:40 ` [meta-virtualization] ceph upgrade Tim Orling
2024-03-12 1:55 ` Bruce Ashfield
2024-03-12 17:58 ` Christopher Clark
2024-03-12 18:43 ` Bruce Ashfield
2024-03-13 10:51 ` ChenQi
[not found] ` <17BC4D73EFF2649F.27213@lists.yoctoproject.org>
2024-03-13 11:09 ` ChenQi
2024-03-13 12:58 ` Bruce Ashfield
2024-03-14 8:11 ` Chen, Qi
2024-03-06 2:22 Bruce Ashfield
2024-03-06 6:38 ` [meta-virtualization] " Khem Raj
2024-03-06 14:24 ` Bruce Ashfield
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=CADkTA4M9w2W+7Cio6x2DBsHf+i6TPtrodVB4p5it_oGbh0bO-w@mail.gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).