[yocto] Release Candidate Build for yocto-1.7.rc2 now available.

2014-10-01 Thread Poky Build User

A release candidate build for yocto-1.7.rc2 is now available at:

 
http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc2


Please begin QA on this build as soon as possible.


Build hash information: 
meta-intel : b25eb7e4dfee7802d4eae657fa5e482a1a010190 
meta-fsl-arm : 2680f54d02fa6efe4cd2aaef7bda9e46cf3e9672 
meta-minnow : 13a5f2ab84c7284647a3e067a33109c11dae0568 
meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 
meta-fsl-ppc : deb326df1489d4844f911605a2627f95c89b167f 
poky : abf9372358e5db70e7d707a5a732c4ec7d0f2efe 


This is an automated message from
The Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder
Email: elizabeth.flana...@intel.com 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] fetch task not run after SRCREV updated

2014-10-01 Thread Burton, Ross
On 1 October 2014 00:00,  ezek...@sanborndeasis.net wrote:
 obviously works fine. It appears to come down to the do_fetch stampfile. Is
 this intended functionality? It seems that if my SRCREV does not match
 against what was downloaded that should be invalidated and the fetch should
 be forced. Am I missing something?

As Gary said, this is fixed in master.  The idiomatic workaround is to
embed SRCREV into PV, such as PV=1.2.3+git${SRCSRV}.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] fetch task not run after SRCREV updated

2014-10-01 Thread Paul Eggleton
On Wednesday 01 October 2014 10:34:50 Burton, Ross wrote:
 On 1 October 2014 00:00,  ezek...@sanborndeasis.net wrote:
  obviously works fine. It appears to come down to the do_fetch stampfile.
  Is
  this intended functionality? It seems that if my SRCREV does not match
  against what was downloaded that should be invalidated and the fetch
  should
  be forced. Am I missing something?
 
 As Gary said, this is fixed in master.  The idiomatic workaround is to
 embed SRCREV into PV, such as PV=1.2.3+git${SRCSRV}.

I think you meant:

PV = 1.2.3+git${SRCPV}

;)

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] libc6-dev issue

2014-10-01 Thread Ashish Dalela
Folks,

While trying to install libc6-dev RPM I get the below error -

error: Can't install libc6-dev-2.17-r3@i586: no package provides
libsegfault-dev

I can't figure out how to build libsegfault-dev. Can anyone provide
guidance?

I tried eglibc clean and rebuild a few times. Even did this with one thread
to avoid race conditions.

Thanks
--Ashish
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-security][PATCH][wip] libseccomp: git version recipe

2014-10-01 Thread Armin Kuster
The latest git repo has Aarch64 and Mips(64) support.
Aarch64 CONFIG_SECCOMP_FILTER support is not complete and is targeted for v3.18.

An update to libseccomp is scheduled after the v3.18 kernel is released.

I don't plan to included this into the layer. The intent is to provide new arch 
support while we wait for the official release.

Signed-off-by: Armin Kuster akuster...@gmail.com
---
 recipes-security/libseccomp/libseccomp_git.bb | 49 +++
 1 file changed, 49 insertions(+)
 create mode 100644 recipes-security/libseccomp/libseccomp_git.bb

diff --git a/recipes-security/libseccomp/libseccomp_git.bb 
b/recipes-security/libseccomp/libseccomp_git.bb
new file mode 100644
index 000..3197208
--- /dev/null
+++ b/recipes-security/libseccomp/libseccomp_git.bb
@@ -0,0 +1,49 @@
+SUMMARY = interface to seccomp filtering mechanism
+DESCRIPTION = The libseccomp library provides and easy to use, platform 
independent,interface to the Linux Kernel's syscall filtering mechanism: 
seccomp.
+SECTION = security
+LICENSE = GPL-2.0
+LIC_FILES_CHKSUM = 
file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6
+
+SRCREV=f6c219703e3e654e60bb341ab4de362a133fdba6
+SRC_URI = git://git.code.sf.net/p/libseccomp/libseccomp;protocol=git \
+
+
+inherit autotools-brokensep
+
+S=${WORKDIR}/git
+
+do_configure_prepend () {
+
+(
+cat  'EOF'
+tests-build:
+   ${MAKE} ${AM_MAKEFLAGS} ${check_PROGRAMS}
+
+tests-install:
+   install ${check_PROGRAMS} ${DESTDIR}
+   @list='$(check_PROGRAMS)'; \
+   for p in $$list; do install $$p.tests ${DESTDIR}; done
+
+   install regression testdiff testgen ${DESTDIR}
+
+EOF
+)  tests/Makefile.am
+}
+do_compile_append() {
+oe_runmake -C tests tests-build
+}
+
+do_install() {
+install -d ${D}/${libdir}/${BPN}/tests
+oe_runmake -C tests DESTDIR=${D}/${libdir}/${BPN}/tests tests-install
+
+install -d ${D}/${libdir}/${BPN}/tools
+install tools/scmp_bpf_sim tools/scmp_arch_detect \
+tools/scmp_bpf_disasm tools/scmp_app_inspector \
+tools/check-syntax tools/scmp_sys_resolver ${D}/${libdir}/${BPN}/tools
+
+}
+
+PACKAGES += ${PN}-tests 
+FILES_${PN}-tests = tests/* tools/* 
+FILES_${PN}-dbg += ${libdir}/${BPN}/tests/.debug/* 
${libdir}/${BPN}/tools/.debug/*
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] yocto 1.6 - beaglebone black - cape manager

2014-10-01 Thread TakkTakk
No Andreas. I could not solve the problem.

2014-09-29 11:15 GMT+02:00 Andreas Galauner andr...@galauner.de:
 On 26.09.2014 15:17, TakkTakk wrote:
 ok, I removed uEnv.txt, pressed the boot switch.
 Starting kernel ... and hang.
 why - Image Name:   Linux-3.14.0-yocto-standard  ?

 I don't have a solution to your problem, but I can at least assure to
 you that you are not alone ;)

 I'm facing the same problem. I have a Beaglebone Black Rev. A6 which
 boots fine with Yocto 1.6 (no meta-beaglebone) and kernel 3.14.
 On another newer board with Rev. B it hangs after Starting Kernel. I
 have no idea why.

 According to the elinux.org wiki the difference between Revision A and B
 is mainly another Version of the SoC (AM3358BZCZ100 in Rev. B and
 AM3359AZCZ100 in Rev. A).

 Did you manage to fix your problem by now?

 - Andy

 --
 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto



-- 
TakTak
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] fetch task not run after SRCREV updated

2014-10-01 Thread ezekiel
Is this the fix

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=202ae5af74f546a9788290a96b0f3c370ee047b2

-Ezekiel

Message: 1
Date: Tue, 30 Sep 2014 17:26:27 -0600
From: Gary Thomas g...@mlbassoc.com
To: yocto@yoctoproject.org
Subject: Re: [yocto] fetch task not run after SRCREV updated
Message-ID: 542b3c23.1040...@mlbassoc.com
Content-Type: text/plain; charset=windows-1252; format=flowed

On 2014-09-30 17:00, ezek...@sanborndeasis.net wrote:
 I noticed that if I update the SRCREV value in a recipe to a newer rev for a 
 GIT repository, OE does not think it needs to run the fetch step unless I 
 force it. In other words

 bitbake -c fetch foobar

 does not pick up that the SRCREV it was downloaded for is no longer correct.

 bitbake -f -c fetch foobar

 obviously works fine. It appears to come down to the do_fetch stampfile. Is 
 this intended functionality? It seems that if my SRCREV does not match 
 against what was downloaded that
 should be invalidated and the fetch should be forced. Am I missing something?

Check the recent [last week or so] logs - this has just been addressed
and should work with the latest master [or maybe master-next]

-- 

Gary Thomas | Consulting for the
MLB Associates | Embedded world

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] fetch task not run after SRCREV updated

2014-10-01 Thread Burton, Ross
On 1 October 2014 23:00,  ezek...@sanborndeasis.net wrote:
 Is this the fix

 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=202ae5af74f546a9788290a96b0f3c370ee047b2

Yes, that's it.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Fan speed control

2014-10-01 Thread Chris Tapp
Are there any recipes compatible with generic_pc to allow the cpu and system 
fan speeds to be controlled?

--

Chris Tapp
opensou...@keylevel.com
www.keylevel.com


You can tell you're getting older when your car insurance gets real cheap!

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Release Candidate Build for yocto-1.7.rc3 now available.

2014-10-01 Thread Poky Build User
-e 
A release candidate build for yocto-1.7.rc3 is now available at:

 
http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc3


Please begin QA on this build as soon as possible.


Build hash information: 
meta-intel : 9f815ab761e6b524625e4180397233eeb728f84e 
meta-fsl-arm : 2680f54d02fa6efe4cd2aaef7bda9e46cf3e9672 
meta-minnow : 13a5f2ab84c7284647a3e067a33109c11dae0568 
meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 
meta-fsl-ppc : deb326df1489d4844f911605a2627f95c89b167f 
poky : 5367855fe56db0c09b8fa7bb423b9de18d11eecc 


This is an automated message from
The Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder
Email: elizabeth.flana...@intel.com 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto