This patch series provides support for the user to run menuconfig command in
the
devtool flow. This would allow the user to modify the current configurations
and
generate a config fragment to update the recipe using devtool finish. Devtool
menuconfig command will work on all packages that conta
In the regular devtool modify flow, the kernel source is fetched by running
do_fetch task. This is an overhead in time and space.
This patch updates modify command to check if the kernel source is already
downloaded. If so, then instead of calling do_fetch, copy the source
from work-shared to devt
If a SRC_URI content ends with '.patch' bitbake is
trying to apply it as it's a patch file.
It causes that if we use git repository for 'patch' package
the bare clone is extracted to a directory
(i.e. build/downloads/git2/git.mirror.org.patch/) which is considered
to be a patch file, so patch.py t
If we add patch git repository to SRC_URI (e.g.
https://github.com/mirror/patch (without the .git suffix) or a local
repository /tmp/patch) the bare clone will go to
downloads/git2/github.com.patch or downloads/git2/tmp.patch and
because the directory ends with '.patch' the do_patch task will assum
Changes the default PACKAGE_DEBUG_SPLIT_STYLE to generate separate
source and debug packages. SDKIMAGE_FEATURES is updated to include the
source packages so that there is not change for the SDK contents.
[YOCTO #12931]
Signed-off-by: Joshua Watt
---
meta/classes/populate_sdk_base.bbclass | 2 +
On 1/24/19 9:22 PM, Khem Raj wrote:
> On Wed, Jan 23, 2019 at 6:11 PM Andre McCurdy wrote:
>>
>> On Wed, Jan 23, 2019 at 2:50 PM Khem Raj wrote:
>>>
>>> On Wed, Jan 23, 2019 at 5:27 PM Andre McCurdy wrote:
On Wed, Jan 23, 2019 at 12:05 PM Khem Raj wrote:
>
> tune files which i
On 1/24/19 9:35 PM, Khem Raj wrote:
> Hi Mark
> On Thu, Jan 24, 2019 at 12:09 PM Mark Hatle wrote:
>>
>> On 1/23/19 6:18 PM, Khem Raj wrote:
>>> tune files which inherit the arch definitions already define appropriate
>>> -mcpu option, which is equivalent of right -march and -mtune combination
>>>
On Fri, 25 Jan 2019 at 17:33, Joshua Watt wrote:
> I probably should have been a little more specific: I was thinking that
> POSTINST_INTERCEPT_${PN} = "0" would prevent the creation of the
> scripts at packaging time, not try and suppress them at rootfs creation
> time. The idea would be to add
Changes to pkg_postinst_ontarget were not triggering rebuilds, this fixes
that.
[YOCTO #13127]
Signed-off-by: Richard Purdie
---
meta/classes/package.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index 853
On Fri, 2019-01-25 at 17:10 +0100, Alexander Kanavin wrote:
> On Fri, 25 Jan 2019 at 16:38, Richard Purdie
> wrote:
> > > > There is a similar issue in multilib for target packages (a
> > > > warning
> > > > because qemu usermode support is missing):
> > > > https://autobuilder.yoctoproject.org/ty
As a further example of this I wanted to experiment with a real world
example. We have:
https://autobuilder.yocto.io/pub/releases/yocto-2.6.1.rc1/testresults/qemux86/testresults.json
https://autobuilder.yocto.io/pub/releases/yocto-2.7_M1.rc1/testresults/qemux86/testresults.json
https://autobuilder
On Fri, 25 Jan 2019 at 16:38, Richard Purdie
wrote:
> > > There is a similar issue in multilib for target packages (a warning
> > > because qemu usermode support is missing):
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/214/steps/7/logs/warnings
> > >
> > > I'm as well n
On Tue, 2019-01-22 at 17:42 +0800, Yeoh Ee Peng wrote:
> OEQA outputs test results into json files and these files were
> archived by Autobuilder during QA releases. Example: each oe-selftest
> run by Autobuilder for different host distro generate a
> testresults.json file.
>
> These scripts were
On Fri, 2019-01-25 at 09:37 -0600, Joshua Watt wrote:
> On Fri, 2019-01-25 at 13:13 +0100, Alexander Kanavin wrote:
> > There is a similar issue in multilib for target packages (a warning
> > because qemu usermode support is missing):
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/44/b
On Fri, 2019-01-25 at 13:13 +0100, Alexander Kanavin wrote:
> There is a similar issue in multilib for target packages (a warning
> because qemu usermode support is missing):
> https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/214/steps/7/logs/warnings
>
> I'm as well not sure how
On Thu, 2019-01-24 at 15:02 -0600, Joshua Watt wrote:
> Changes the default PACKAGE_DEBUG_SPLIT_STYLE to generate separate
> source and debug packages. SDKIMAGE_FEATURES is updated to include
> the
> source packages so that there is not change for the SDK contents.
>
> [YOCTO #12931]
>
> Signed-o
The warnings deal with two specific cases of failure:
1) unable to execute nativesdk postinsts for mingw SDKs because
they need to be run under wine
2) unable to execute target postinsts when there is no qemu
usermode support for the target
Neither of these should be a big problem as mingw issue w
There is a similar issue in multilib for target packages (a warning
because qemu usermode support is missing):
https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/214/steps/7/logs/warnings
I'm as well not sure how to handle this:
1. Keep these two warnings as warnings so users see th
How is this not appropriate for upstream?
Ross
On Fri, 25 Jan 2019 at 11:40, C.r. Guo wrote:
>
> From: Chunrong Guo
>
> Signed-off-by: Chunrong Guo
> ---
> .../mozjs/mozjs/0001-add-aarch64-be-support.patch | 28
> ++
> meta-oe/recipes-extended/mozjs/mozjs_52.9.1.bb |
From: Chunrong Guo
Signed-off-by: Chunrong Guo
---
.../mozjs/mozjs/0001-add-aarch64-be-support.patch | 28 ++
meta-oe/recipes-extended/mozjs/mozjs_52.9.1.bb | 1 +
2 files changed, 29 insertions(+)
create mode 100644
meta-oe/recipes-extended/mozjs/mozjs/0001-add-aarc
20 matches
Mail list logo
