On Fri, Jan 18, 2019 at 6:46 AM srinivasan wrote:
>
> Dear Yocto Experts,
>
> I am seeing the below error when i am trying to integrate freescale
> layers into my custom os?
Which imx8 MACHINE are you trying?
Daiane
>
> srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/customos/build_customosdi
On Fri, 2019-01-18 at 05:30 +0100, Ulf Samuelsson wrote:
> So if KNOWN_TASKS is defined in a configuration file in oe-core, it
> would be OK?
> It needs to be extended to check for KNOWN_TASKS == None of course.
No, this is too fragile. We then have to maintain two different lists
of tasks. If we
Signed-off-by: Ross Burton
---
recipes-security/AppArmor/apparmor_2.12.bb | 4 ++--
recipes-security/AppArmor/files/py-libdir.patch | 13 +
2 files changed, 15 insertions(+), 2 deletions(-)
diff --git a/recipes-security/AppArmor/apparmor_2.12.bb
b/recipes-security/AppArmor/app
setuptools will install into what python3-native thinks $libdir is, which may
not match the target $libdir. Pass in libdir as appropriate to force the
correct paths.
Signed-off-by: Ross Burton
---
recipes-security/AppArmor/apparmor_2.12.bb | 5 ++--
recipes-security/AppArmor/files/py-libd
I try AUTOREV in the recipe app_1.0.bb
SRCREV := "${AUTOREV}"
But it doesn't work.
Which other variables could inhibit AUTOREV?
MZ
Il 17/01/19 15:09, Burton, Ross ha scritto:
> Look up AUTOREV in the manual, that does exactly what you want.
>
> Ross
>
> On Thu, 17 Jan 2019 at 14:08, Mauro Zi
> 18 jan. 2019 kl. 12:29 skrev Richard Purdie
> :
>
>> On Fri, 2019-01-18 at 05:30 +0100, Ulf Samuelsson wrote:
>> So if KNOWN_TASKS is defined in a configuration file in oe-core, it
>> would be OK?
>> It needs to be extended to check for KNOWN_TASKS == None of course.
>
> No, this is too frag
> I try AUTOREV in the recipe app_1.0.bb
> SRCREV := "${AUTOREV}"
> But it doesn't work.
> Which other variables could inhibit AUTOREV?
Could you share complete recipe, please?
I would give it a try:
SRCREV = "${AUTOREV}"
Best regards,
Lukasz Zemla
--
__
On Fri, 2019-01-18 at 15:16 +0100, Ulf Samuelsson wrote:
> > 18 jan. 2019 kl. 12:29 skrev Richard Purdie <
> > richard.pur...@linuxfoundation.org>:
> >
> > > On Fri, 2019-01-18 at 05:30 +0100, Ulf Samuelsson wrote:
> > > So if KNOWN_TASKS is defined in a configuration file in oe-core,
> > > it
> >
> 18 jan. 2019 kl. 15:40 skrev Richard Purdie
> :
>
> On Fri, 2019-01-18 at 15:16 +0100, Ulf Samuelsson wrote:
>>> 18 jan. 2019 kl. 12:29 skrev Richard Purdie <
>>> richard.pur...@linuxfoundation.org>:
>>>
On Fri, 2019-01-18 at 05:30 +0100, Ulf Samuelsson wrote:
So if KNOWN_TASKS is
I've rebased and made some minor changes to a Python 3.7.1 patch from
patchworks. I'd be interested in seeing this patch make it into master if
possible.
Could anyone provide any guidance on the process of submitting a patch?
Thanks,
Seth
--
___
yocto
On Fri, 18 Jan 2019 at 15:08, Ulf Samuelsson wrote:
> We could insert a check if the KNOWN_TASKS is valid in a verification test.
> When building core-image-minimal, the task order within core-image-minimal is
> analyzed, (dependencies on all other recipes is filtered away).
> Then you find out i
> On 18 Jan 2019, at 16.34, Burton, Ross wrote:
>
>> On Fri, 18 Jan 2019 at 15:08, Ulf Samuelsson wrote:
>> We could insert a check if the KNOWN_TASKS is valid in a verification test.
>> When building core-image-minimal, the task order within core-image-minimal
>> is analyzed, (dependencies o
> 18 jan. 2019 kl. 16:56 skrev Alexander Kanavin :
>
>
>
>>> On 18 Jan 2019, at 16.34, Burton, Ross wrote:
>>>
>>> On Fri, 18 Jan 2019 at 15:08, Ulf Samuelsson wrote:
>>> We could insert a check if the KNOWN_TASKS is valid in a verification test.
>>> When building core-image-minimal, the t
The definition in poky.conf has been updated.
Signed-off-by: Peter Kjellerstedt
---
This of course assumes that the corresponding patch that I just sent
to the openembedded-core mailing list has been integrated first.
documentation/ref-manual/ref-variables.xml | 2 +-
1 file changed, 1 insertio
You can start by reading the following:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Alex
On Fri, 18 Jan 2019 at 16:24, Seth McLean wrote:
>
> I've rebased and made some minor changes to a Python 3.7.1
I try BB_SRCREV_POLICY in conf/local.conf
First I try
BB_SRCREV_POLICY := "clear"
Then I try
BB_SCREV_POLICY_pn-app := "clear"
app_1.0.bb is the recipe with
SRCREV="${AUTOREV}"
SRC_URI += " \
file://git@sourcer/app.git \
"
I'm working with a mixed version of Krogoth/Jethro.
Any
Peter,
Thanks for the patch. See
https://yoctoproject.org/docs/2.7/ref-manual/ref-manual.html#var-SDK_VERSION
for the update.
Scott
On Fri, Jan 18, 2019 at 8:02 AM Peter Kjellerstedt <
peter.kjellerst...@axis.com> wrote:
> The definition in poky.conf has been updated.
>
> Signed-off-by: Peter
All
I am using "rocko"
How can we turn off ipv6 altogether? We are not doing anything to startup ipv6.
Still I see several lines in the logs which look like:
kernel: IPv6: wlan0: IPv6 duplicate address . detected
kernel[288]: IPv6: wlan0: IPv6 duplicate address ... detected
thanks, srini
18 matches
Mail list logo
