All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gyorgy Sarvari <skandigraun@gmail.com>
To: "Kumar, Manu" <kumar.manu@siemens.com>,
	"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Query: Regarding lighttpd/librarries in /usr/lib not copying
Date: Mon, 6 Jan 2025 16:05:04 +0100	[thread overview]
Message-ID: <767702b3-302c-4695-96f2-7299547f2da8@gmail.com> (raw)
In-Reply-To: <SI2PR06MB517020EDA3F2E22BC5EA20B186102@SI2PR06MB5170.apcprd06.prod.outlook.com>

On 06.01.25 13:52, Kumar, Manu wrote:
> Yes Sarvari, you are rite.. I have declared as per your input .. but i 
> am facing same as I mentioned in previous thread ..

Hmmm... I just tried to build your recipe with Kirkstone, and it did 
work as expected.

Do you have the other folders populated in the rootfs folder, like do 
you see a bunch of so files in custom_image/1.0-r0/rootfs/usr/lib/ 
folder? Or is it also empty?

Also, do you use any custom bbappend with lighttpd?

As a last thought for this mail: lighttpd recipe provides a number of 
lighttpd-modules-* packages (most of which are not installed 
automatically). The easiest to see this list is to take a look at the 
build packages in deploy/$PACKAGE_TYPE/$ARCH/lighttpd-module-* files.

You could check the output of 'grep "Installing lighttpd-module" 
log.do_rootfs' command in both Dunfell and Kirkstone. If Dunfell 
installed some extra that you are missing in Kirkstone, you could add 
them to the IMAGE_INSTALL variable (or do the RDEPENDS variable of the 
recipe that needs it specifically).



  reply	other threads:[~2025-01-06 15:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06  3:26 Query: Regarding lighttpd/librarries in /usr/lib not copying kumar.manu
2025-01-06 10:33 ` [yocto] " Gyorgy Sarvari
2025-01-06 12:52   ` Kumar, Manu
2025-01-06 15:05     ` Gyorgy Sarvari [this message]
2025-01-07  5:41       ` Kumar, Manu
2025-01-07  6:32         ` Gyorgy Sarvari
2025-01-07  9:07           ` Kumar, Manu
2025-01-07 10:05             ` Kumar, Manu
2025-01-07 10:24               ` Gyorgy Sarvari
2025-01-07 16:37                 ` Kumar, Manu
2025-01-07 17:18                   ` Gyorgy Sarvari
2025-01-07 17:25                     ` Alexander Kanavin
2025-01-07 17:38                       ` Kumar, Manu
2025-01-07 17:44                         ` Gyorgy Sarvari
2025-01-07 17:48                           ` Kumar, Manu
2025-01-07 17:50                           ` Alexander Kanavin
2025-01-07 17:54                             ` Kumar, Manu
2025-01-08  6:32                             ` Kumar, Manu

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=767702b3-302c-4695-96f2-7299547f2da8@gmail.com \
    --to=skandigraun@gmail.com \
    --cc=kumar.manu@siemens.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.