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: Tue, 7 Jan 2025 11:24:01 +0100	[thread overview]
Message-ID: <6bd68955-44a5-4a5b-b1f8-990643cb698a@gmail.com> (raw)
In-Reply-To: <TYZPR06MB51783A4E0A436D1469C9120286112@TYZPR06MB5178.apcprd06.prod.outlook.com>

On 07.01.25 11:05, Kumar, Manu wrote:
> reason behind ask this question is.. in earlier tisdk all the modules were there in "/usr/lib" as when we start lightpd service(which was there in (/etc/init.d) it will check modules in "/usr/lib". in the latest tisdk also if I run "systemctl start lighttpd" looks like it is searching "/usr/lib"
>
This change comes from this[1] commit (look at the very bottom of it). 
If it causing problems, you can try overriding it in a bbappend or 
similar. Though maybe it would be more interesting to look into why your 
ti-sdk is looking for these files at the incorrect place. TI layers are 
usually reasonably maintained, I'd expect them to follow changes in the 
oe-core layer...

[1]: 
https://git.yoctoproject.org/poky/commit/meta/recipes-extended/lighttpd?h=kirkstone&id=3755f6c4eb404b6218784ad21c3a56312c425cc2


>
> -----Original Message-----
> From: Kumar, Manu (FT D IN PAMC MI EMB FW)
> Sent: Tuesday, January 7, 2025 2:37 PM
> To: Gyorgy Sarvari <skandigraun@gmail.com>; yocto@lists.yoctoproject.org
> Subject: RE: [yocto] Query: Regarding lighttpd/librarries in /usr/lib not copying
>
> Ok , I will try and let you know !!
>
> But how can I make all the modules to be present inside "/usr/lib" instead of "/usr/lib/lighttpd" ?
>
> Regards
> Manu
>
>


  reply	other threads:[~2025-01-07 10:24 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
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 [this message]
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=6bd68955-44a5-4a5b-b1f8-990643cb698a@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.