u-boot mainline supports menuconfig and is slowing moving drivers to be enabled
using menuconfig. This patch enables menuconfig for u-boot using cml1.
However using menuconfig in conjuntion with UBOOT_CONFIG cannot happen.
When you run menuconfig it is against a particular defconfig, while using
U
From: Alexander Kanavin
Instead, first check if we need to do anything at all during first boot,
and if so, either postpone to first boot via pkg_postinst_ontarget()
when running on host, or run the necessary setup code when running on target.
(From OE-Core rev: 16df1717c3813ba773e0dfa2d1db47181
Dear Alex,
> The patch should go to meta-openembedded list, and it should be created
> against the layer source tree, not against the component source
> tree.
Thank you for all your kindness.
I have created a patch for meta-networking/recipes-netkit/netkit-telnet.
Please refer to the attached pa
On 05/29/2018 09:39 AM, Robert Yang wrote:
On 05/29/2018 01:14 AM, Randy MacLeod wrote:
On 05/24/2018 10:48 PM, Robert Yang wrote:
Usually, the debugfs' (-dbg.tar.*) work follow is:
s/work follow/workflow/
1) Install regular rootfs to dir_foo
2) Install debugfs (-dbg.tar.*) to the same di
On 05/29/2018 01:14 AM, Randy MacLeod wrote:
On 05/24/2018 10:48 PM, Robert Yang wrote:
Usually, the debugfs' (-dbg.tar.*) work follow is:
s/work follow/workflow/
1) Install regular rootfs to dir_foo
2) Install debugfs (-dbg.tar.*) to the same dir_foo
So we need allow install debugfs on roo
From: Böszörményi Zoltán
npm cache clear throws an error with npm@5 and suggests to
use npm cache verify instead. But our cache is actually empty,
so use npm cache clear --force.
npm install in the source directory creates symlinks with npm@5.
Use a combination of npm pack and npm install modul
> Am 28.05.2018 um 21:12 schrieb Alexander Kanavin :
>
> 2018-05-28 21:41 GMT+03:00 Jens Rehsack :
>> When I log into my build machine, I just do
>>
>> $ oe_builddir use ~/gpw-community-bsp/gpw-yocto-platform/
>>
>> and I'm in the right location and have all environment settings prepared to
>
2018-05-28 21:41 GMT+03:00 Jens Rehsack :
> When I log into my build machine, I just do
>
> $ oe_builddir use ~/gpw-community-bsp/gpw-yocto-platform/
>
> and I'm in the right location and have all environment settings prepared to
> start a bitbake immediately.
oe-init-build-env does the same thin
The modern the time, the improvements in ExtUtils::MakeMaker.
Nowadays, .packlist and perllocal.pod aren't touched anymore when appropriate
flags set during configure stage. Controlling the flags globally avoids
dual-life recipes need share patching.
Further: remove prepending ${PERL_ARCHLIB} in
Jens Rehsack (2):
cpan_build.bbclass: adopt to recent EU::MM
cpan_build.bbclass: tell Module::Build the replacement
meta/classes/cpan.bbclass | 3 +--
meta/classes/cpan_build.bbclass | 2 +-
2 files changed, 2 insertions(+), 3 deletions(-)
--
Jens Rehsack - rehs...@gmail.com
signatur
Instead of patching Module::Build, maybe Module::Build::Tiny and all other
similar tools, use the official way to tell them which is the target perl
on target.
Signed-off-by: Jens Rehsack
---
meta/classes/cpan_build.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta
> Am 21.05.2018 um 21:04 schrieb Alexander Kanavin
> :
>
> On 05/21/2018 06:55 PM, Jens Rehsack wrote:
>> Move scripts/bashrc from meta-jens/scripts to oe-core to share user-friendly
>> oe builddir management with community. Using this script will help manage
>> multiple BSPs and targets like p
On 05/24/2018 10:48 PM, Robert Yang wrote:
Usually, the debugfs' (-dbg.tar.*) work follow is:
s/work follow/workflow/
1) Install regular rootfs to dir_foo
2) Install debugfs (-dbg.tar.*) to the same dir_foo
So we need allow install debugfs on rootfs.
So we need to allow installing the debugfs
Definitely, once the RDEPENDS is there, people will forget about it and it
will still be there long after we've forgotten why it was put there...
On 18-05-18 15:20, Burton, Ross wrote:
Fixing busybox is a better solution. yes.
Ross
On 18 May 2018 at 13:24, Fabio Berton wrote:
Yes, I tested
Signed-off-by: Khem Raj
---
...patible-basename-for-non-glibc-syste.patch | 33 +++
meta/recipes-core/systemd/systemd_237.bb | 1 +
2 files changed, 34 insertions(+)
create mode 100644
meta/recipes-core/systemd/systemd/0035-Define-glibc-compatible-basename-for-non-glibc-sy
Signed-off-by: Khem Raj
---
...ange-the-default-device-timeout-to-2.patch | 9 +-
...ation-compile-failure-by-typecasting.patch | 173 ++
meta/recipes-core/systemd/systemd_237.bb | 1 +
3 files changed, 177 insertions(+), 6 deletions(-)
create mode 100644
meta/recipes-c
Bring in an important fix
https://bugzilla.redhat.com/show_bug.cgi?id=1559181
Signed-off-by: Khem Raj
---
meta/recipes-extended/rpcsvc-proto/rpcsvc-proto.bb | 4 ++--
.../0001-Use-cross-compiled-rpcgen.patch| 13 +
2 files changed, 7 insertions(+), 10 deletions(-)
diff
On Sat, May 26, 2018 at 08:22:39AM -0400, Damien Riegel wrote:
> Hi,
>
>
> When generating the extended SDK, my setup fails with the following
> error:
>
> ERROR: Failed to generate filtered task list for extensible SDK:
> ERROR: bitbake failed:
> ERROR: Unable to start bitbake server
>
On 05/22/2018 06:19 PM, Andre McCurdy wrote:
> On Tue, May 22, 2018 at 5:48 PM, Randy MacLeod
> wrote:
>> On 05/22/2018 07:06 PM, Andre McCurdy wrote:
>> ...
>>> Building before and after Armin's patch and then diffing .config files
>>> in each build directory gives:
>>>
>> I didn't know what al
On 05/23/2018 04:01 AM, Burton, Ross wrote:
> This is breaking a number of other bits of X:
>
> - xf86-video-intel (was DRI1 removed or disabled in 1.20?)
> - xf86-input-mouse
> - xf86-video-omapfb
hmm, will double check
- armin
> Ross
>
> On 19 May 2018 at 03:13, Armin Kuster wrote:
>> From:
On 05/25/2018 12:16 PM, Andre McCurdy wrote:
> Apparently there are recipes in the wild which generate files with
> filenames containing '$' characters - which cause errors during
> packaging.
>
> Instead of adding another special case to escape '$' characters when
> constructing the command pass
[v3]
Made formating and spelling changes per Martin
[v2]
Remove python3 in default PACKACKECONFIG
include https://patchwork.openembedded.org/patch/148257/
Because of the newly added dependency on meta-python, the python(3)
packageconfig is no longer "default-on".
Signed-off-by: Martin Hundebøll
On Monday, May 28, 2018 9:52:16 AM EDT Alexander Kanavin wrote:
> (don't forget devtool also has 'edit/find/update-recipe' commands).
Since it keys off the FILE and BBINCLUDED as parsed it follows along with the
devtool workspaces just fine. There should be no confusion added and if
anything see
(don't forget devtool also has 'edit/find/update-recipe' commands).
Alex
2018-05-28 16:50 GMT+03:00 Alexander Kanavin :
> 2018-05-28 16:38 GMT+03:00 Mark Asselstine :
>> This is a new class which can be used (for example via USER_CLASSES in
>> local.conf) to make your build more development frien
2018-05-28 16:38 GMT+03:00 Mark Asselstine :
> This is a new class which can be used (for example via USER_CLASSES in
> local.conf) to make your build more development friendly. When
> included this class will create symlinks to the various bb and
> bbappend files in WORKDIR.
I do think this is a
This is a new class which can be used (for example via USER_CLASSES in
local.conf) to make your build more development friendly. When
included this class will create symlinks to the various bb and
bbappend files in WORKDIR.
Normally when you are debugging or extending a package's recipe files
a de
On Mon, 2018-05-28 at 11:55 +0300, Hannu Lounento wrote:
> On 25/05/18 18:34, Christopher Larson wrote:
> > We should probably investigate if it's possible to shift those into
> > do_fetch eventually. Contacting upstream during do_configure is not
> > kosher.
>
> The reason for fetching during co
On 25/05/18 18:34, Christopher Larson wrote:
We should probably investigate if it's possible to shift those into
do_fetch eventually. Contacting upstream during do_configure is not kosher.
The reason for fetching during configure is that the CMake build system
in the git repository in question
The variants are needed in particular when executing postinst_intercepts as
those may require running binaries built for different architectures and
against different sets of library paths, when multilib is in use (or nativesdk
host
packages are installed), so a single global variant of the script
Previously only one global variant of the script was created,
which caused numerous issues:
1) multilib was not properly supported due to multilib variants each
needing their own version of the qemu binary and library paths to be set
2) nativesdk was not properly supported for the same reason
Thi
Previously a warning was printed regardless of context and nature
of the failure, and because it was only a warning, it was mostly ignored.
Now, the following is considered when a failure happens:
1) whether we are installing packages into a target image, or populating
a SDK with host or target pa
Otherwise, there would be a failure at image creation time; avoid
that by postponing to first boot explicitly.
Signed-off-by: Alexander Kanavin
---
meta/recipes-core/systemd/systemd_237.bb | 10 +++---
meta/recipes-core/udev/eudev_3.2.5.bb| 8 ++--
2 files changed, 13 insertions(+),
Sumo release provides a transition period so that deferrals to first boot
via 'exit 1' can be converted to pkg_postinst_ontarget(). For the next release
however, postinst script failures should be treated as such.
[YOCTO #12607]
Signed-off-by: Alexander Kanavin
---
meta/lib/oe/package_manager.p
This has the following benefits:
- consistent with how the other caches are created into target rootfs
- only runs once per package manager transaction, instead of once per every
immodule package
- correctly postpones to first boot if qemu is not working; from postinst itself
this would've require
This was undocumented, and it's better to just always enable
full debug output, as this allows immediate generation of logs
with full diagnostics when things go not as expected.
Also, change the output of dnf from note to debug level; this
does not affect what is written to log file, but does redu
On 05/28/2018 09:27 AM, Seiichi Ishitsuka wrote:
I was able to reproduce the old problems shown below with netkit-telnet_0.17.bb.
https://patchwork.openembedded.org/patch/96727/
https://bugs.launchpad.net/ubuntu/+source/netkit-telnet/+bug/507455
The patch should go to meta-openembedded list, a
36 matches
Mail list logo
