From: Dvorkin Dmitry <dvorkin@tibbo.com>
To: yocto@yoctoproject.org
Subject: strange QA issue - how to ignore automatic so dependency
Date: Tue, 1 Dec 2015 01:42:35 +0300 [thread overview]
Message-ID: <565CD0DB.6010900@tibbo.com> (raw)
In-Reply-To: <2603447.ByLEse0mF5@peggleto-mobl.ger.corp.intel.com>
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*"
next prev parent reply other threads:[~2015-11-30 22:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 22:03 [PATCHv2] [layerindex-web] recipe blacklisted information Alex Franco
2015-11-30 22:22 ` Paul Eggleton
2015-11-30 22:42 ` Dvorkin Dmitry [this message]
2015-11-30 23:06 ` strange QA issue - how to ignore automatic so dependency Khem Raj
2015-11-30 23:15 ` Dvorkin Dmitry
2015-11-30 23:22 ` Khem Raj
2015-11-30 23:32 ` Dvorkin Dmitry
2015-12-01 9:40 ` [PATCHv2] [layerindex-web] recipe blacklisted information Martin Jansa
2015-12-01 10:42 ` Barros Pena, Belen
2015-12-01 11:14 ` Martin Jansa
[not found] ` <565DDB89.1030005@intel.com>
2015-12-01 18:26 ` Alex Franco
2015-12-01 19:11 ` Paul Eggleton
2015-12-02 0:47 ` Alex Franco
2015-12-02 11:38 ` Barros Pena, Belen
2015-12-02 11:35 ` Barros Pena, Belen
2015-12-02 20:02 ` Paul Eggleton
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=565CD0DB.6010900@tibbo.com \
--to=dvorkin@tibbo.com \
--cc=yocto@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.