On Wed, 2018-11-07 at 09:01 +, Richard Purdie wrote:
> On Fri, 2018-11-02 at 14:03 +0800, Chen Qi wrote:
> > The current logic for checking cve tag is not correct. It errors
> > out if and only if the patch contains a line which begins with
> > CVE-- and contains nothing else.
> >
> >
Hi Anibal/RP,
> In order to do a distributed Boards testing the Yocto Autobuilder
> needs to publish in some place accessible the artifacts (image,
> kernel, etc) to flash/boot the board and the test suite expected to
> execute.
[Reply] That is correct, since Linaro have this in place to use
On 11/09/2018 03:56 AM, Bruce Ashfield wrote:
On 2018-11-07 9:05 p.m., Hongzhi.Song wrote:
The maximum cpus are 64 on intel-x86-32.
But intel-x86-64 support ranges from 1 to 8192.
So we should move the config to intel-x86-64.cfg.
ok. This makes more sense, but two questions:
- why limit
On Friday, 9 November 2018 11:41:42 AM NZDT Paul Eggleton wrote:
> You could accomplish the latter using PACKAGECONFIG_pn-python3 = "pgo" at
> the configuration level
Oops, I meant PACKAGECONFIG_remove_pn-python3 = "pgo" here.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
On Monday, 5 November 2018 4:32:26 PM NZDT Paul Eggleton wrote:
> On Wednesday, 31 October 2018 11:06:31 AM NZDT Scott Rifenbark wrote:
> > I have an initial section at
> > https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#moving-to-the-yocto-project-2.6-release,
> > which is based on
Is there a way to configure meta-mono to ahead of time (AOT) compile the system
assemblies for the target?
Specifically, I would like to not have to run the following on my targets.
sudo mono --aot /usr/lib/mono/4.5/mscorlib.dll
for f in /usr/lib/mono/gac/*/*/*.dll; do sudo mono --aot "$f"; done
Hi Markus,
Have you tried doing it in the postinst step executed on your target? Try:
pkg_postinst_ontarget_${PN} () {
setcap cap_net_raw+eip $D${bindir}/node
}
RDEPENDS_${PN} += "libcap-bin"
/ptw
> I have tested to set capabilities on the node binary within a custom recipe
> (custom
On 2018-11-07 9:05 p.m., Hongzhi.Song wrote:
The maximum cpus are 64 on intel-x86-32.
But intel-x86-64 support ranges from 1 to 8192.
So we should move the config to intel-x86-64.cfg.
ok. This makes more sense, but two questions:
- why limit to 256 on x86-64 ?
- why not put 64 as the limit
A build flagged for QA (yocto-2.4.4.rc1) was completed on the autobuilder and
is available at:
https://autobuilder.yocto.io/pub/releases/yocto-2.4.4.rc1
Build hash information:
bitbake: 8bd16328a9332c57b03198826e22b48fadcd21d9
eclipse-poky-neon:
We want to build everything without sstate during bringup testing.
Adding oe-selftest will catch errors other targets wouldn't. We just want to
test on qemuarm64 and qemux86-64 architectures so remove beaglebone as an
unneeded third. This takes advantage of the template as well.
Signed-off-by:
I have tested to set capabilities on the node binary within a custom recipe
(custom layer) but that failed.
pkg_postinst_${PN} () {
setcap cap_net_raw+eip $D${bindir}/node
}
PACKAGE_WRITE_DEPS = "libcap-native"
RDEPENDS_${PN} = "libcap"
The error message:
ERROR:
11 matches
Mail list logo
