All of lore.kernel.org
 help / color / mirror / Atom feed
From: "sateesh m" <sateesh0457@gmail.com>
To: "Aleksandar Nikolic" <aleksandar.nikolic010@gmail.com>,
	yocto@lists.yoctoproject.org
Subject: Re: [yocto] GLIBCXX_3.4.30' not found
Date: Tue, 01 Apr 2025 22:24:03 -0700	[thread overview]
Message-ID: <19208.1743571443186192544@lists.yoctoproject.org> (raw)
In-Reply-To: <19208.1743570434438484993@lists.yoctoproject.org>

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

Hi Aleksandar Nikolic,

Yes, we need to use only the older Dunfell version. Initially, when I built the latest image, I did not face any issues—the image was successfully built. Afterward, I created my own layer and updated the BusyBox version to 1.35. Upon building using bitbake -c cleanall busybox and bitbake busybox, the updated BusyBox version was successfully built.
However, while compiling the complete image (for example, core-image-minimal), I observed an issue with GLIBC. To address this, I removed the layer I had added and rebuilt the image. Now, BusyBox has reverted to the backport version (1.31), but while jobs are running, cmake-native is also executing, and an error related to GLIBC 2.3.40 not being found is displayed.
I suspect this issue might be related to the local PC environment. Could you please suggest an alternative solution to fix this issue?

Regards,
Sateesh

[-- Attachment #2: Type: text/html, Size: 1024 bytes --]

  reply	other threads:[~2025-04-02  5:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02  3:45 GLIBCXX_3.4.30' not found sateesh m
2025-04-02  3:58 ` [yocto] " Khem Raj
2025-04-02  4:00   ` sateesh m
2025-04-02  4:10   ` sateesh m
2025-04-02  5:07     ` Aleksandar Nikolic
2025-04-02  5:24       ` sateesh m [this message]
2025-04-02  5:29     ` Khem Raj
2025-04-02  5:50       ` sateesh m
2025-05-13 13:41         ` claudiubucur
2025-05-13 13:50           ` sateesh m
2025-05-13 13:57             ` Klaus
2025-05-13 14:05               ` sateesh m
2025-05-13 14:10                 ` Klaus
2025-05-13 14:17                   ` sateesh m

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=19208.1743571443186192544@lists.yoctoproject.org \
    --to=sateesh0457@gmail.com \
    --cc=aleksandar.nikolic010@gmail.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 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.