I attached the depends .dot file and also a small perl-ptest.info file with
only the perl-ptest occurences.
On Thursday, May 22, 2014 4:15 PM, Paul Eggleton
wrote:
On Thursday 22 May 2014 06:00:02 Alexandru Vaduva wrote:
> On Thursday, May 22, 2014 3:43 PM, Paul Eggleton
> wrote:
The hack will put the line: require perl-ptest.incinside a if structure.
The if will test if ptest is in the image-features or not.
On Thursday, May 22, 2014 3:43 PM, Paul Eggleton
wrote:
On Thursday 22 May 2014 05:38:41 Alexandru Vaduva wrote:
> it appear, it shouldn`t I believe.
>
Alexandru Vaduva wrote:
> On Thursday, May 22, 2014 3:19 PM, Paul Eggleton
> wrote:
> > On Thursday 22 May 2014 03:31:05 Alexandru Vaduva wrote:
> > > Does anyone has any input on the next bug:
> > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=6203
> >
&g
Hello Paul I do not have a conclusion from buildhistory, but maybe I do not
know for what to look.
On Thursday, May 22, 2014 3:19 PM, Paul Eggleton
wrote:
Hi Alex,
On Thursday 22 May 2014 03:31:05 Alexandru Vaduva wrote:
> Does anyone has any input on the next bug:
>
Does anyone has any input on the next bug:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6203
Thanks,
Alex--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
d
an error.
Solved this with the last patch.
Alex
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Friday, April 11, 2014 3:46 PM
To: Valentin Cobelea; Diego Sueiro
Cc: yocto@yoctoproject.org; Alexandru Vaduva; Paul Eggleton
Subject: Re: [yocto]
From: "Alexandru.Vaduva"
The problem is well known for 64 bits architectures and the solution
is offered in the same recibe but in the meta-selinux layer.
Signed-off-by: Alexandru.Vaduva
---
recipes-security/libcap-ng/libcap-ng/python.patch | 39 +
recipes-security/libcap
From: "Alexandru.Vaduva"
The value was defined as:
FILESEXTRAPATHS_prepend := "${THISDIR}/refpolicy-${PV}:"
and changed it to:
FILESEXTRAPATHS_prepend := "${THISDIR}/refpolicy-2.20130424:"
because the bb that inherit this overwrites the PV every time,
changing its name.
Upstream-Status:
From: "Alexandru.Vaduva"
The value was defined as:
FILESEXTRAPATHS_prepend := "${THISDIR}/refpolicy-${PV}:"
and changed it to:
FILESEXTRAPATHS_prepend := "${THISDIR}/refpolicy-2.20130424:"
becase the bb that inherit this overwrites the PV every time,
changing its name.
Signed-off-by: Alexandru.V
From: "Alexandru.Vaduva"
The value was defined as:
FILESEXTRAPATHS_prepend := "${THISDIR}/refpolicy-${PV}:"
and changed it to:
FILESEXTRAPATHS_prepend := "${THISDIR}/refpolicy-2.20130424:"
becase the bb that inherit this overwrites the PV every time,
changing its name.
Signed-off-by: Alexandru.V
From: "Alexandru.Vaduva"
The value was defined as:
FILESEXTRAPATHS_prepend := "${THISDIR}/refpolicy-${PV}:"
and changed it to:
FILESEXTRAPATHS_prepend := "${THISDIR}/refpolicy-2.20130424:"
because the bb that inherit this overwrites the PV every time,
changing its name.
Upstream-Status:
Hello guys, I am trying to enable the functionality for the camera.
I am trying to solve the following problem:
mmal: mmal_vc_component_create: failed to create component
'vc.ril.camera'
mmal: mmal_component_create_core: could not create component
'vc.ril.camera'
mmal: Failed to create
Hello guys,
I imported an external toolchain into yocto using meta-sourcery layer.
It build fine some userspace recipes and also the kernel but I git some
errors on busybox.
For the busybox the error is:
mips64-nlm-linux-ld
--sysroot=/home/alexandru/Downloads/yocto/poky/buildKernel/tmp/sysroots/x
.
Thanks.
On Thu, Oct 31, 2013 at 4:44 PM, Khem Raj wrote:
> On Thu, Oct 31, 2013 at 1:38 AM, jan alexandru vaduva
> wrote:
> > Thanks for the information. That is what I was looking for. I was asking
> of
> > the canadian build possibilities for a toolchian and I found the
Thanks for the information. That is what I was looking for. I was asking of
the canadian build possibilities for a toolchian and I found the answer to
that question.
If I may ask. There was a thread:
"
>* I have a cross-toolchain supplied by an ARM SoC vendor which I need
to*>* use to build my di
Hello,
I have a curiosity:
Take a toolchain that builds for a 32-bits architecture, but breaks for a
64-bits one.
Is there a way to ensure that when builded with Yocto that toolchain will
be generated and used to build target specific recipes.
Thanks,
Alex
__
on. to be available
into the final rootfs archive.
Alex
.
On Fri, Oct 18, 2013 at 4:41 PM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:
> Hi Alex,
>
> On Friday 18 October 2013 15:19:57 jan alexandru vaduva wrote:
> > Is there any way of defining a variable into
Hello everyone,
Is there any way of defining a variable into a recipe and use it in another.
I tried: export VAR="value" but when I tested it`s existence in devshell it
did not exist(echo $VAR).
Defining this variable in local.conf is not a viable solution.
Thank you,
Alex
_
Hello all,
I am trying to use a toochain from meta-sourcery layer - Mentor
Graphics(Code Sourcery) - and I get the following error when building a
recipe:
ERROR: ExpansionError during parsing
/media/sdc1/fb/alvd/test/broadcom/poky/meta-sourcery/recipes/meta/external-
sourcery-toolchai
101 - 119 of 119 matches
Mail list logo
