(borrow from OpenEmbedded with below tweaks)
Enhance login_defs_pam.sed according to shadow source, to ensuer we don't
leave any unknown definitions in /etc/login.defs when pam is enabled
no need for --disable-account-tools-setuid which is detected upon pam
automatically, and no specific CFLAGS append
move shadow site options to generic site files
adjust indention
RDEPENDS on a list of pam-plugins since they're separately packaged
test with both pam enabled and pam disabled. when pam is enabled, tried
some same tweak with desired effect.
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
currently staging.bbclass mangle *.la to ensure sysroot prefix attached to
dependency_libs if other *.la is referenced, however it only happens on
${libdir}. libpam is special with its libraries under ${base_libdir}. So
this extends mangle to ${base_libdir} too
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
So far pam is not really functional as there no pam config files exists, here
we borrow from openembedded to setup core /etc/pam.d to make it functional:
* change 'pam' to 'libpam' following Debian naming convention, and change
(R)DEPENDS in other recipes
* borrow openembedded libpam-base-files with changes:
- rename to libpam-runtime to follow Debian naming
- only keep common-* core files which can be traced back to Debian
libpam-runtime-1.0.1 for license track. Other service specific files
(such as atd, cron, ...) are removed because either they may contaminate
the license or it's right thing to have their own packages providing them
- use same libpam recipe instead of creating a new. This way other /etc/
stuff are all contained by libpam-runtime
* like openembedded, we package each pam plugin into seperate package now,
with some differnce though:
- Some ${sbindir} binaries are bound to specific PAM plugin. So better to
package them together with corresponding plugin package
- populate_sysroot_prepend is invoked before actual populate_sysroot, at
that time ${D} binaries haven't been tripped. So it's difficult to specify
-dev for those plugin pacakges from _prepend which are simply empty.
actually one -dev/-doc per recipe is one good exercise here.
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Add a patch(should be GPLv3) to fix the compile issue, otherwise only produce
binary for build system in cross-compile environment. Simple function test
done.
Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
Add which-2.20, which is licensed under GPLv3.
The installation will override the busybox "which" command.
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
Revert the change from 28d70bcddb.
Change the upstream commit to id: d30de158c1986d2161647629f279018702a42750.
This fixes the const is read-only issue when compiling.
Signed-off-by: Mark Hatle <mhatle@windriver.com>
Add the ability to specify user level classes via the local.conf.
Use this new capability to add an image-prelink class that does an
image wide cross-prelink activity.
Signed-off-by: Mark Hatle <mhatle@windriver.com>
Fix an issue where pseudo could try to compile incorrectly on an
x86_64 host system. Now it verifies that it should be trying to build
a 32-bit library, and if so the necessary prereqs are available.
Also uprev to the latest version of pseudo changes to enable wrapping
of execl, local variable storage and misc fixes.
Signed-off-by: Mark Hatle <mhatle@windriver.com>
For one, populate-volatile.sh is itself a rcS script which is invoked earlier
than package's own postinst method (last one in rcS). If package has already
installed their volatile files correctly, it doesn't make sense to update volatile
again in postinst since nothing is changed.
On the other hand, dbus/hal are special since their user/group are only created
in the target. If they pre-install volatiles like others, populate-volatile.sh
will report "undefined user" since at that time their user/group haven't been
created. The better way solving this is to generate their volatile in the fly
after user/group are created, and then update volatiles.
This fix [BUGID #121]
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
--with-python= should be followed by the path to python binary, not
prefix, also export several environment for passing building,
fixes [BUGID #69]
Signed-off-by: Qing He <qing.he@intel.com>
If this isn't set, pkg-config will use its inbuilt paths which mean it can
end up looking in the native sysroot.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Move the environment-setup script generation into a separate class and adapt
meta-toolchain to use it.
Add a new dummy target, meta-ide-support, to install an appropriately
configured script to TMPDIR and ensure all of the required packages for target
development are available.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
from 3.0.3
changes:
- rebased patch configure.patch and pcimodules-pciutils.diff
- fix a bug in parameter order in config that causes invalid
search path and library version
- remove unnecessary kernel version reference in configure
- use DESTDIR mechanism for build and installation
- pciutils should RDEPENDS on pciutils-ids
- enable shared library build and package a new package series,
libpci
- conceive a new patch to fix shared library build, default build
would embedd invalid library dependencies
- add another patch to fix build on arm
- fix a bug in previous do_install_depends that used invalid
installation mode
- symbolic link /usr/sbin/pciutils to /usr/bin, so non-root user
can use it as well
Signed-off-by: Qing He <qing.he@intel.com>
