From: Mingli Yu
Update /sbin to $base_sbindir to fix the
below warning when usrmerge enabled in
DISTRO_FEATURES.
WARNING: mingetty-1.08-r3 do_package: mingetty: NOT adding alternative provide
/usr/sbin/getty: /usr/sbin/mingetty does not exist
WARNING: mingetty-1.08-r3 do_package: QA Issue: ming
From: Mingli Yu
Update /lib to $nonarch_base_libdir to fix
the below error when usrmerge enabled in
DISTRO_FEATURES.
ERROR: mdadm-4.0-r0 do_package_qa: QA Issue: mdadm package is not obeying
usrmerge distro feature. /lib should be relocated to /usr. [usrmerge]
Signed-off-by: Mingli Yu
---
me
Original approach to add -no- flags cause link time behavior changes
where packages start to lose the -fPIC -DPIC in compiler cmdline and this
list keeps growing as we build more and more packages,
Instead lets just remove the options we dont need from SECURITY_CFLAGS
this makes it more robust and
On Thu, 2018-08-16 at 22:44 +0100, richard.pur...@linuxfoundation.org
wrote:
> On Thu, 2018-08-16 at 17:08 -0400, Bruce Ashfield wrote:
> > I'm getting a strange install issue with x86 that I've never seen
> > before, and that
> > part is unchanged from v3 to v4.
> >
> > .. and then I realized tha
On Thu, Aug 16, 2018 at 10:02 PM, Patchwork
wrote:
> == Series Details ==
>
> Series: "openssl: consolidate target na..." and 6 more
> Revision: 1
> URL : https://patchwork.openembedded.org/series/13570/
> State : failure
>
> == Summary ==
>
> Thank you for submitting this patch series to OpenEm
On Wed, Aug 15, 2018 at 11:26 PM, Martin Hundebøll wrote:
> Hi Andre,
>
> On 15/08/2018 21.47, Andre McCurdy wrote:
>>
>> On Wed, Aug 15, 2018 at 4:59 AM, Martin Hundebøll
>> wrote:
>>>
>>> When the read-only-rootfs image feature is enabled, and openssh is
>>> installed into an image, the ssh dae
release notes:
https://lists.gnupg.org/pipermail/gnutls-devel/2018-July/008584.html
add ssl3 and tls1.3 config options now supported.
Signed-off-by: Armin Kuster
---
meta/recipes-support/gnutls/gnutls.inc | 2 ++
.../gnutls/{gnutls_3.6.2.bb => gnutls_3.6.3.bb}
On Thu, Aug 16, 2018 at 12:34 PM, Andre McCurdy wrote:
> On Tue, Jul 17, 2018 at 2:10 AM, Andrej Valek
> wrote:
>> The main idea is to have libssl and libcrypto in separate packages.
>> This saves space if only single library is needed and also some recipes
>> (in other layers) depend on these l
== Series Details ==
Series: "openssl: consolidate target na..." and 6 more
Revision: 1
URL : https://patchwork.openembedded.org/series/13570/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
On 08/17/2018 03:31 AM, Andre McCurdy wrote:
> On Wed, Aug 15, 2018 at 11:26 PM, Anuj Mittal wrote:
>> Enable profile guided optimization (pgo) for python3. Enabling pgo in
>> python is generally as simple as invoking the target profile-opt which:
>>
>> - builds python binaries with profile instru
The aarch64 build issue in the afalg engine appears to have been
fixed upstream since openssl 1.1.0g:
https://github.com/openssl/openssl/commit/a0c262644eab897b51faf1fa013008052c3754c2
Signed-off-by: Andre McCurdy
---
meta/recipes-connectivity/openssl/openssl_1.1.0i.bb | 6 --
1 file cha
The openssl 1.0 recipe puts the libdir symlink to /etc/ssl/openssl.cnf
in the base openssl package (along with the libdir symlinks to
/etc/ssl/certs and /etc/ssl/private). Keep the openssl 1.1 recipe
aligned with that approach until there's a clear reason to do
something else. For more background,
The openssl 1.1 recipe doesn't have a PACKAGECONFIG option for perl,
so the RDEPENDS for openssl-misc shouldn't be conditional on it.
Signed-off-by: Andre McCurdy
---
meta/recipes-connectivity/openssl/openssl_1.1.0i.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/reci
Merge duplicates + minor reformatting (no functional changes).
Note that the openssl 1.1 recipe still needs to be updated to handle
MIPS Release 6 ISA targets (e.g. linux-mipsisa32r6, etc).
Signed-off-by: Andre McCurdy
---
.../recipes-connectivity/openssl/openssl_1.0.2p.bb | 7 ++--
.../recipe
A single version of the openssl.sh environment-setup script is
currently shared by both the openssl 1.0 and 1.1 recipes. The libdir
path in the script needs to be tweaked for openssl 1.1.
Signed-off-by: Andre McCurdy
---
meta/recipes-connectivity/openssl/openssl_1.1.0i.bb | 1 +
1 file changed,
Formatting and comment tweaks only, no functional changes.
Signed-off-by: Andre McCurdy
---
.../recipes-connectivity/openssl/openssl_1.0.2p.bb | 43 +++---
.../recipes-connectivity/openssl/openssl_1.1.0i.bb | 36 ++
2 files changed, 42 insertions(+), 37 deletions(
According to comments in Configurations/10-main.conf, the linux-elf
target is "... to be used on older Linux machines where gcc doesn't
understand -m32 and -m64".
The linux-x86 target appears to be the newer replacement (currently
the only difference between the two is that linux-x86 adds -m32 to
Signed-off-by: Zhixiong Chi
---
meta/lib/oe/sdk.py | 4
1 file changed, 4 insertions(+)
diff --git a/meta/lib/oe/sdk.py b/meta/lib/oe/sdk.py
index 153b07d76b..5d7e4ed2ac 100644
--- a/meta/lib/oe/sdk.py
+++ b/meta/lib/oe/sdk.py
@@ -88,6 +88,10 @@ class Sdk(object, metaclass=ABCMeta):
When we add the nativesdk-glibc-locale dependence for libc-glibc, if the SDK_OS
is mingw32, it will broken the building with the following error:
>NOTE: Resolving any missing task queue dependencies
>ERROR: Nothing RPROVIDES 'nativesdk-glibc' (but
>virtual:nativesdk:layers/oe-core/meta/recipes-cor
It helps to find/use native tools under ${STAGING_BINDIR_NATIVE}/*-native.
Solving below error:
$ oe-run-native python3-native python3
Running bitbake -e python3-native
Error: Unable to find 'python3' in
.../tmp/work/x86_64-linux/python3-native/3.5.5-r1.0/recipe-sysroot-native/usr/bin:.../tmp/wo
== Series Details ==
Series: oe-run-native: Add *-native directories under STAGING_BINDIR_NATIVE to
PATH environment variable (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/13558/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Cor
Thanks for the review. I have removed colon ":" before
find expression in v2.
Regards,
Jagadeesh
On Fri, Aug 17, 2018 at 2:59 AM, Christopher Larson wrote:
> On Thu, Aug 16, 2018 at 10:45 AM Jagadeesh Krishnanjanappa
> wrote:
>>
>> It helps to find/use native tools under ${STAGING_BINDIR_NATIVE
It helps to find/use native tools under ${STAGING_BINDIR_NATIVE}/*-native.
Solving below error:
$ oe-run-native python3-native python3
Running bitbake -e python3-native
Error: Unable to find 'python3' in
.../tmp/work/x86_64-linux/python3-native/3.5.5-r1.0/recipe-sysroot-native/usr/bin:.../tmp/wo
From: Changqing Li
Signed-off-by: Changqing Li
---
.../unzip/0001-unzip-fix-CVE-2018-135.patch| 48 ++
meta/recipes-extended/unzip/unzip_6.0.bb | 1 +
2 files changed, 49 insertions(+)
create mode 100644
meta/recipes-extended/unzip/unzip/0001-unzip-fix-C
On 08/15/2018 07:08 PM, Konstantin Shemyak wrote:
On 15.8.2018 12:43 changqing...@windriver.com wrote:
[...]
+++
b/meta/recipes-extended/unzip/unzip/0001-unzip-fix-CVE-2018-135.patch
@@ -0,0 +1,46 @@
+From 349f566e6e757458843fa164a0f0584280e1501e Mon Sep 17 00:00:00
2001
+From: Changqing
On 8/16/18 3:37 AM, Chen Qi wrote:
> On other distros like ubuntu/centos, libnss-db usually provides:
> - The libraries
> - The Makefile to create database
> (in /var/db for centos, /var/lib/misc/ for ubuntu)
> - The makedb command (it's in glibc-common for centos7)
>
> What we had is:
> - The
On 8/15/18 11:25 PM, Robert Yang wrote:
>
>
> On 08/16/2018 02:14 PM, Robert Yang wrote:
>> When the assembler reports that the input and output are the same,
>> report the
>> file names involved, in order to help debugging. Also do not equate
>> two files
>> are the same if the have the same
On Tue, Jul 17, 2018 at 2:10 AM, Andrej Valek wrote:
> Some packages have hard-coded path to /etc/ssl location.
> Create a symlinks to correct location.
>
> Signed-off-by: Andrej Valek
> Signed-off-by: Marko Peter
> ---
> meta/recipes-connectivity/openssl/openssl_1.1.0h.bb | 18 +++-
On Thu, 2018-08-16 at 17:08 -0400, Bruce Ashfield wrote:
> I'm getting a strange install issue with x86 that I've never seen
> before, and that
> part is unchanged from v3 to v4.
>
> .. and then I realized that a file has changed in my builds, since
> I'm
> working on 4.18.
>
> This is worth test
On Thu, Aug 16, 2018 at 10:45 AM Jagadeesh Krishnanjanappa <
jkrishnanjana...@mvista.com> wrote:
> It helps to find/use native tools under ${STAGING_BINDIR_NATIVE}/*-native.
>
> Solving below error:
>
> $ oe-run-native python3-native python3
> Running bitbake -e python3-native
> Error: Unable to f
I'm getting a strange install issue with x86 that I've never seen
before, and that
part is unchanged from v3 to v4.
.. and then I realized that a file has changed in my builds, since I'm
working on 4.18.
This is worth testing on the autobuilder, but I will have a v5 that
adds a test for some
file
The existing kernel-devsrc package starts with a full copy of the kernel
source and then starts to strip out elements that are not required.
This results in extra time (I/O) and extra space being taken up in the
final package. The main purpose of the kernel-devsrc package has been to
build modules
On Thu, 2018-08-16 at 13:30 -0400, Bruce Ashfield wrote:
> I have both of the issues fixed, but am waiting for a build cycle to
> complete.
>
> Fundamentally nothing needs to mess with the kernel source for out of
> tree builds anymore, so just testing for 'build' to exist and
> trusting
> that it
On Tue, Jul 17, 2018 at 2:10 AM, Andrej Valek wrote:
> The main idea is to have libssl and libcrypto in separate packages.
> This saves space if only single library is needed and also some recipes
> (in other layers) depend on these library packages.
> Together with this other packages like in 1.0
On Wed, Aug 15, 2018 at 11:26 PM, Anuj Mittal wrote:
> Enable profile guided optimization (pgo) for python3. Enabling pgo in
> python is generally as simple as invoking the target profile-opt which:
>
> - builds python binaries with profile instrumentation enabled,
> - runs a specific profile task
== Series Details ==
Series: oe-run-native: Add *-native directories under STAGING_BINDIR_NATIVE to
PATH environment variable
Revision: 1
URL : https://patchwork.openembedded.org/series/13558/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This
It helps to find/use native tools under ${STAGING_BINDIR_NATIVE}/*-native.
Solving below error:
$ oe-run-native python3-native python3
Running bitbake -e python3-native
Error: Unable to find 'python3' in
.../tmp/work/x86_64-linux/python3-native/3.5.5-r1.0/recipe-sysroot-native/usr/bin:.../tmp/wo
On 08/15/2018 04:42 PM, Richard Purdie wrote:
On Wed, 2018-08-15 at 16:50 +0100, Richard Purdie wrote:
There has been one failure so far:
https://autobuilder.yocto.io/builders/build-appliance/builds/1201/ste
ps/BuildImages_1/logs/stdio
I suspect we need to tweak the do_populate_poky_src task i
On Wed, Aug 15, 2018 at 10:58 PM, Khem Raj wrote:
> On Wed, Aug 15, 2018 at 9:05 PM Randy MacLeod
> wrote:
>>
>> LGTM.
>>
>> Patched and built on an ubu-16.04 box.
>> I was able to log into both qemux86-64 and qemuppc
>> using core-image-minimal.
>>
>> As people might expect, loads has changed:
>
On 08/10/2018 10:48 AM, Kai Kang wrote:
Add systemd service file of lttng-tools from Fedora
ftp://fr2.rpmfind.net/linux/fedora/linux/development/rawhide
/Everything/source/tree/Packages/l/lttng-tools-2.10.5-1.fc29.src.rpm
And disable the service by default.
s/And disable the service by default
Recipe upgrade statistics:
* Failed(do_compile): 15
gdb, 8.1.1, Khem Raj
libsolv, 0.6.35, Maxin B. John
python3-pycairo, 1.17.1, Derek Straka
mesa, 18.1.6, Otavio Salvador
openssl, 1.0.2p, Alexander Kanavin
elfutils, 0.173, Hongxu Jia
Please see this security advisory:
https://www.openssl.org/news/secadv/20180612.txt
Remove obsolete patch.
Signed-off-by: Andrej Valek
---
...-dofile.pl-only-quote-stuff-that-actually.patch | 29 --
.../{openssl_1.1.0h.bb => openssl_1.1.0i.bb} | 5 ++--
2 files change
Please see this security advisory:
https://www.openssl.org/news/secadv/20180612.txt
Refresh patches
Signed-off-by: Andrej Valek
---
...build-with-clang-using-external-assembler.patch | 0
.../0001-allow-manpages-to-be-disabled.patch | 0
...penssl-force-soft-link-to-avoid-rare-race.patc
can I run qt5 apps on image supporting wayland without x11?
I removed x11 from image distro variable
and I use wayland weston instead.
can i run qt5 apps in this case ?
Thanks,
--
Mohamed Dawod
Computer Engineering Department
Faculty of Engineering
Cairo University
--
__
Thanks for updated version.
Just in case someone needs to build perf with e.g. 3.16 kernel, then you
need bbappend like this:
# need to copy few more files to support building with old 3.16 kernel
PERF_SRC_append = " scripts arch lib"
# ERROR: perf-1.0-r9 do_configure: Path does not exist:
kern
Refresh the following patch:
"disable-graphviz.patch" to fix this warning:
Some of the context lines in patches were ignored. This can lead to
incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify
devtool finish --force-patch-refresh
On other distros like ubuntu/centos, libnss-db usually provides:
- The libraries
- The Makefile to create database
(in /var/db for centos, /var/lib/misc/ for ubuntu)
- The makedb command (it's in glibc-common for centos7)
What we had is:
- The libraries are in glibc-extra-nss
- The Makefile is r
Changes in V2:
* Create makedbs.sh according to the Makefile. Use it so that we can get rid of
the make dependency.
The following changes since commit d4011ce0a37083b19de1769d7f18aa42d7b98137:
bitbake: bb/utils.py: add break_hardlinks helper (2018-08-16 09:50:42 +0100)
are available in the g
On 08/16/2018 04:41 AM, Randy MacLeod wrote:
On 08/15/2018 10:02 AM, Richard Purdie wrote:
On Wed, 2018-08-15 at 15:00 +0800, Chen Qi wrote:
From: Jackie Huang
On other distros like ubuntu/centos, libnss-db usually provides:
- The libraries
- The Makefile to create database
(in /var/db for
On Mon, 2018-08-13 at 17:06 +0800, Dengke Du wrote:
> When we enable nfs-server feature, we should add the required file
> /etc/exports installed by nfs-export-root.
>
> Signed-off-by: Dengke Du
> ---
> meta/classes/core-image.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
We d
Thanks for your inputs.
Indeed I am not using master, but 'pyro'.
I added python3-modules, but still did not get the modules that I wanted. For
example, I see atexit.py in the rootfs in /usr/lib/python2.7. But I dont see
that under python3.5, I need that.
For pexpect and jsonrpclib, I was able
Hi,
I need to know the modifications needed to run Qt5 apps on wayland custom
image instead of x11.
I removed x11 and run wayland weston instead.
when i try to run Qt-cinemaexperience as a test I face the following error
:
---
This application failed to start because it couldnt find or load
On Thu, 2018-08-16 at 12:42 +0530, Sunny Shukla wrote:
> We are using Rocko build for our am335x starter kit. While building
> core-image-minimal (rootfs) we are facing a strange problem, some of
> the libs we have included are getting build but the version appended
> to libs names are not proper,
Signed-off-by: Richard Purdie
---
meta/recipes-core/glibc/glibc-initial.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/glibc/glibc-initial.inc
b/meta/recipes-core/glibc/glibc-initial.inc
index d3cfdcc4ccb..acd0d6b1dc5 100644
--- a/meta/recipes-core/glib
these two lines were typed in local.conf file already
On Thu, Aug 16, 2018 at 4:13 AM Denys Dmytriyenko wrote:
> On Wed, Aug 15, 2018 at 05:20:01PM +0200, Mohamed Dawod wrote:
> > Hi,
> >
> > I am trying to run qt5 application "Qt5-cinematicexperience" on my custom
> > image
> > I faced the foll
1. So far, only qemux86[-64] support hw breakpoint, no matter whether or
not with kvm.
qemuppc: The oe-core configuration uses a PPC G4 system as the
default cpu but qemu doesn't simulate the hw breakpoint register for G4.
qemuarm: The arch more than v7 supports hw breakpoint, however arm use
v5
v4 v5:
modify commit, test cases with kvm, test qemuarm64
v3:
specify arch for the case of hw breakpoint
v2:
test_trace_events_sample of ksample.py
Hongzhi.Song (2):
runtime selftest: test_trace_events_sample of ksample.py
runtime selftest: limit kernel hw bp arches
meta/lib/oe
The debug info can not be written to trace buffer immediately
by thread. So we should sleep some seconds.
Signed-off-by: Hongzhi.Song
---
meta/lib/oeqa/runtime/cases/ksample.py | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/meta/lib/oeqa/runtime/cases/ksample
Please ignore this.
--Hongzhi
On 2018年08月16日 15:36, Hongzhi.Song wrote:
v4:
modify commit, test cases with kvm, test qemuarm64
v3:
specify arch for the case of hw breakpoint
v2:
test_trace_events_sample of ksample.py
Hongzhi.Song (2):
runtime selftest: test_trace_events_sam
Please ignore it.
--Hongzhi
On 2018年08月16日 10:49, Hongzhi.Song wrote:
v4:
modify commit, test cases with kvm, test qemuarm64
v3:
specify arch for the case of hw breakpoint
v2:
test_trace_events_sample of ksample.py
Hongzhi.Song (2):
runtime selftest: test_trace_events_sample
1. So far, only qemux86[-64] support hw breakpoint, no matter whether or
not with kvm.
qemuppc: The oe-core configuration uses a PPC G4 system as the
default cpu but qemu doesn't simulate the hw breakpoint register for G4.
qemuarm: The arch more than v7 supports hw breakpoint, however arm use
v5
v4:
modify commit, test cases with kvm, test qemuarm64
v3:
specify arch for the case of hw breakpoint
v2:
test_trace_events_sample of ksample.py
Hongzhi.Song (2):
runtime selftest: test_trace_events_sample of ksample.py
runtime selftest: limit kernel hw bp arches
meta/lib/oeqa/
The debug info can not be written to trace buffer immediately
by thread. So we should sleep some seconds.
Signed-off-by: Hongzhi.Song
---
meta/lib/oeqa/runtime/cases/ksample.py | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/meta/lib/oeqa/runtime/cases/ksample
Hi,
We are using Rocko build for our am335x starter kit. While building
core-image-minimal (rootfs) we are facing a strange problem, some of
the libs we have included are getting build but the version appended
to libs names are not proper, as shown in the examples below.
1) Building eventlog
BB
64 matches
Mail list logo
