There's a openssl 1.0.1j out now (fixing FOUR (!) CVEs, including "disabling SSLv3 didn't work"...). I think considering the situation we'd take the upgrade for dizzy, even though we've frozen.

Ross,

Presumably the list of affected packages is: - gnutls - openssl - nss Are there more? Will ENEA be able to send patches to these packages? Ross

Hi guys, Yesterday The Register published this: http://www.theregister.co.uk/2014/10/14/nasty_ssl_30_vulnerability_to_drop_tomorrow/ and today following was

It could be, that's largely up to how you want to package things for convenience. Well, I'd hope that what we provide in the "Writing a new recipe" manual section [1] should be helpful enough to get

Hi all, It seems that another vulnerability is coming soon, the advice is disable SSLv3.: http://www.theregister.co.uk/2014/10/14/nasty_ssl_30_vulnerability_to_drop_tomorrow/ From Hanno Böck

Hello, I am trying to add a nativesdk package of a custom recipe to toolchain in Poky-8.0.2. I have added nativesdk-qjson (custom package) to TOOLCHAIN_HOST_TASK variable, but it is throwing following

--- recipes-devtools/oracle-java/oracle-jse-jdk-arm_1.7.0.bb | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 recipes-devtools/oracle-java/oracle-jse-jdk-arm_1.7.0.bb diff

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

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

<pokybuild@...> wrote: Beth, I noticed that the Cc list for the original email looks to be corrupted: Cc: ""@ossystems.com.bryi.zhao,

I still use it every day, but it is being re-worked for 1.8. That being said, the functionality that it added is largely present in core now, and will be addressed by other developer workflow

-e A release candidate build for yocto-1.7.rc4 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc4 Please begin QA on this build as soon as possible. Build hash

Dear all, May I know if anyone has a BSP for PCEngines APU1c ? Thanks. Regards.

just noticed the entry at: http://layers.openembedded.org/layerindex/branch/master/layers for

I bought a Sam5d3 Xplained board and the os on it is 1.5.1 yocto project. I can see that under /lib folder there is only ld.linux.armhf.so, not ld linux.so, which is used by cross compile

Can you please explain how you got your "1.5.1 yocto system"? Did you built it yourself or downloaded prebuilt from the site? If latter, then it should match the toolchain...

These errors occur when I add "-mfloat-abi=hardfp" to the toolchain setting. If I don't add it, no error occurs. Now I think the problem is that 1.5.1 or 1.6.2 toolchain doesn't support hard float,

Of course not - the list wouldn't exist until after the recipe was run, so it's a chicken / egg problem ;-) -- Chris Tapp opensource@... www.keylevel.com ---- You can tell you're getting

That doesn't sound like a toolchain error, but rather an autotools one. Make sure you are setting up cross compilation properly.