[yocto] strange QA issue - how to ignore automatic so dependency
I'm trying to include binary JDK into my linux image.
just unpacking jdk-...tar.gz into recipe image and packing it into RPM
(I'm using RPM as base of my distribution).
after adding
INSANE_SKIP_${PN} = "file-rdeps ldflags dev-so build-deps"
into recipe I've got no errors or warning while building recipe itself,
RPM is created and it contains some dynamic libraries dependencies
but I've got error building rootfs with this recipe:
(skipped)...
Updating cache... [100%]
Computing transaction...error: Can't install
tps-jdk-7u60+linux+arm+vfp+hflt-r0@cortexa8hf_vfp_neon: no package
provides libXrender.so.1
I can't include libXrender.so.1 into my image, I can't remove libraries
from JDK.
Is there any way to ignore this dependency?
something like RPM_LDD_IGNORE_CHECK="libX*"
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] strange QA issue - how to ignore automatic so dependency
I know. But
it really does not require to have libX* in the system to successfully
run JDK+our software
We're using simple tar xvzf jdk-...tar.gz in all of our embedded
systems, so I know what I'm talking about, sorry.
This feature blocks my efforts to have a well-designed system with
Poky/Yocto... :(
On 01.12.2015 02:06, Khem Raj wrote:
On Nov 30, 2015, at 2:42 PM, Dvorkin Dmitry wrote:
I'm trying to include binary JDK into my linux image.
just unpacking jdk-...tar.gz into recipe image and packing it into RPM (I'm
using RPM as base of my distribution).
after adding
INSANE_SKIP_${PN} = "file-rdeps ldflags dev-so build-deps"
into recipe I've got no errors or warning while building recipe itself,
RPM is created and it contains some dynamic libraries dependencies
but I've got error building rootfs with this recipe:
(skipped)...
Updating cache... [100%]
Computing transaction...error: Can't install
tps-jdk-7u60+linux+arm+vfp+hflt-r0@cortexa8hf_vfp_neon: no package provides
libXrender.so.1
I can't include libXrender.so.1 into my image, I can't remove libraries from
JDK.
Is there any way to ignore this dependency?
No, and if you ignored it then this binary won’t function as expected on the
system. So you should find out providers of missing
rdeps and add them to your image via depends
something like RPM_LDD_IGNORE_CHECK="libX*"
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] strange QA issue - how to ignore automatic so dependency
On 01.12.2015 02:22, Khem Raj wrote:
On Nov 30, 2015, at 3:15 PM, Dvorkin Dmitry wrote:
I know. But
it really does not require to have libX* in the system to successfully run
JDK+our software
We're using simple tar xvzf jdk-...tar.gz in all of our embedded systems, so I
know what I'm talking about, sorry.
you are walking muddy water, I will caution you before I hand a chainsaw to you
as I suggest something as below.
I see. Thank you!
you can use patchelf or something like that on these binaries and remove the
dependencies after unpacking them
run the .so in question via patchelf --remove-needed
and that will make shlibs code in OE not flag them
This feature blocks my efforts to have a well-designed system with
Poky/Yocto... :(
Well designed would mean to adhere to prerequisites as needed by prebuilt
software you are using
On 01.12.2015 02:06, Khem Raj wrote:
On Nov 30, 2015, at 2:42 PM, Dvorkin Dmitry wrote:
I'm trying to include binary JDK into my linux image.
just unpacking jdk-...tar.gz into recipe image and packing it into RPM (I'm
using RPM as base of my distribution).
after adding
INSANE_SKIP_${PN} = "file-rdeps ldflags dev-so build-deps"
into recipe I've got no errors or warning while building recipe itself,
RPM is created and it contains some dynamic libraries dependencies
but I've got error building rootfs with this recipe:
(skipped)...
Updating cache... [100%]
Computing transaction...error: Can't install
tps-jdk-7u60+linux+arm+vfp+hflt-r0@cortexa8hf_vfp_neon: no package provides
libXrender.so.1
I can't include libXrender.so.1 into my image, I can't remove libraries from
JDK.
Is there any way to ignore this dependency?
No, and if you ignored it then this binary won’t function as expected on the
system. So you should find out providers of missing
rdeps and add them to your image via depends
something like RPM_LDD_IGNORE_CHECK="libX*"
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] systemd postinstall start service
Hello! I have a recipe that can be installed into image using postinstall RPM scriptlet only. It's an archive wrapped with a shell script. During the do_rootfs step this RPM is installed such a way: executional archive placed into /opt/. Then during the first system load systemd runs it's postinstall scriptlet scriptlet is simple: /opt/my_server.bin.sh systemctl enable my_server.service systemctl daemon-reload systemctl start my_server.service In my system when systemd runs this postinstall scriptlet it's executed, system is loaded, service is enabled, but not started. service state is "enabled, but inactive (died)" During the postinstall scriptlet execution at systemd first load I see message that my service is stopping instead of starting. After reboot my_server.service is enabled and started. Looks like systemd doesn't want to start service or it stopping it immediately after postinstall. What can I do to start it on first load after postinstall ? my_service.service have such a settings: [Unit] Description=my_server After=syslog.target [Service] Type=simple Restart=on-failure Thanks! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] wrong automatic dependency
Hello!
I wrote my own recipe for crda.
(http://wireless.kernel.org/en/developers/Regulatory/CRDA)
Dependencies is:
DEPENDS = "libgcrypt libnl"
RDEPENDS_${PN} = "udev wireless-regdb"
Crda Makefile is using python to rebuild it's database in
build/installation step.
After installation I have several packages: crda itself, crda-dev,
crda-doc, ... etc.
In my image I'm using only 'crda' package that doesn't need python.
But it seems Yocto detects python and add automatic dependency of python
to my image anyway.
$ grep "crda" ./*.dot | grep pyt
./task-depends.dot:"crda.do_build" -> "python-dbus.do_package_write_ipk"
./task-depends.dot:"crda.do_build" -> "python.do_package_write_rpm"
./task-depends.dot:"crda.do_build" -> "python.do_package_write_deb"
./task-depends.dot:"crda.do_build" -> "python.do_package_write_ipk"
./task-depends.dot:"crda.do_build" ->
"python-pygobject.do_package_write_rpm"
./task-depends.dot:"crda.do_build" ->
"python-pygobject.do_package_write_deb"
./task-depends.dot:"crda.do_build" ->
"python-pygobject.do_package_write_ipk"
./task-depends.dot:"crda.do_build" -> "python-dbus.do_package_write_rpm"
./task-depends.dot:"crda.do_build" -> "python-dbus.do_package_write_deb"
Is there any way to get rid of python dependency in this and only this
recipe? it makes my image significally bigger.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] extra deploy for image
Hello, guys!
I'm building the image and getting it in the .../deploy/
together with uImage, DTSes and modules (as separate files).
It's standard recipes behavior.
I need one more extra tool for the host system to build and place into
/deploy/
I created a recipe, added
///
inherit deploy
do_deploy() {
}
do_deploy-native() {
install ${S}/mytool ${DEPLOYDIR}/mytool
}
addtask deploy before do_build after do_compile
BBCLASSEXTEND = "native nativesdk"
//
into it's recipe, added
EXTRA_IMAGEDEPENDS += "mytool-native"
into myarch.conf
, build the image successfully. Image recipe (I see it) builds
mytool-native also, but does not call deploy for it.
Do anybody knows how to deploy mytool-native together with my Linux
image if mytool.bb is a separate recipe?
Thank you!
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] do_rootfs failed with message about host system(?) locale
ERROR: MyIMG-1.0-r1 do_rootfs: [log_check] MyIMG: found 2 error messages in the logfile: [log_check] Failed to set locale, defaulting to C [log_check] Failed to set locale, defaulting to C ERROR: MyIMG-1.0-r1 do_rootfs: Function failed: do_rootfs ERROR: Logfile of failure stored in: /home/dv/workspace/tpp.17/poky/x.tpp/tmp/work/tpp-tps-linux-gnueabi/MyIMG/1.0-r1/temp/log.do_rootfs.30451 ERROR: Task (/home/dv/workspace/tpp.17/poky/meta-tibbo/recipes-core/images/MyIMG.bb:do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 5400 tasks of which 5394 didn't need to be rerun and 1 failed. the complete logfile is there: https://paste.fedoraproject.org/paste/s~SuKagYWMH2wmJLB6ckFQ I got read of any errors in my image. The only thing is my host PC locale. But if I set export LANG=en_US export LC_ALL=en_US before running bitbake it doesn't help. <>-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] NPM yocto build problem
I see Jean-Marie made this commit https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=a34d0d539e5fdf341541fb628652d22289e80512 I'm experiencing problems building and installing more then one node modules into image: https://pastebin.com/CXPkqD8j It says, /usr/lib/node is a FILE and is is already installed by another package. I'm using RPM package manager in Yocto and I'm pre-installing several NPM modules into my image. Did I make something wrong? signature.asc Description: OpenPGP digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
