Re: [yocto] defconfig file (or fragment files) not used

On 2018-03-30 9:08 AM, Vincent Daanen wrote: Hi On 03/29/18 16:12 PM, Bruce Ashfield wrote: [cut] Do you have all of the CAN* Kconfig dependencies in your defconfig ? No only the ones I need If you don't, the kernel config subsystem will turn them off. Also note that a 'defconfig'

Re: [yocto] defconfig file (or fragment files) not used

Hi > On 03/29/18 16:12 PM, Bruce Ashfield wrote: > [cut] > Do you have all of the CAN* Kconfig dependencies in your defconfig ? No only the ones I need > If you don't, the kernel config subsystem will turn them off. > > Also note that a 'defconfig' translates to a merge config run (yes, even

[yocto] adding other languages to yocto build

friends, ? anyone using ada, objective c, c#, swift or any other such languages. if so can you point me to a recipe. my interest is in the order listed. looking for an alternative to C/C++ TIA srini CONFIDENTIALITY NOTICE: This email message and any

Re: [yocto] [meta-raspberrypi] Has anybody run VC4 + X + recent meta/masters lately

On Thu, Mar 29, 2018 at 11:46 PM, Trevor Woerner wrote: > On Thu 2018-03-29 @ 11:34:08 PM, Andreas Müller wrote: >> On Thu, Mar 29, 2018 at 11:23 PM, Andreas Müller >> wrote: >> > On Thu, Mar 29, 2018 at 11:05 PM, Trevor Woerner

Re: [yocto] ClamAV PCRE support

Hi Tom, On 03/29/2018 11:29 PM, Tom Gibson wrote: > When I run clamscan on our board I get a number of errors of the > form “logical signature for … uses PCREs but support is disabled, > skipping” so the solution would appear to be to add PCRE support. In > the ClamAV bitbake

[yocto] meta-mono: breaking as libglade removed

Hi, libglade seems to have been removed which is breaking meta-mono builds. What's best to fix this? Should I be adding the recipe into meta-mono? Thanks, Alex -- ___ yocto mailing list yocto@yoctoproject.org

[yocto] [meta-java][PATCH 3/3] openjdk-8: use ca-certificates-java

From: André Draszik The OpenJDK-8 package currently comes with a trustStore that was generated at OpenJDK-8-native build time from *all* certificates available in the system, not just from those that are marked as trusted. This isn't right... openjdk-8 and openjre-8 now

[yocto] [meta-java][PATCH 2/3] layer.conf: add ca-certificates-java to SIGGEN_EXCLUDERECIPES_ABISAFE

From: André Draszik Same as ca-certificates in openembedded-core Signed-off-by: André Draszik --- conf/layer.conf | 4 1 file changed, 4 insertions(+) diff --git a/conf/layer.conf b/conf/layer.conf index 84a4d89..60fd726 100644 ---

[yocto] [meta-java][PATCH 1/3] ca-certificates-java: add recipe to generate trustStore

From: André Draszik The OpenJDK-8 package currently comes with a trustStore that was generated at OpenJDK-8-native build time from *all* certificates available in the system, not just from those that are marked as trusted. This isn't right... So this recipe hooks into

[yocto] [meta-java][PATCH 0/3] Java CA certificates updates

openjdk-8 and openjre-8 use a trustStore that has nothing to do with the system trusted CA certificates as provided by the ca-certificates package. These patches fix both to use the system CA certificates instead. The depend on oe-core patch ca-certificates: use relative symlinks from