On Thu, 21 Nov 2019 at 22:18, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> We got so far and after looking at the position we ended up I decided
> it was easier to switch poky-altcfg rather than change poky and/or OE
> defaults. I resolved that bug as "complete" as we now had
I would have the following requirements for any provider you choose:
1. Having kvm enabled (for the purpose of running qemu tests in the cloud
with good performance)
2. NFS server as a service from the cloud provider (so you don't have to
set it up and maintain it yourself)
3. Ability to share
Thanks, patch applied and pushed.
Alex
On Mon, 21 Oct 2019 at 14:46, Yann CARDAILLAC
wrote:
> Hi guys,
>
> I'm working on bug :
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13531
>
> I've add GPLV2-or-later to all the sources, is there any modification you
> want to add?
>
> Best
Bash is only needed by one not particularly important script,
so not requiring bash is a useful option for builds that
cannot have gpl3 components.
Signed-off-by: Alexander Kanavin
---
recipes-mac/AppArmor/apparmor_2.13.3.bb | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff
/packages-split/apparmor/usr/lib/python3.7/site-packages/LibAppArmor/_LibAppArmor.cpython-37m-i686-linux-gnu.so)
Signed-off-by: Alexander Kanavin
---
recipes-mac/AppArmor/apparmor_2.13.3.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/recipes-mac/AppArmor/apparmor_2.13.3.bb
b/recipes-mac
On Tue, 1 Oct 2019 at 16:54, Stephen K Jolley
wrote:
> A significant performance problem has been found on the autobuilder where
> some builds are scaling in time badly as the sstate cache grows, taking 12
> hours or more in some cases. Unfortunately nobody seems motivated to help
> work on this
On Wed, 4 Sep 2019 at 10:53, vygu wrote:
> Just to signal there are several mistakes with the recipe "perf.bb" from
> poky on master (currently: e2bde009b325b40641407ecf50f54ed8c41726d6)
>
> - If "Python 3 is not yet supported" by "perf" sources, it causes an issue
> during the do_compile task
>
On Mon, 2 Sep 2019 at 16:06, sateesh m wrote:
> Sure, sir. If you don't mine can you please share where this log file will
> present.
> I am seeing /tmp-glibc/work/riscv-oe-linux/ptest-runner/2.3.4.../temp/
> I am seeing here but log.do_rootfs file is not Present here.
>
> Can you please tell me
On Mon, 2 Sep 2019 at 15:06, sateesh m wrote:
> I followed the wiki https://wiki.yoctoproject.org/wiki/Ptest , but when I
> boot to my image and run ptest-runner I have the output : "No ptests found."
> Is this normal ? I thought that
>
> DISTRO_FEATURES_append = " ptest"
> and
>
On Mon, 2 Sep 2019 at 15:05, Brian Silverman wrote:
> The tags chosen above are based on what we test and ship. So my issue is
> that someone has to correctly follow the above instructions for different
> versions of multiple layers if they want a reproducible build of a specific
> version of
On Wed, 21 Aug 2019 at 11:00, Bert Böhne wrote:
> thanks for your reply. Do I need the plugins for writing and debugging
> code in Eclipse? The documentation says:
>
>
>
> 24.9.11. ADT Removed¶
>
>
>
> The Application Development Toolkit (ADT) has been removed because its
> functionality almost
On Tue, 20 Aug 2019 at 17:34, Bert Böhne wrote:
> I am using Yocto 2.7 and I want to use the SDK to build applications(or
> give the SDK to my colleagues to let them build applications). I have read
> in the documentation that there are plugins for Eclipse. But for Yocto
> 2.7(or maybe earlier)
On Mon, 19 Aug 2019 at 11:38, wrote:
> some of our colleagues would like to join the yocto after the linux
> embedded. Unfortuntely I can’t find any website or link where a ticket
> purchasing is possible. Is it possible to receive any information on the
> purchasing process and when it will
On Tue, 13 Aug 2019 at 12:41, Martin Siegumfeldt wrote:
> The link above is not about eSDK, it's about devtool which works perfectly
> fine in a non-SDK environment (e.g. plain yocto).
>
> Hmm, since it is a subsection beneath 'Using the Extensible SDK' I was
> expecting the list to describe
On Tue, 13 Aug 2019 at 10:40, Martin Siegumfeldt wrote:
> I am wondering if/when Meson is expected supported through the eSDK - I
> don't see it from the list:
>
> https://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-a-closer-look-at-devtool-add
> ?
>
The link above is not
This will enable standardizing qemu machines to '-vga std' emulated
hardware (as opposed to the current mix of vmware or cirrus cards,
both outdated).
See https://bugzilla.yoctoproject.org/show_bug.cgi?id=13466 for details.
Signed-off-by: Alexander Kanavin
---
bsp/common-pc-64/common-pc-64.scc
On Thu, 8 Aug 2019 at 10:57, JH wrote:
> Hi Alex, thanks for your response and kind help. I finally fixed it by
> adding a do_package_qa() in my bb file. What will be the consequence
> about it?
>
The consequences are that you have removed all of the standard quality
checks on your recipe, so
On Tue, 6 Aug 2019 at 03:53, wrote:
> Wiki: https://www.yoctoproject.org/public-virtual-meetings/
>
That page links a Google calendar, and the calendar is in many ways
mismatching what is listed on the page. Can you please re-create the
calendar?
Alex
--
every easy in the
> document to disable it, but it did not give any clues -:(.
>
> Thank you.
>
> Kind regards,
>
> - jh
> On 8/6/19, Alexander Kanavin wrote:
> > It may help if you copy-paste the exact error you are getting, and the
> > content of the directory wh
It may help if you copy-paste the exact error you are getting, and the
content of the directory where it happens.
Alex
On Tue, 6 Aug 2019 at 13:09, JH wrote:
> On 8/6/19, Alexander Kanavin wrote:
> > You don't; package_qa is reporting real issues with your packaging, so
>
You don't; package_qa is reporting real issues with your packaging, so you
need to address them.
Alex
On Tue, 6 Aug 2019 at 10:40, JH wrote:
> Hi,
>
> According to the latest document:
>
> "Package QA checks are now performed during a new do_package_qa task
> rather than being part of the
Awesome, thanks!
Alex
On Wed, 31 Jul 2019 at 17:04, Alex J Lennon
wrote:
>
> On 18/06/2019 11:58, Alexander Kanavin wrote:
> > Ping #2!
> >
> > Alex
>
>
> Apologies for the long delay! The patch is in finally...
>
>
>
--
__
Pulling down things from the network in do_install() is not the best
option. Is reproducibility and integrity of such downloads guaranteed? What
about the component licensing, where is that checked (against upstream
changes)? Also, yocto's download caching and mirroring facility is
side-stepped
On Tue, 23 Jul 2019 at 20:49, wrote:
>
>- There are patches available which enable runqueue optimisations
>based on output comparisons of tasks. This removes the need to run later
>tasks if the output is unchanged and is based upon the previous hash
>equivalence server work. This
I don’t really know what’s the situation with meta-mono specifically, but if
you’re willing to be the maintainer, that’d be great. Do keep in mind that
yocto is almost entirely a volunteer project, contributors and maintainers come
and go without long term promises.
Alex
> On 18 Jul 2019, at
Ping #2!
Alex
On Mon, 27 May 2019 at 12:22, Alex J Lennon
wrote:
>
> Thanks for the reminder Alex
> On 27/05/2019 11:16, Alexander Kanavin wrote:
>
> Ping?
>
> Alex
>
> On Mon, 13 May 2019 at 18:25, Alexander Kanavin
> wrote:
>
> When build directory
Should be ${D}, not ${B} in do_install.
Alex
On Fri, 14 Jun 2019 at 15:53, Larry Brown wrote:
> I've created a recipe that simply copies files into a folder of the
> image. Basically in this form:
>
> --
>
> SUMMARY = "Some text"
> HOMEPAGE
On Wed, 12 Jun 2019 at 09:54, Yi Zhao wrote:
> +PACKAGECONFIG[selinux] =
> "-Dselinux=enabled,-Dselinux=disabled,libselinux,"
>
This line should probably go into the oe-core recipe? It is fine to have
options that depend on things absent in oe-core, as long as those options
are disabled by
On Tue, 4 Jun 2019 at 17:12, Quentin Schulz <
quentin.sch...@streamunlimited.com> wrote:
> Why do we filter INCOMPATIBLE_LICENSE to have only SPDX licenses or
> their aliases (my understanding of respectively SRC_DISTRIBUTE_LICENSES
> and SPDXLICENSEMAP)?
> Is this actually expected?
>
> If it
y, compiling tizonia on Ubuntu) works fine, there
> it can find the soundcloud module. I just don't understand where autotools
> (during bitbake) is looking for the soundcloud module and what I have to do
> to make it work.
>
> Cheers,
> Serkan
>
> On Thu, May 30, 2019 at
This is really an autotools question, not a yocto question. Specifically,
what happens at this point?
*| checking python module: soundcloud... no*
Quite likely, the autotools script runs native python and asks it to import
soundcloud, which fails. You need a different approach, maybe checking for
Ping?
Alex
On Mon, 13 May 2019 at 18:25, Alexander Kanavin wrote:
>
> When build directory is deeply nested, the shebang limit of 127
> characters is hit, which leads to doltlibtool failing to execute.
>
> Signed-off-by: Alexander Kanavin
> ---
> recipes-mono/mono/mono-5
On Thu, 23 May 2019 at 02:22, Scott Rifenbark wrote:
> * In dev-manual's "Using the Auto Upgrade Helper (AUH)" section -
> https://www.yoctoproject.org/docs/2.7/mega-manual/mega-manual.html#gs-using-the-auto-upgrade-helper:
> Step 5 talks about making configurations in the local.conf file.
Yes - your distro configuration file is the correct place to do it.
Alex
On Wed, 22 May 2019 at 07:12, Pandey, Kamal wrote:
>
> Hi,
>
> I want to know if there is any other place where we can set configuration for
> a particular layer, apart from local.conf. For example if I want to set
>
I think Jean-Marie might be able to help as he recently did a bit of NPM fixing?
Alex
On Tue, 21 May 2019 at 19:52, Scott Rifenbark wrote:
>
> Hi,
>
> I am trying to determine if the information in
> https://wiki.yoctoproject.org/wiki/TipsAndTricks/NPM is relevant and
> up-to-date for
Marek wrote:
>
> On Tue, May 21, 2019 at 12:14 PM Alexander Kanavin
> wrote:
>>
>> You can write a class which sets the template for SRC_URI and then a
>> series of recipes that inherit the class, and define the variable that
>> would turn the template into the a
You can write a class which sets the template for SRC_URI and then a
series of recipes that inherit the class, and define the variable that
would turn the template into the actual URI.
Alex
On Tue, 21 May 2019 at 12:10, Belisko Marek wrote:
>
> Hi,
>
> On Tue, May 21, 2019 at 12:00
If you provide some context for why you want this, we might be able to
suggest a different way.
Alex
On Tue, 21 May 2019 at 08:11, Belisko Marek wrote:
>
> Hi,
>
> I have special need to fetch repo which is defined in config file in form
> (repo and branch):
> g...@testrepo.com/myrepo
Otherwise, if bitbake fails, there will be tracebacks later on.
Signed-off-by: Alexander Kanavin
---
modules/steps.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/modules/steps.py b/modules/steps.py
index 2eb4499..87d7584 100644
--- a/modules/steps.py
+++ b/modules
Basically if you make a patch for the numpy recipe to address this,
and post it to oe-core list, everyone would appreciate :)
Alex
On Tue, 14 May 2019 at 20:16, Aaron Cohen wrote:
>
> Is there a place I should post this that would get more attention?
>
> On Thu, May 9, 2019 at 4:48 PM Aaron
How does your image recipe look like? Also, log.do_rootfs can provide
a hint about what got installed into the image (you will find it in
the image build directory).
Alex
On Tue, 14 May 2019 at 11:42, Pandey, Kamal wrote:
>
> Hi
> I was trying to add ntp package to my image, I used the
You probably need to add a dependency on glib-2.0 to your recipe, then
the needed pkgconfig will be in the target sysroot.
If you can copy-paste the entire recipe, that would help.
Alex
On Tue, 14 May 2019 at 11:06, Tong Chen wrote:
>
> Hi all:
> I'm adding some kernel extensions to poky. In
When build directory is deeply nested, the shebang limit of 127
characters is hit, which leads to doltlibtool failing to execute.
Signed-off-by: Alexander Kanavin
---
recipes-mono/mono/mono-5.xx.inc | 4
1 file changed, 4 insertions(+)
diff --git a/recipes-mono/mono/mono-5.xx.inc b
Tarballs from archive.ubuntu.com can and do disappear (similar to
archive.debian.org).
Signed-off-by: Alexander Kanavin
---
recipes-mac/AppArmor/apparmor_2.13.2.bb | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/recipes-mac/AppArmor/apparmor_2.13.2.bb
b/recipes-mac
SSTATE_DIR and DL_DIR can (and should) be shared between all builds.
Each MACHINE/DISTRO combination works best with it's own build_dir.
Alex
On Thu, 9 May 2019 at 11:47, Fabian Knapp wrote:
>
> Hello,
>
> we have multiple MACHINEs and DISTROs and Im wondering for which
> combinations I have
Nevertheless, you are welcome to resurrect the plugin, if you are
willing to do the maintenance work. Yocto is what you make it.
Alex
On Wed, 8 May 2019 at 15:37, Zoran Stojsavljevic
wrote:
>
> https://marc.info/?l=openembedded-core=155482339222316=2
>
> (do not shoot the messenger, thank you)
You need to use vardepsexclude (read in the bitbake manual how to).
Generally I am not a fan of putting timestamps into anything
yocto-built, it's prone to issues like this, breaks reproducibility,
and also subverts sstate if not managed carefully. I'd almost suggest
you build the image with a
Most likely neither of these recipes actually provides a package named
'dhcp' or 'avahi'. Run 'bitbake -e avahi' and look for the PACKAGES
variable in the output, that would tell you the actual package names
that you can add to the image.
Alex
On Tue, 9 Apr 2019 at 16:16, Pandey, Kamal wrote:
>
On Tue, 2 Apr 2019 at 20:33, wrote:
> > [15] Bug 13257 - [2.7 M3 rc1] python3 ptest facing timeout issue
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13257
>
> I'm hoping a patch from Ross in master fixes this, need to retest ptest
> with this applied.
Sadly I have narrowed this down to
-buffered
one, and so ptest-runner will get the lines as soon as they are
written.
Signed-off-by: Alexander Kanavin
---
utils.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/utils.c b/utils.c
index 504df0b..1376e39 100644
--- a/utils.c
+++ b/utils.c
@@ -243,16 +243,13
Bah, sorry, debugging got into the patch.
Will resend.
Alex
On Thu, 4 Apr 2019 at 17:34, Alexander Kanavin wrote:
>
> As ptest-runner communicates with child processes via pipe2(),
> the corresponding channels are not attached to a pty. In that
> situation stdio facilities
-buffered
one, and so ptest-runner will get the lines as soon as they are
written.
Signed-off-by: Alexander Kanavin
---
utils.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/utils.c b/utils.c
index 504df0b..c130fbd 100644
--- a/utils.c
+++ b/utils.c
@@ -243,16
On Thu, 4 Apr 2019 at 02:39, Khem Raj wrote:
> Definitely, and I agree that we should put relevant information in
> commits, usually
> the information about side effects if any, links to changelog etc. are
> useful too
> however, we should not enforce a behavior which could result in
> redundancy
Just to make clear, the AUH workflow does require the maintainer to
sign off and edit a commit message via 'git commit -s --reset-author
--amend' for every commit, so AUH does not get in the way of useful
commit messages.
Alex
On Wed, 3 Apr 2019 at 12:31, Burton, Ross wrote:
>
> On Tue, 2 Apr
the poky distro is the base distro for the image
> this is inherited. Therefore it needs to be removed with the
> DISTRO_FEATURES_remove unless there is another way,
> which I'm not aware to easily remove/adjust without having
> to create a new distro.
>
> Regards,
> Dimitris
>
>
You can do that using
bitbake -e and looking for how DISTRO_FEATURES is formed in
the output of the command.
Alex
On Fri, 29 Mar 2019 at 10:37, Alexander Kanavin wrote:
>
> On Fri, 29 Mar 2019 at 09:51, Dimitris Tassopoulos wrote:
>
> > To do that, add this to your build/conf/
On Fri, 29 Mar 2019 at 09:51, Dimitris Tassopoulos wrote:
> To do that, add this to your build/conf/local.conf file
>
>> DISTRO_FEATURES_remove = " 3g"
This works around the issue after the fact. It's better to track down
where 3g is added in the first place, and adjust that.
Alex
--
On Mon, 18 Mar 2019 at 08:14, Mauro Ziliani wrote:
> Is it possible to sign Release automatically from bitbake?
At the moment signing deb repositories is not supported (but it is
supported for rpm and opkg).
You are welcome to add the missing support,
meta/lib/oe/package_manager.py is where it
Yocto master has got a lot of fixing around gitsm fetcher
(particularly creation of symlinks seems to be gone), so if you could
try that and report, that would be appreciated.
Alex
On Wed, 6 Mar 2019 at 15:20, philippe gislard
wrote:
>
> Hello everyone,
>
> Our use case is the following:
> - We
The supported recommended workflow for this things is with devtool.
Please try especially 'devtool modify' and 'devtool upgrade'. The latter
will rebase patches for you, regardless of how they were made.
Alex
On Wed, 6 Mar 2019 at 15:18, Pandey, Kamal wrote:
> Hello,
>
> I am trying to modify
On Sat, 23 Feb 2019 at 22:18, Philip Prindeville
wrote:
> I’ve worked on a lot of embedded projects involving cross-building (like
> AstLinux and OpenWrt), but I’m new to Yocto so please bear with the noob
> questions.
>
> I’d like to build packages (mostly RPM’s, plus a Linux kernel or three)
On Wed, 20 Feb 2019 at 19:08, Joshua Watt wrote:
> .../diffutils/diffutils/sdiff-no-kill.patch | 32 ---
> .../diffutils/diffutils_3.6.bbappend | 18 ---
> .../diffutils/diffutils_3.7.bbappend | 14
Should this be called simply
On Wed, 20 Feb 2019 at 12:25, Piotr Piwko wrote:
> I would like to add cmd.py library to my final image. In order to do
> so I modified python2-manifest.json file from poky delivery.
>
> This solution works fine. However, is there any possibility to do not
> change the global
You can just use a qemux86-64 target, which is much faster because it
executes directly on the hardware. What's the need to emulate
specifically arm?
Alex
On Mon, 18 Feb 2019 at 19:34, Jean-Christian de Rivaz
wrote:
>
> Hi,
>
> The chromium-x11 browser can't be compiled for the qemuarm machine
and I'm curious if RRS
> has caught up as expected.
>
> On 2/12/19 5:57 PM, Paul Eggleton wrote:
> > Hi Alex
> >
> > On Wednesday, 13 February 2019 6:22:23 AM NZDT Alexander Kanavin wrote:
> >> On Tue, 12 Feb 2019 at 17:10, wrote:
> >>> The recipe
On Thu, 14 Feb 2019 at 01:35, Timothy Froehlich wrote:
> Hi, I've been struggling a bit with this question. I want to use Yocto to
> build two+ products with separate dev/prod images for each (dev including
> debug-tweaks, etc.). I've ruled out separate image recipes because my dev
> builds
On Tue, 12 Feb 2019 at 17:10, wrote:
> The recipe reporting system integration with the layer index is available at:
> https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/ and the
> historical data has now been imported.
Sadly the new RRS still seems to be suffering from the 'outdated
You need to inspect the rootfs log, to find out precisely why they are
failing. Placing things into _ontarget() is only a part of the instruction,
and applicable only when postinsts have a genuine need to be executed on
the target device. I think your situation is explained by this:
If deferring
On Mon, 28 Jan 2019 at 11:20, wrote:
> There are 2 CVE issues fixing in latest u-boot upstream, so
> update commit id to involve these fixing patches.
We generally don't update commit id's to something random, as that
means picking a source tree in the middle of a development cycle. If
you want
One more thing: can you provide the .spec file that is generated
during build and used to create .rpm packages? You will find it under
tmp/work//x_media/
Please try not to edit anything out of it.
Alex
On Wed, 23 Jan 2019 at 12:02, Måns Zigher wrote:
>
> I have toke the rpm file that was
On Tue, 22 Jan 2019 at 17:59, Måns Zigher wrote:
> I am struggling with a recipe which more or less just downloads binaries and
> creating a package. We have previously been using ipkg but now we have
> switched to rpm in our builds. One of the binaries in the packages is a
> library let's
Alejandro
> Hernandez
> libmodulemd 1.7.02.0.0 Alexander Kanavin
> pcmanfm 1.3.01.3.1 Alexander Kanavin
> webkitgtk 2.22.4 2.22.5 Alexander Kanavin
> boost
You can start by reading the following:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Alex
On Fri, 18 Jan 2019 at 16:24, Seth McLean wrote:
>
> I've rebased and made some minor changes to a Python 3.7.1
> On 18 Jan 2019, at 16.34, Burton, Ross wrote:
>
>> On Fri, 18 Jan 2019 at 15:08, Ulf Samuelsson wrote:
>> We could insert a check if the KNOWN_TASKS is valid in a verification test.
>> When building core-image-minimal, the task order within core-image-minimal
>> is analyzed, (dependencies
Signed-off-by: Alexander Kanavin
---
README | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/README b/README
index 4752dc6..cb9f87e 100644
--- a/README
+++ b/README
@@ -30,13 +30,6 @@ Setup
upgrade-helper.conf. A sample file is provided in AUH source tree
On Wed, 9 Jan 2019 at 22:34, Stefano Cappa wrote:
> As explained here https://github.com/nodejs/Release, NodeJS 10 is the current
> active LTS and NodeJS 8 is right now in "Maintenance" (from January 2019).
>
> I saw that in master branch, Node has been updated from 8.12 to 8.14. Is
> there an
On Mon, 7 Jan 2019 at 20:32, Paul Eggleton
wrote:
> I think the RRS still serves a purpose, if it's putting out correct
> information of course.
> I have spent quite a bit of time reworking it, but Michael hasn't had the
> time to do
> the upgrade yet. I will ping him again.
It is certainly
3.0.03.0.0.20180831Alejandro
> Hernandez
> libmodulemd 1.7.02.0.0 Alexander Kanavin
> pcmanfm 1.3.01.3.1 Alexander Kanavin
> webkitgtk 2.22.4
On Fri, 4 Jan 2019 at 21:33, Shantanoo Desai wrote:
> I just have become more comfortable with Yocto for e.g. using devtool and
> basic bitbake commands.
>
> I am was successfully able to create some python applications for my target
> board via a layer. I would like to use CI / CD eventually
> On 3 Jan 2019, at 15.50, Derek Dresser wrote:
>
>> On Thu, Jan 3, 2019 at 5:36 AM Alexander Kanavin
>> wrote:
>> On Thu, 3 Jan 2019 at 10:11, Derek Dresser wrote:
>> > I have an application that uses features introduced in Python 3.6, so I am
>> > t
On Thu, 3 Jan 2019 at 10:11, Derek Dresser wrote:
> I have an application that uses features introduced in Python 3.6, so I am
> trying to add a new version of Python to my Yocto build. I know that 3.5.6
> is the latest version of Python that has been included in a Yocto release. I
> found
On Thu, 3 Jan 2019 at 10:09, Peter Balazovic wrote:
> I am trying to use "devtool" from eSDK to create own recipe. At first it
> works with repo and can generate recipe and binaries and deploy to target
> machine.
>
> Now I'd like to update it with a new revision of source code.
> So I updated
On Thu, 3 Jan 2019 at 10:10, Peter Balazovic wrote:
> I have created recipe with devtool and now I want to upgrade following
>
> > devtool upgrade myrecipe --srcrev 82a02d8585d262d6ab2d9dc335ed2231dc2d7f06
>
> I am getting error
>
> > ERROR: recipe is already in your workspace
>
> How to
It's likely that you ask bitbake to build something that has a hard
dependency on openssl 1.0. Most probably openssh.
Alex
On Thu, 20 Dec 2018 at 05:30, Vishwanath Chandapur wrote:
>
> Hi Team,
>
> I have set opnessl version in sumo but getting below errors.
>
>
> PREFERRED_VERSION_openssl =
On Mon, 17 Dec 2018 at 04:31, Bruce Ashfield
wrote:
> > This adds support for a virtual graphics card provided by QEMU,
> > which allows accelerated host-assisted GL inside QEMU guests.
>
> merged. This will be in my next consolidated pull request.
Thanks. I'm new to this - why is the patch in
This adds support for a virtual graphics card provided by QEMU,
which allows accelerated host-assisted GL inside QEMU guests.
Signed-off-by: Alexander Kanavin
---
cfg/virtio.cfg | 1 +
1 file changed, 1 insertion(+)
diff --git a/cfg/virtio.cfg b/cfg/virtio.cfg
index 98d76a67..039cb9a8 100644
On Fri, 14 Dec 2018 at 17:07, Richard Purdie
wrote:
> +with bb.tinfoil.Tinfoil() as tinfoil:
> +tinfoil.prepare(config_only=False)
> +recipes = self.recipes
> +if not recipes:
> +recipes = tinfoil.all_recipe_files(variants=False)
> +
> +
You can put the ipk file location directly into SRC_URI. Bitbake will
unpack it without further tricks. Then just copy the contents in
do_install().
Alex
On Sat, 17 Nov 2018 at 09:35, Robert Berger
wrote:
>
> Hi,
>
> I came across a scenario, which does not seem too strange, but I am not
> sure
I don’t think esdk is designed for this kind of ‘full stack’ development. You
can go back to working directly with yocto layers, and skip the esdk
altogether. Devtool will work exactly same (minus the sdk specific commands).
Alex
> On 18 Oct 2018, at 19.37, aaron_wri...@selinc.com wrote:
>
>
Hello Dan,
I believe you need to contact Nicholas:
https://lists.yoctoproject.org/pipermail/yocto/2018-September/042588.html
Alex
On Sun, 7 Oct 2018 at 13:20, Dan Lynch wrote:
>
> Greetings Yocto mailing listers,
>
> I am pretty new to Yocto and completely new to this list obviously. So
> allow
2018-09-21 21:43 GMT+02:00 Sinan Kaya :
> 2. Apply the attached patches to sumo branch.
>
> We'd like to hear the community opinion.
For stable branches the yocto project tends to be on the conservative
side. Which means option 2: backport the cve fixes.
For the master branch, version upgrades
You can probably have a .bbappend file which removes all the unneeded files in
do_install_append()
Alex
2018-09-21 19:29 GMT+02:00 Matthias Schoepfer
:
> Hi!
>
> In my case, I am using coreutils and busybox. But I only need one
> program of coreutils. Now, I have plenty binaries with .coreutils
I think what you are looking for is a Yocto generated SDK for your image?
bitbake -c populate_sdk
Alex
2018-09-18 23:00 GMT+02:00 Fabian Sturm :
> Hi,
>
> I am wondering, there does not seem to be any information about native
> compile of projects in a Yocto docker container. It seems that
It seems as though the build system is unable to create this directory:
/home/b/yocto-krogoth/../../yocto/downloads//uninative/acf1e44a0ac2e855e81da6426197d36358bf7b4e88e552ef933128498c8910f8
You probably have a permission problem there, working from /home/b but
attempting to create /home/yocto.
These two are orthogonal. "amalgamation" is building sqlite from a
single source file for performance and simplicity reasons, which is
what yocto does as well, despite there being no mention of it in the
recipe. Enabling or disabling specific sqlite features can be done
regardless of whether
It's right in the message?
ERROR: Logfile of failure stored in:
/home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/temp/log.do_rootfs.27709
Alex
2018-09-09 10:58 GMT+02:00 Jens Rehsack :
> Hi,
>
> I got following issue when building an
Sadly, Yocto is not well equippped to deal with projects that download
stuff from the internet as a part of the build process. I'd say if
it's just one project, write a separate recipe for it, and build it
via that. Then install into the original recipe's sysroot or build dir
as needed, and make
2018-08-31 12:49 GMT+02:00 Alan Martinovic :
> am just in the process of forming a base for automated nightly builds.
> The goal is to have the build process run every night and report what
> the status was.
>
> I've opted for python for all the conditionals and checks and then have
> external
>
2018-08-28 21:39 GMT+02:00 jan vermaete :
> It's working. Thanks!
>
> I hope deb package will be again fully supported in the next release.
Someone has to do the work though. If you truly want it fixed, you
know what to do :)
Alex
--
___
yocto mailing
2018-08-28 16:34 GMT+02:00 jan vermaete :
> I have a perfect working project at the latest state of Sumo.
> However, building the image when having all meta layers at the latest
> state at master fails.
>
> The step 'do_rootfs' gives:
> --
> The following packages have unmet dependencies:
>
1 - 100 of 381 matches
Mail list logo
