于 2013年01月24日 19:25, Xin Ouyang 写道:
PAM modules in ${base_libdir}/security/ should be binary .so files,
not symlinks, so fix this. Since pam_cgroup.so is installed into
${base_libdir}/security, move libcgroup.so.* to ${base_libdir} to
avoid unsafe-references-in-binaries QA issue.
Signed-off-by:
PAM modules in ${base_libdir}/security/ should be binary .so files,
not symlinks, so fix this. Since pam_cgroup.so is installed into
${base_libdir}/security, move libcgroup.so.* to ${base_libdir} to
avoid unsafe-references-in-binaries QA issue.
Acked-by: Ross Burton ross.bur...@intel.com
On Sat, Jan 26, 2013 at 5:13 PM, Pascal Ouyang xin.ouy...@windriver.com wrote:
于 2013年01月24日 19:25, Xin Ouyang 写道:
PAM modules in ${base_libdir}/security/ should be binary .so files,
not symlinks, so fix this. Since pam_cgroup.so is installed into
${base_libdir}/security, move libcgroup.so.*
On Fri, Jan 25, 2013 at 9:07 PM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
On Fri, 2013-01-25 at 20:32 -0200, Otavio Salvador wrote:
There're some processors which provide binary blobs for DRI and GPU
support which need to be build in BSP; to avoid some dirt and ugly
hacks in
The existing check for SKIP_FILEDEPS can be overridden per recipe
using SKIP_FILEDEPS_pn-${PN}. However, there's no mechanism for
letting a single package within a recipe use SKIP_FILEDEPS.
This patch adds SKIP_FILEDEPS_pkg, by analogy to FILES_pkg.
Note that it only works one way; if the recipe
The existing checks for SKIP_FILEDEPS allow it to be turned on and
off per recipe, but provide no way to turn it on and off per package,
except by giving packages particular magic names like *-locale-*. Add
a check against SKIP_FILEDEPS_pkg, parallel to FILES_pkg.
The following changes since
On Tue, Jan 22, 2013 at 04:05:42PM +, g...@git.openembedded.org wrote:
Module: openembedded-core.git
Branch: master
Commit: ffab86f13cafb10d8d6273b6af8cd9a3c84eae20
URL:
http://git.openembedded.org/?p=openembedded-core.gita=commit;h=ffab86f13cafb10d8d6273b6af8cd9a3c84eae20
Author:
This makes the external module compilation a bit more robust for
cases where external module recipes may be passing extra params
to make via EXTRA_OEMAKE, and more that often one needs to pass
M=$(PWD) when building external modules and if we use EXTRA_OEMAKE
that would mean that it would appear
