Is your kernel already building from linux-yocto-custom ? Or are you
using the default linux-yocto kernel and recipes already ?
I have a project that is using linux-yocto-custom and another project
which is using the default linux-yocto kernel.
If you are using one of the standard qemu
This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and
will show how long it is since their last mannual version check.
You can check the detail information at
http://packages.yoctoproject.org/manuallychkinfo
PackageName
This mail was sent out by Package Report System.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-xxx in upstream_tracking files to ignore this
recipe remainder until newer
at 2013-9-20 19:00, Laurentiu Palcu wrote:
Hi,
On Fri, Sep 20, 2013 at 06:25:19PM +0800, Li Zhijian wrote:
III） compile a simple C program
# cat test.c
int main ()
{
printf(hello world\n);
return 0;
}
# source toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
# $CC -o test
On 13-09-22 12:05 PM, John Doe wrote:
Is your kernel already building from linux-yocto-custom ? Or are you
using the default linux-yocto kernel and recipes already ?
I have a project that is using linux-yocto-custom and another project
which is using the default linux-yocto kernel.
If you
at 2013-9-23 10:34, Li Zhijian wrote:
at 2013-9-20 19:00, Laurentiu Palcu wrote:
Hi,
On Fri, Sep 20, 2013 at 06:25:19PM +0800, Li Zhijian wrote:
III） compile a simple C program
# cat test.c
int main ()
{
printf(hello world\n);
return 0;
}
# source
This is needed to build policy modules outside of the refpolicy.
Policy module build systems need to determine the name of the policy
that will be in effect on the target host. This allows them to
locate the policy headers that will be under
$sysroot/usr/share/selinux/$name/include. Given that
Cc'ing Mark.
On 09/22/2013 11:51 PM, Philip Tricca wrote:
This is needed to build policy modules outside of the refpolicy.
Policy module build systems need to determine the name of the policy
that will be in effect on the target host. This allows them to
locate the policy headers that will be
