Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Changqing Li <changqing.li@windriver.com>
To: "Jörg Sommer" <joerg.sommer@navimatix.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] Revert "python3-ctypes: depend on ldconfig only if distro-feature set"
Date: Tue, 25 Feb 2025 10:02:52 +0800	[thread overview]
Message-ID: <23e2fa72-4225-4dfd-8d5b-cd8afe03b411@windriver.com> (raw)
In-Reply-To: <nvmjowjub7hxr4wz4njvcwdi5mo2g4ppiixrsdgr5zrqs3dwch@mrwc5mgkqid4>

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


On 2/25/25 07:36, Jörg Sommer wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> Changqing Li via lists.openembedded.org schrieb am Do 20. Feb, 11:57 (+0800):
>> The reverted commit causes regression when ldconfig not in
>> DISTRO_FEATURES, before, without ldconfig in DISTRO_FEATURES,
>> ctypes.util.find_library(name) can find the lib if it is installed,
> Hello Changqing Li,
>
> Did I understand correctly that gtk+3 was found before, indent of ldconfig
> was in der DISTRO_FEATURES? But after the change, if fails.
>
> Where is libgdk installed? In /usr/lib or somewhere else?

Hi,

libgtk is under /usr/lib. See:

root@qemux86-64:~# ldconfig -p | grep gtk-3

libgtk-3.so.0 (libc6,x86-64) => /usr/lib/libgtk-3.so.0

root@qemux86-64:~# python3

Python 3.13.2 (main, Feb 4 2025, 14:51:09) [GCC 14.2.0] on linux Type 
"help", "copyright", "credits" or "license" for more information.

 >>> from ctypes.util import find_library

 >>> find_library('gtk-3')

  'libgtk-3.so.0'


For the case that ldconfig is NOT in DISTRO_FEATURES, gtk+3 can be 
found. After commit "python3-ctypes: depend on ldconfig only if 
distro-feature set" is merged,

ldconfig is not installed, so ctypes.util.find_library cannot found gtk+3.

//Changqing

>
>
> Bye, Jörg
>
> --
> Navimatix GmbH           T: 03641 - 327 99 0
> Tatzendpromenade 2       F: 03641 - 526 306
> 07745 Jenawww.navimatix.de
>
> Geschäftsführer: Steffen Späthe, Jan Rommeley
> Registergericht: Amtsgericht Jena, HRB 501480

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

  reply	other threads:[~2025-02-25  2:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20  3:57 [PATCH] Revert "python3-ctypes: depend on ldconfig only if distro-feature set" changqing.li
2025-02-21 14:34 ` [OE-core] " Mathieu Dubois-Briand
2025-02-24  0:27   ` Changqing Li
     [not found]   ` <1826FD59DBA1FC0B.20721@lists.openembedded.org>
2025-02-24  8:20     ` Changqing Li
2025-02-24 11:02       ` Mathieu Dubois-Briand
     [not found]       ` <18271FF8E1B74516.20721@lists.openembedded.org>
2025-02-25  9:12         ` Mathieu Dubois-Briand
2025-02-24 23:36 ` Jörg Sommer
2025-02-25  2:02   ` Changqing Li [this message]
2025-02-25  5:33     ` Jörg Sommer
2025-02-27 22:32     ` Jörg Sommer
2025-02-28  2:56       ` Changqing Li
2025-02-28  5:42         ` Jörg Sommer
2025-02-28 10:20           ` Richard Purdie
2025-02-28 10:35             ` Jörg Sommer
2025-02-28 10:50               ` Richard Purdie
2025-03-03  3:30                 ` Changqing Li

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=23e2fa72-4225-4dfd-8d5b-cd8afe03b411@windriver.com \
    --to=changqing.li@windriver.com \
    --cc=joerg.sommer@navimatix.de \
    --cc=openembedded-core@lists.openembedded.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