From: Markus Volk <f_l_k@t-online.de>
To: yocto@lists.yoctoproject.org, Ankita.AN@exaleapsemi.com
Subject: Re: [yocto] gnome desktop with kirkstone #kirkstone #gnome
Date: Tue, 11 Feb 2025 06:48:44 +0100 [thread overview]
Message-ID: <858IRS.YAZ7V09LQ36C3@t-online.de> (raw)
In-Reply-To: <24986.1739252218195376608@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
Looking at the log.do_compile it seems that you need to include cstdint:
/home/integration-team/webkit/sources/build/tmp-glibc/work/riscv64-oe-linux/webkitgtk/2.36.8-r0/webkitgtk-2.36.8/Source/ThirdParty/ANGLE/include/GLSLANG/ShaderVars.h:19:26:
error: 'uint64_t' does not name a type
19 | using ShCompileOptions = uint64_t;
| ^~~~~~~~
/home/integration-team/webkit/sources/build/tmp-glibc/work/riscv64-oe-linux/webkitgtk/2.36.8-r0/webkitgtk-2.36.8/Source/ThirdParty/ANGLE/include/GLSLANG/ShaderVars.h:17:1:
note: 'uint64_t' is defined in header '<cstdint>'; did you forget to
'#include <cstdint>'?
16 | #include <vector>
+++ |+#include <cstdint>
17 |
On Mon, Feb 10 2025 at 21:36:58 -08:00:00, Ankita.AN@exaleapsemi.com
wrote:
> Hi,
> Sorry for reopening this conversation, again started working on it
> now.
>
> PFA for error log I get while building gnome-session recipe for
> riscv64(kirkstone).
>
> Could you please help me on it?
>
> Thanks
[-- Attachment #2: Type: text/html, Size: 1447 bytes --]
next prev parent reply other threads:[~2025-02-11 5:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 10:51 gnome desktop with kirkstone #kirkstone #gnome Ankita.AN
2024-11-20 10:58 ` [yocto] " Alexander Kanavin
2024-11-20 11:09 ` Markus Volk
[not found] ` <1809A882E9B0199B.32520@lists.yoctoproject.org>
2024-11-20 11:38 ` Markus Volk
2025-02-11 5:36 ` Ankita.AN
2025-02-11 5:48 ` Markus Volk [this message]
2025-02-11 12:37 ` Ankita.AN
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=858IRS.YAZ7V09LQ36C3@t-online.de \
--to=f_l_k@t-online.de \
--cc=Ankita.AN@exaleapsemi.com \
--cc=yocto@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