From: "embedded (VIVAVIS AG)" <embedded@vivavis.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: AW: [yocto] libnss-resolve not automatically installed
Date: Thu, 4 Aug 2022 12:35:16 +0000 [thread overview]
Message-ID: <0167a3c723b34bafa4edc0b81ca0ea66@vivavis.com> (raw)
In-Reply-To: <CAMKF1sqVSHHmi=NGqmFvbmtjA2fi8PLj5iTodU4+ESyiczPKmA@mail.gmail.com>
Hi Khem,
> Von: Khem Raj <raj.khem@gmail.com>
> Gesendet: Donnerstag, 4. August 2022 13:20
>>
>> To install the missing library libnss-resolve.so.2, I've added
>> IMAGE_INSTALL_append = " libnss-resolve"
>> to my image recipe, but I wonder, if this is the right place or necessary
>> at all.
>>
>> My assumption was that having nss-resolve in PACKAGECONFIG will
>> also install the related library, which is obviously not the case.
>
> Packageconfigs are about what you would like to build it’s still another step what you would like to bundle in your image which is what IMAGE_INSTALL does. At times this is already done because whatever the packagrconfig is enabling is already part of a output package that’s in your IMAGE_INSTALL dependencies and gets pulled in indirectly but that’s not the case here. Therefore you have to do it in both places
>
>>
>> Furthermore, I had to write an append-file for base-files, such that
>> /etc/nsswitch.conf contains the following line
>> hosts: resolve [!UNAVAIL=return] files dns myhostname
>>
Ok, there's nothing to worry about.
Adding libnss-resolve to IMAGE_INSTALL and overwriting nsswitch.conf in
the append-file ist he correct procedure here.
Thanks for clarification.
Carsten
next prev parent reply other threads:[~2022-08-04 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 17:30 libnss-resolve not automatically installed embedded (VIVAVIS AG)
2022-08-04 11:19 ` [yocto] " Khem Raj
2022-08-04 12:35 ` embedded (VIVAVIS AG) [this message]
2022-08-04 13:38 ` Khem Raj
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=0167a3c723b34bafa4edc0b81ca0ea66@vivavis.com \
--to=embedded@vivavis.com \
--cc=raj.khem@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox