From: He Zhe
Backport a patch from upstream to fix the following runtime failure.
The latest nm v2.33.1 outputs symbols addresses without prefix zeros
for "nm -f posix", which causes the following error.
nm01 5 TFAIL: Got wrong format with -f bsd
(From OE-Core rev: 59cb0dd9f8e65b2d398fcaf4d163c
On 01/19/20 13:32, Patchwork wrote:
== Series Details ==
Series: Open file with O_CLOEXEC to avoid fd leak (rev3)
Revision: 3
URL : https://patchwork.openembedded.org/series/22123/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an a
== Series Details ==
Series: Open file with O_CLOEXEC to avoid fd leak (rev3)
Revision: 3
URL : https://patchwork.openembedded.org/series/22123/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have bee
From: Pavel Modilaynen
Use close-on-exec (O_CLOEXEC) flag when open log file to
make sure its file descriptor is not leaked to parent
process on fork/exec.
Signed-off-by: Mingli Yu
---
pseudo_util.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pseudo_util.c b/pseudo_util
== Series Details ==
Series: Open file with O_CLOEXEC to avoid fd leak (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/22123/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have bee
From: Pavel Modilaynen
Use close-on-exec (O_CLOEXEC) flag when open log file to
make sure its file descriptor is not leaked to parent
process on fork/exec.
Signed-off-by: Mingli Yu
---
pseudo_util.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pseudo_util.c b/pseudo_util
== Series Details ==
Series: Open file with O_CLOEXEC to avoid fd leak
Revision: 1
URL : https://patchwork.openembedded.org/series/22123/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been execu
From: Pavel Modilaynen
Use close-on-exec (O_CLOEXEC) flag when open log file to
make sure its file descriptor is not leaked to parent
process on fork/exec.
---
pseudo_util.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pseudo_util.c b/pseudo_util.c
index c867ed6..0ec527b 1
Some baremetal applications might require support from libstdc++
On newlib based toolchains, libstdc++ can be built as a static
library that applications can then link against it.
Pass libsdtc++-(static)dev to LIBC_DEPENDENCIES allowing the
library to be present for cross compilation as well as on
While the gnu style for symbol versioning is the most usual,
--enable-symvers[=style] can be provided several values,
gnu, gnu-versioned-namespace, darwin, darwin-export, and sun,
depending on users needs.
Introduce the SYMVERS_CONF variable to allow the user to
configure the symbol versioning in
Signed-off-by: Wang Mingyu
---
meta/recipes-devtools/dnf/{dnf_4.2.2.bb => dnf_4.2.18.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/dnf/{dnf_4.2.2.bb => dnf_4.2.18.bb} (98%)
diff --git a/meta/recipes-devtools/dnf/dnf_4.2.2.bb
b/meta/recipes-devtools/dnf/
On Sat, 18 Jan 2020 at 15:25, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Sat, 2020-01-18 at 13:22 -0800, Alejandro Enedino Hernandez
> Samaniego wrote:
> > Some baremetal applications might require support from libstdc++.
> >
> > On newlib based toolchains, libstdc++ can be b
On Sat, 2020-01-18 at 22:25 +, Rasmus Villemoes wrote:
> I've added a custom setting to TARGET_LDFLAGS, but then I noticed
> that
> the glibc build ignored that. The glibc do_compile did
>
> LDFLAGS = ""
>
> for a very long time, with the explanation that "# -Wl,-rpath-link
> /lib in LDFLAGS
On Sat, 2020-01-18 at 13:22 -0800, Alejandro Enedino Hernandez
Samaniego wrote:
> Some baremetal applications might require support from libstdc++.
>
> On newlib based toolchains, libstdc++ can be built as a static
> library that applications can then link against it.
>
> Pass libsdtc++-(static)d
On Thu, 2020-01-16 at 15:19 -0500, Trevor Gamblin wrote:
> From: Trevor Gamblin
>
> See bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=13632
>
> Autobuilder tests occasionally fail, reporting that a new logfile
> could not be created. While this failure did occur multiple times, it
> coul
On Sat, Jan 18, 2020 at 6:48 PM Richard Purdie
wrote:
>
> libfm installs mime types we want in our mime-database and it also uses
> desktop files
> containing MimeType.
>
> Signed-off-by: Richard Purdie
> ---
> meta/recipes-support/libfm/libfm_1.3.1.bb | 2 +-
> 1 file changed, 1 insertion(+),
I've added a custom setting to TARGET_LDFLAGS, but then I noticed that
the glibc build ignored that. The glibc do_compile did
LDFLAGS = ""
for a very long time, with the explanation that "# -Wl,-rpath-link
/lib in LDFLAGS can cause breakage if another glibc is in
staging". Is that actually still
Recipe upgrade statistics:
* Failed (devtool error): 19
sysklogd, 2.1, Chen Qi
ifupdown, 0.8.35, Anuj Mittal
rpm, 4.15.1, Mark Hatle
rt-tests, 1.6, Alexander Kanavin
e2fsprogs, 1.45.5, Robert Yang
acl, 2.2.53, Chen Qi
atk, 2.34.1, A
An error like the following is thrown when building
baremetal applications on some x86 architectures:
(machine, osabi, abiversion, littleendian, bits) \
= oe.elf.machine_dict(d)[target_os][target_arch]
Exception: KeyError: i686
Since the i686 (target_arch) key does not exist in the diction
Some baremetal applications might require support from libstdc++.
On newlib based toolchains, libstdc++ can be built as a static
library that applications can then link against it.
Pass libsdtc++-(static)dev to LIBC_DEPENDENCIES allowing the
library to be present for cross compilation as well as
Signed-off-by: Khem Raj
---
.../ghostscript/powerpc64le/objarch.h | 40 +++
1 file changed, 40 insertions(+)
create mode 100644
meta/recipes-extended/ghostscript/ghostscript/powerpc64le/objarch.h
diff --git
a/meta/recipes-extended/ghostscript/ghostscript/powerpc64le/ob
This is same as PPC64 BE
Signed-off-by: Khem Raj
---
meta/recipes-devtools/tcf-agent/tcf-agent_git.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/tcf-agent/tcf-agent_git.bb
b/meta/recipes-devtools/tcf-agent/tcf-agent_git.bb
index b4bd4ca63c..e0a07a9375 100644
--- a
LE is default for modern powerpc64, power8+
PowerPC64 Little Endian Linux ABI specifies Power8 as the minimum ISA.
The basic ABI can run on earlier versions of the 64 bit PowerPC ISA,
but it was helpful to define a new, minimum instruction set for Linux
distribution releases during the switch to L
Signed-off-by: Khem Raj
---
meta/recipes-connectivity/openssl/openssl_1.1.1d.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1d.bb
b/meta/recipes-connectivity/openssl/openssl_1.1.1d.bb
index 458ae7daf4..7fd0f9a269 100644
--- a/meta/recipes-
Even though we do not expect any legacy ( 32bit ) for LE, linux-yocto
does enable the compat code, so enable 32bit support to get that going
Signed-off-by: Khem Raj
---
meta/recipes-devtools/gcc/gcc-common.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/gcc/gcc-comm
This patchset adds base support for building ppc64 in Litte-Endian mode,
the linux-yocto changes and qemu related changes will make it buildable
target out of box, but that is not yet made available
The following changes since commit ecbf203e34484731dcb6acc5e75df79cb86e55dc:
sstatesig: Improve
On Sat, 2020-01-18 at 11:13 +, Richard Purdie wrote:
> On Sat, 2020-01-18 at 12:08 +0100, Andreas Müller wrote:
> > On Sat, Jan 18, 2020 at 9:40 AM Richard Purdie
> > wrote:
> > > > V1 -> V2:
> > > > * Shelve global path export thingy
> > > > * Add me as maintainer of itstool (let's consider '
libfm installs mime types we want in our mime-database and it also uses desktop
files
containing MimeType.
Signed-off-by: Richard Purdie
---
meta/recipes-support/libfm/libfm_1.3.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-support/libfm/libfm_1.3.1.bb
b
On Fri, 2020-01-17 at 14:41 -0800, akuster808 wrote:
> I would like to thank you and Intel for taking up this task even
> thought
> the community seemed to have issues with Centos7 being dropped.
>
> Is there anything community can do at this point?
The work isn't complete, we have a proof of con
On Sat, 2020-01-18 at 12:08 +0100, Andreas Müller wrote:
> On Sat, Jan 18, 2020 at 9:40 AM Richard Purdie
> wrote:
> > > V1 -> V2:
> > > * Shelve global path export thingy
> > > * Add me as maintainer of itstool (let's consider 'ü' in my name
> > > as
> > > test case :)
> > > * Change "to to" to "
On Sat, Jan 18, 2020 at 9:40 AM Richard Purdie
wrote:
> >
> > V1 -> V2:
> > * Shelve global path export thingy
> > * Add me as maintainer of itstool (let's consider 'ü' in my name as
> > test case :)
> > * Change "to to" to "to" in commit message
> > * Build shared-mime-info from git to allow auto
On Fri, 2020-01-17 at 14:16 +, Ross Burton wrote:
> Python 2 ceased being maintained on the 1st January 2020. We've
> already
> removed all users of it from oe-core so the final step is to move the
> recipe and supporting classes to meta-python2.
>
> The following are removed in this commit:
On Fri, 2020-01-17 at 22:28 +0100, Andreas Müller wrote:
> On fresh images file-browsers do not know how to open files and
> usually open a
> dialog with ALL applications available on the machine. This is not
> what users
> are used to when working with linux: For just one application
> installed p
33 matches
Mail list logo
