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 18:18:47 +0100 [thread overview]
Message-ID: <ffe32e3d-021f-4224-96d5-e3e496dcd950@gmail.com> (raw)
In-Reply-To: <TYZPR06MB5178AB7FF8792D7ABBC1A47286112@TYZPR06MB5178.apcprd06.prod.outlook.com>
Beside that change you made, you also need to make sure that lighttpd
installs the files to the location where you expect them to be. Add
something like this in a bbappend (this option comes from the
meson_options.txt file, where the module install location can be specified):
EXTRA_OEMESON:append = " -Dmoduledir=lib "
On 07.01.25 17:37, Kumar, Manu wrote:
> I have tried to change "sources/oe-core/meta/recipes-extended/lighttpd/lighttpd_1.4.67" only last 2 lines as below,
> python populate_packages:prepend () {
> lighttpd_libdir = d.expand('${libdir}')
> do_split_packages(d, lighttpd_libdir, r'^mod_(.*)\.so$', 'lighttpd-module-%s', 'Lighttpd module for %s', extra_depends='')
> }
>
> But I am getting error as below,
>
> NOTE: Executing Tasks
> ERROR: lighttpd-1.4.67-r0 do_package: QA Issue: lighttpd: Files/directories were installed but not shipped in any package:
> /usr/lib/lighttpd/mod_alias.so
> /usr/lib/lighttpd/mod_wstunnel.so
> /usr/lib/lighttpd/mod_redirect.so
> /usr/lib/lighttpd/mod_webdav.so
> /usr/lib/lighttpd/mod_evhost.so
> /usr/lib/lighttpd/mod_authn_file.so
> /usr/lib/lighttpd/mod_secdownload.so
> /usr/lib/lighttpd/mod_staticfile.so
> /usr/lib/lighttpd/mod_usertrack.so
> /usr/lib/lighttpd/mod_setenv.so
> /usr/lib/lighttpd/mod_proxy.so
> /usr/lib/lighttpd/mod_indexfile.so
> /usr/lib/lighttpd/mod_auth.so
> /usr/lib/lighttpd/mod_ajp13.so
> /usr/lib/lighttpd/mod_deflate.so
> /usr/lib/lighttpd/mod_simple_vhost.so
> /usr/lib/lighttpd/mod_scgi.so
> /usr/lib/lighttpd/mod_openssl.so
> /usr/lib/lighttpd/mod_vhostdb.so
> /usr/lib/lighttpd/mod_accesslog.so
> /usr/lib/lighttpd/mod_fastcgi.so
> /usr/lib/lighttpd/mod_ssi.so
> /usr/lib/lighttpd/mod_dirlisting.so
> /usr/lib/lighttpd/mod_status.so
> /usr/lib/lighttpd/mod_access.so
> /usr/lib/lighttpd/mod_expire.so
> /usr/lib/lighttpd/mod_userdir.so
> /usr/lib/lighttpd/mod_sockproxy.so
> /usr/lib/lighttpd/mod_evasive.so
> /usr/lib/lighttpd/mod_cgi.so
> /usr/lib/lighttpd/mod_extforward.so
> /usr/lib/lighttpd/mod_rrdtool.so
> /usr/lib/lighttpd/mod_uploadprogress.so
> /usr/lib/lighttpd/mod_rewrite.so
> Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
> lighttpd: 34 installed and not shipped files. [installed-vs-shipped]
> ERROR: lighttpd-1.4.67-r0 do_package: Fatal QA errors were found, failing task.
>
>
> Can you please help me how to overriding it in a bbappend or similar as you mentioned in older thread.. it helps !!!
>
> -----Original Message-----
> From: Gyorgy Sarvari <skandigraun@gmail.com>
> Sent: Tuesday, January 7, 2025 3:54 PM
> To: Kumar, Manu (FT D IN PAMC MI EMB FW) <kumar.manu@siemens.com>; yocto@lists.yoctoproject.org
> Subject: Re: [yocto] Query: Regarding lighttpd/librarries in /usr/lib not copying
>
> 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
>>
>>
next prev parent reply other threads:[~2025-01-07 17:18 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
2025-01-07 16:37 ` Kumar, Manu
2025-01-07 17:18 ` Gyorgy Sarvari [this message]
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=ffe32e3d-021f-4224-96d5-e3e496dcd950@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox