Hi
Even if it does not cover all the use cases. Can we consider this patch?
Thanks!
On Sat, Apr 25, 2020 at 11:29 PM Ricardo Ribalda Delgado
wrote:
>
> Hi Christopher
>
> On Fri, Apr 24, 2020 at 5:56 PM Christopher Larson wrote:
> >
> > This will only work the way you expect if hte user's
> -Original Message-
> From: Andre McCurdy
> Sent: den 13 maj 2020 00:20
> To: Peter Kjellerstedt
> Cc: OE Core mailing list
> Subject: Re: [OE-core] [PATCH] file: Remove unneccessary override of
> PACKAGECONFIG for native
>
> On Tue, May 12, 2020 at 2:43 PM Peter Kjellerstedt
>
Hi Trevor,
It will be really helpful to me.But I don't have a Fedora system with me.
I have only Ubuntu System.
I am available on #oe IRC Channels.
*Thanks & Regards,*
Rahul Kumar
Software Engineer,Linux Solutions Engineering
Group,Montavista Software LLC
Email Id: rah...@mvista.com
From: Mark Hatle
Prior to fetching, the system checks if the sstate file is present
either locally or on the mirror. If it is, then it goes to the fetch
stage. Up to three files can be fetched, sstate, sstate.siginfo and
sstate.sig (if signature validation is enabled).
The previous
On Tue, 2020-05-12 at 23:37 +0300, Adrian Bunk wrote:
> Signed-off-by: Adrian Bunk
> ---
> .../recipes-devtools/apt/apt-native_1.2.31.bb | 4 +-
> ...nging-the-global-LC_TIME-for-Release.patch | 80 ---
> ...caled-std-put_time-instead-rolling-o.patch | 46 ---
>
On Wed, May 13, 2020 at 10:14 AM Peter Kjellerstedt
wrote:
>
> > -Original Message-
> > From: Andre McCurdy
> > Sent: den 13 maj 2020 00:20
> > To: Peter Kjellerstedt
> > Cc: OE Core mailing list
> > Subject: Re: [OE-core] [PATCH] file: Remove unneccessary override of
> > PACKAGECONFIG
On Mon, 2020-05-11 at 14:48 -0500, Joshua Watt wrote:
> Add support for an --offset argument when defining a partition. Many
> SoCs require that boot partitions be located at specific offsets.
> Prior
> to this argument, most WKS files were using the --align attribute to
> specify the location of
On Wed, May 13, 2020 at 05:30:13PM +0100, Richard Purdie wrote:
> On Tue, 2020-05-12 at 23:37 +0300, Adrian Bunk wrote:
> > Signed-off-by: Adrian Bunk
> > ---
> > .../recipes-devtools/apt/apt-native_1.2.31.bb | 4 +-
> > ...nging-the-global-LC_TIME-for-Release.patch | 80 ---
> >
On 2020/5/11 δΈε5:23, kai.k...@windriver.com wrote:
From: Kai Kang
It fails to build gcr if no commmand gpg on build host:
| meson.build:44:0: ERROR: Program(s) ['gpg2', 'gpg'] not found or not
executable
Add dependency gnupg-native to fix the error.
Signed-off-by: Kai Kang
---
Signed-off-by: Adrian Bunk
---
meta/recipes-devtools/apt/apt.inc | 1 +
...le-is-not-portable-use-std-locale-cl.patch | 27 +++
2 files changed, 28 insertions(+)
create mode 100644
On Wed, 2020-05-13 at 01:14 +, Naveen Saini wrote:
> Ping
Needs rebasing against master please as there were other libva changes
recently.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#138237):
On Wed, May 13, 2020 at 2:31 PM Richard Purdie
wrote:
> On Wed, 2020-05-13 at 12:30 -0700, Andre McCurdy wrote:
> > Yes. Unfortunately making recipes robust for users who want to change
> > PACKAGECONFIG values doesn't seem to be a high priority for oe-core.
> > Why else would default
On Wed, 2020-05-13 at 12:30 -0700, Andre McCurdy wrote:
> Yes. Unfortunately making recipes robust for users who want to change
> PACKAGECONFIG values doesn't seem to be a high priority for oe-core.
> Why else would default PACKAGECONFIG values be assigned with ??=
> instead of ?= other than as a
Hi Richard,
These patches apply on top of current master.
Regards,
Naveen
-Original Message-
From: Richard Purdie
Sent: Thursday, May 14, 2020 5:35 AM
To: Saini, Naveen Kumar ;
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/2] libva: upgrade 2.6.1 -> 2.7.1
libatomic has mind of its own when it comes to setting -march for arm64
which conflicts with -mcpu option we pass from environment in some cases
since we always pass -march/-mcpu in OE, its safe to remove this option
mcpu removal from cortex-a55 is no longer needed since the option
conflict is
mcpu is more appropriate on aarch64 and generates more optimized code
forr a given SOC, unlike -march/-mtune combination as decribed here [1]
[1]
https://community.arm.com/developer/tools-software/tools/b/tools-software-ides-blog/posts/compiler-flags-across-architectures-march-mtune-and-mcpu
Now that they uses -mcpu, its better to have tune specific build
directories, since aarch64 wont be appropriate any longer
Signed-off-by: Khem Raj
---
meta/conf/machine/include/tune-cortexa53.inc | 4
meta/conf/machine/include/tune-cortexa55.inc | 1 +
This is more appropriate for the machine we are emulating
Signed-off-by: Khem Raj
---
meta/conf/machine/qemuarm64.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/machine/qemuarm64.conf b/meta/conf/machine/qemuarm64.conf
index 1e2d4f018d..92da16888a 100644
---
Signed-off-by: Khem Raj
---
meta/conf/machine/include/tune-cortexa55.inc | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/meta/conf/machine/include/tune-cortexa55.inc
b/meta/conf/machine/include/tune-cortexa55.inc
index 8242cc9cef..89032b59ec 100644
---
Signed-off-by: Khem Raj
---
meta/conf/machine/include/tune-cortexa57.inc | 17 +
1 file changed, 17 insertions(+)
create mode 100644 meta/conf/machine/include/tune-cortexa57.inc
diff --git a/meta/conf/machine/include/tune-cortexa57.inc
== Series Details ==
Series: "tune-cortexa55.inc: crc and cr..." and 5 more
Revision: 1
URL : https://patchwork.openembedded.org/series/24139/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
Signed-off-by: Robert P. J. Day
---
diff --git a/meta/files/common-licenses/Unlicense
b/meta/files/common-licenses/Unlicense
new file mode 100644
index 00..68a49daad8
--- /dev/null
+++ b/meta/files/common-licenses/Unlicense
@@ -0,0 +1,24 @@
+This is free and unencumbered software
From: Changqing Li
since we use one variable VOLATILE_DIR to control the volatile,
rename the filename to make it common
Signed-off-by: Changqing Li
---
.../{fs-perms-persistent-log.txt => fs-perms-persistent.txt}| 2 --
1 file changed, 2 deletions(-)
rename
From: Changqing Li
respect VOLATILE_DIR to support persistent /var/tmp too
Signed-off-by: Changqing Li
---
meta/recipes-core/base-files/base-files_3.0.14.bb | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-core/base-files/base-files_3.0.14.bb
From: Changqing Li
respect VOLATILE_DIR to support persistent /var/tmp too
Signed-off-by: Changqing Li
---
meta/recipes-core/initscripts/initscripts-1.0/volatiles | 3 ---
meta/recipes-core/initscripts/initscripts_1.0.bb| 8 +++-
2 files changed, 7 insertions(+), 4 deletions(-)
From: Changqing Li
respect VOLATILE_DIR to support persistent /var/tmp too
Signed-off-by: Changqing Li
---
meta/recipes-core/systemd/systemd_245.5.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/systemd/systemd_245.5.bb
From: Changqing Li
To support persistent /var/tmp, rename VOLATILE_LOG_DIR
to VOLATILE_DIR
Don't use VOLATILE_LOG_DIR/VOLATILE_TMP_DIR
to control it separately since it will make things complicated,
we need to make kinds of fs-perms*.txt for kinds of combination
of the two variables.
From: Changqing Li
respect VOLATILE_DIR to support persistent /var/tmp too
Signed-off-by: Changqing Li
---
meta/recipes-core/udev/eudev_3.2.9.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-core/udev/eudev_3.2.9.bb
b/meta/recipes-core/udev/eudev_3.2.9.bb
index
From: Changqing Li
Changqing Li (6):
bitbake.conf: rename VOLATILE_LOG_DIR to VOLATILE_DIR
fs-perms-persistent.txt: renamed from fs-perms-persistent-log.txt
base-files: respect VOLATILE_DIR
initscripts: respect VOLATILE_DIR
systemd: respect VOLATILE_DIR
eudev: respect VOLATILE_DIR
From: Mark Hatle
Prior to fetching, the system checks if the sstate file is present
either locally or on the mirror. If it is, then it goes to the fetch
stage. Up to three files can be fetched, sstate, sstate.siginfo and
sstate.sig (if signature validation is enabled).
The previous
Patch 1 is a backport from master (it's already in Dunfell). If you have a
locked-sigs file, and the sstate for that item isn't available the .siginfo and
sigdata files were not being written. Patch 1/2 resolved that with the
fragment in "dump_sigtask".
Patch 2 was sent for master as well, and
From: Mark Hatle
Prior to fetching, the system checks if the sstate file is present
either locally or on the mirror. If it is, then it goes to the fetch
stage. Up to three files can be fetched, sstate, sstate.siginfo and
sstate.sig (if signature validation is enabled).
The previous
From: Richard Purdie
With hashequiv the get_taskhash function is called much more regularly
and contains expensive operations. This these don't change based upon
hash in a given build, improve the caching within the function to
reduce overhead.
(From OE-Core rev:
From: Bruce Ashfield
The routine to get the timestamp of the kernel commits should
specify LC_ALL to ensure consistent behaviour. We were making
a copy of the env, adding the setting .. and then not using it
on the call.
We specifiy the env in the subprocess call to ensure the
variable is
== Series Details ==
Series: kernel/reproducibility: use specified environment settings
Revision: 1
URL : https://patchwork.openembedded.org/series/24133/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
9895e0ac338a Linux 5.4.38
5a54c69c4ef8 Revert "ASoC: meson: axg-card: fix codec-to-codec link setup"
527c60e8b7a8 Linux 5.4.37
4e7fb753e803 ASoC: stm32:
From: Bruce Ashfield
Rather than duplicating the code to generate the kbuild environment
variable: KBUILD_BUILD_TIMESTAMP, we can factor the checks into a
python function and call it from the main image and kernel module
do_compile routines.
All paths have been checked and the timestamp is
From: Bruce Ashfield
Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:
f015b86259a5 Linux 5.4.40
2852b559afdf PM / devfreq: Add missing locking while setting suspend_freq
8e054bd6dfc4 udp: document udp_rcv_segment special case for
From: Bruce Ashfield
Hi all,
This is a resend of the v5.4 stable bump to v5.4.38, plus a new -stable
bump to v5.4.40.
The extra changes to make these pass the AB tests are the kernel
reproducibility commits.
The issue we had on the last submission was that IKHEADERS was switched
to a module,
From: Bruce Ashfield
If CONFIG_IKHEADERS is set to =m, then reproducibility issues creep
into the modules build, since the variables we are setting for the
main kernel build are not present.
Since the source code must be available for a possibly git query
on the timestamp, there didn't seem to
This includes the fixes for CVE-2020-5260 and CVE-2020-11008.
Signed-off-by: Adrian Bunk
---
meta/recipes-devtools/git/git_2.24.1.bb | 11 ---
meta/recipes-devtools/git/git_2.24.3.bb | 9 +
2 files changed, 9 insertions(+), 11 deletions(-)
delete mode 100644
On Wed, May 13, 2020 at 10:24 AM wrote:
>
> From: Bruce Ashfield
>
> Rather than duplicating the code to generate the kbuild environment
> variable: KBUILD_BUILD_TIMESTAMP, we can factor the checks into a
> python function and call it from the main image and kernel module
> do_compile routines.
This includes the fixes for CVE-2020-5260 and CVE-2020-11008.
Signed-off-by: Adrian Bunk
---
meta/recipes-devtools/git/git_2.20.1.bb | 11 ---
meta/recipes-devtools/git/git_2.20.4.bb | 11 +++
2 files changed, 11 insertions(+), 11 deletions(-)
delete mode 100644
On 5/12/20 7:22 PM, Randy MacLeod wrote:
On 2020-05-12 12:58 a.m., Rahul Kumar wrote:
Hi,
Can any one please help me to figure out how to deal with the GPLv3+
issue.
you can see my Patch at below link
https://patchwork.openembedded.org/patch/172134/
*Issue:*
the new license (GPLv3) causes
44 matches
Mail list logo