Sorry i am new to this forum, actually my target is as follows:
I want to compile openjdk 8 for arm processor due to one of my requirement .
I have used meta-java layer with openjre 102b14 version.
Its compiling good with arm compiler.
But i want to add any available JIT ie just in time compiler t
From: Wenzong Fan
Uprev refpolicy to 2.20161023 and fix build errors for refpolicy-minimum.
The following changes since commit bae51859f0dbcdde9fd563d15128a6dbbb816801:
audit: upgrade 2.6.6 -> 2.7 (2017-01-09 08:59:55 -0500)
are available in the git repository at:
git://git.pokylinux.org/
From: Wenzong Fan
Signed-off-by: Wenzong Fan
---
.../ftp-add-ftpd_t-to-mlsfilewrite.patch | 0
.../poky-fc-clock.patch | 0
.../poky-fc-corecommands.patch| 0
.../poky-fc-dmesg.patch
From: Wenzong Fan
Fix build errors:
| policy/modules/system/init.te:1120:ERROR 'class dbus is not within scope' at
token ';' on line 40246:
| allow initrc_t init_t:dbus send_msg;
| allow init_t initrc_t:dbus { send_msg acquire_svc };
Signed-off-by: Wenzong Fan
---
...07-refpolicy-minimum-syst
On 01/09/2017 02:12 PM, Alexander Kanavin wrote:
> On 01/07/2017 05:29 PM, Robert P. J. Day wrote:
>> colleague wants to know how one stays up to date with security
>> alerts related to YP releases, i checked out the yocto-security
>> mailing list:
>>
>> https://lists.yoctoproject.org/pipermail/y
On 10 January 2017 at 10:01, Bent Bisballe Nyeng wrote:
> So /is/ the yocto-security mailinglist considered "dead"? Or has there
> simply not been any security issues for a while?
>
IIRC, yocto-security was more to discuss security issues, not an
announcement of security related fixes. If you c
On 01/10/2017 11:29 AM, Burton, Ross wrote:
On 10 January 2017 at 10:01, Bent Bisballe Nyeng
mailto:x...@mjolner.dk>> wrote:
So /is/ the yocto-security mailinglist considered "dead"? Or has there
simply not been any security issues for a while?
IIRC, yocto-security was more to discuss security i
[[yocto] [meta-selinux][PATCH 0/2] uprev refpolicy to 2.20161023] On 17.01.10
(Tue 00:54) wenzong@windriver.com wrote:
> From: Wenzong Fan
>
> Uprev refpolicy to 2.20161023 and fix build errors for refpolicy-minimum.
>
> The following changes since commit bae51859f0dbcdde9fd563d15128a6dbbb
Wenzong / Shrikant,
I thought I knew the answer to the above question, and maybe my
understanding is still correct, but I think I need to ask it now anyway.
I don't use refpolicy-minimum for anything, so when I did the updates to
refpolicy*_git I didn't even glance at refpolicy-minimum_git. Wenz
Hi Joe,
On Tue, Jan 10, 2017 at 8:18 PM, Joe MacDonald
wrote:
>
> Wenzong / Shrikant,
>
> I thought I knew the answer to the above question, and maybe my
> understanding is still correct, but I think I need to ask it now anyway.
>
> I don't use refpolicy-minimum for anything, so when I did the u
Hi,
I'm using generated Poky SDK to cross-compile our program source-codes, which
works fine.
Now I wish to integrate the build of the project into Yocto recipes using our
makefiles.
However, some custom parameters in the makefiles are using the variables
OECORE_TARGET_SYSROOT and OECORE_
The loop to compare the recorded conffile hash with their hash on disk is
outputted at level INFO but the loop was executed at level NOTICE and higher.
This means that if a conffile had been deleted the status operation would
produce error messages for output it isn't displaying.
Signed-off-by: R
Handle conffiles that don't exist gracefully so that instead of showing an error
message from file_md5sum_alloc() a notice that the file has been deleted is
shown instead.
Signed-off-by: Ross Burton
---
libopkg/conffile.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/libopkg/conffile.
I am having a heck of a hard time getting a minor kernel config fragment
applied.
In order to minimize all variables, I am simply trying to build linux-yocto for
a qemux86 MACHINE target.
There had been some discussion on the mailing list previously that suggested
making sure linux-yocto.inc w
These are specified differently when using the Yocto build system you
should not be using these variables in your makefiles
On Tue, Jan 10, 2017 at 8:11 AM Karim ATIKI wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi,
>
>
>
>
>
>
>
> I'm using generated Poky SDK to cross-compile our program source-codes,
On Tue, 10 Jan 2017 10:37:48 Bent Bisballe Nyeng wrote:
> I found the list initially through this page:
> https://wiki.yoctoproject.org/wiki/Security where it is described as the
> security [at] yoctoprojct [dot] org being the discussion list and the yocto
> [dash] security [at] yoctoproject[dot] o
On 2017-01-10 1:05 PM, Schmitt, Richard wrote:
I am having a heck of a hard time getting a minor kernel config fragment
applied.
In order to minimize all variables, I am simply trying to build
linux-yocto for a qemux86 MACHINE target.
What release ? Everything is working here, but I can s
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Tuesday, January 10, 2017 2:58 PM
To: Schmitt, Richard ; yocto@yoctoproject.org
Subject: Re: [yocto] kernel config fragments not applied
On 2017-01-10 1:05 PM, Schmitt, Richard wrote:
>> I am having a he
On 2017-01-10 4:13 PM, Schmitt, Richard wrote:
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Tuesday, January 10, 2017 2:58 PM
To: Schmitt, Richard ; yocto@yoctoproject.org
Subject: Re: [yocto] kernel config fragments not applied
On 2017-01-10 1:05
On 2017-01-10 4:20 PM, Bruce Ashfield wrote:
On 2017-01-10 4:13 PM, Schmitt, Richard wrote:
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Tuesday, January 10, 2017 2:58 PM
To: Schmitt, Richard ;
yocto@yoctoproject.org
Subject: Re: [yocto] kernel co
On 2017-01-10 4:27 PM, Bruce Ashfield wrote:
On 2017-01-10 4:20 PM, Bruce Ashfield wrote:
On 2017-01-10 4:13 PM, Schmitt, Richard wrote:
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Tuesday, January 10, 2017 2:58 PM
To: Schmitt, Richard ;
yocto@y
On 01/10/2017 10:25 PM, Joe MacDonald wrote:
[[yocto] [meta-selinux][PATCH 0/2] uprev refpolicy to 2.20161023] On 17.01.10
(Tue 00:54) wenzong@windriver.com wrote:
From: Wenzong Fan
Uprev refpolicy to 2.20161023 and fix build errors for refpolicy-minimum.
The following changes since com
Khem,
Ok.
How are they specified using Yocto build system ?
Is there any doc link ?
K.
De : Khem Raj
Envoyé : mardi 10 janvier 2017 20:39
À : Karim ATIKI; yocto
Objet : Re: [yocto] [bitbake] OECORE_TARGET_SYSROOT and OECORE_NATIVE_SYSROOT
variables not ava
23 matches
Mail list logo
