Hello everyone,
I've been looking into updating oe-core's aging web engine/browser
combo, and want to give you a heads up about what's going to happen:
1) webkit-gtk engine will be updated to latest stable upstream release
(2.8.3 which is providing Webkit2 API and is a Gtk3 port)
2) midori
On 06/15/2015 05:24 PM, Burton, Ross wrote:
If you actually compare the build dependencies, you'll see that Midori
and Epiphany are actually almost identical.
We need to upgrade WebKit as the release we're shipping has known
security flaws and is very old - and the community is rightly moaning
On 06/16/2015 09:50 AM, Andreas Müller wrote:
How about doing same as others do e.g fedora [1-2]: Keep two version
of webkit-gtk based on same recent code:
* gtk2/webkit1
* gtk3/webkit2
Before showing how, you need to explain why. Fedora has to package
webkit1 because they have a lot of apps
On 06/16/2015 04:27 PM, Andreas Müller wrote:
Yes and midori is the only working browser in Yocto (I know): firefox
crashes since very long time for illegal ARM instruction and chromium
does not start at all.
Latest epiphany will be provided as a replacement for midori. It works
fine here in
On 06/16/2015 04:37 PM, Alexander Kanavin wrote:
Latest epiphany will be provided as a replacement for midori. It
works fine here in the core-image-sato under qemu. I can't promise it
will work on ARM, but any ARM-specific issues are almost certainly
in webkit's (or other we
On 06/25/2015 11:02 PM, Aníbal Limón wrote:
I'm glad to announce the enabling of Automatic Upgrade Helper (a.k.a.
AUH), the AUH is a service
that provides recipe upgrades and will be run on weekly basis.
If you are a maintainer (listed in [1]) you will receive AUH emails with
Recipe upgrades whe
On 08/13/2015 02:21 PM, Paul Sherwood wrote:
I am not affiliated to any Yocto Project member organisation, but am
assisting with integration at the Automotive Grade Linux project, which
is re-using some work from upstreams at git.yoctoproject.org
Recently members of the AGL community have starte
On 11/27/2015 05:11 PM, Benoit Rapidel wrote:
I want to install NumPy with Python3 supporton a Beaglebone Black.
Unfortunately, I couldn't find any information or a recipe. Anyone has
ever tried, success, failed ?
There is a recipe for numpy in oe-core, but it's not particularly up to
date, a
On 11/27/2015 06:39 PM, Benoit Rapidel wrote:
I found one in meta. How do I update it ? I'm using poky jethro.
Should a create a new one named python3-numpy or the same recipe should
handle both
python versions ?
From what I can see, the standard approach is to create a separate
recipe for pyt
On 01/04/2016 07:25 AM, recipe-rep...@yoctoproject.org wrote:
This mail was sent out by Recipe reporting system.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstr
On 01/19/2016 07:24 PM, Philip Balister wrote:
* Recipe copied from meta-openembedded/jethro.
* Used by GNU Radio.
Signed-off-by: Philip Balister
Thanks, all three pushed to meta-qt4.
Alex
--
___
yocto mailing list
yocto@yoctoproject.org
https
On 01/19/2016 07:24 PM, Philip Balister wrote:
* Copied from meta-openembedded/jethro.
* Used by GNU Radio.
ERROR: QA Issue: File '/usr/lib/libqwtmathml.so.6.0.1' from qwt was
already stripped, this will prevent future debugging! [already-stripped]
ERROR: QA Issue: File '/usr/lib/libqwt.so
On 02/24/2016 05:35 PM, Khem Raj wrote:
I have this command in my qmake pro files:
VERSION = $$system(git describe --abbrev=0 --tags)
__ __
I would like to have the package manager follow the tag versioning.
__ __
Which means I would like to have somethin
> The gstreamer _git recipes have not been updated to include the
> gobject introspection patches which were applied to the 1.6.3 recipes.
Yeah, I forgot about the git recipes, as they're totally hidden from
default builds. I'll get them fixed.
> Try disabling gobject introspection via DISTRO or
> I am trying to build latest poky version from upstream but it was failing
> in "gobject-introspection-data?".
>
> I disabled it with comments mentioned in:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?id=8c14c746da1784c4bdaa621dde6fccd99e72ef1b
>
>
> by adding folloing line
On 03/23/2016 04:24 PM, Jaggi, Manish wrote:
What is the process of upstreaming a new meta layer ?
The layer is specific to cavium thunderx and it can be named as meta-cavium
Is this the correct mailing list to upstream ?
You need to publish the layer somewhere public (e.g. github), and then
On 04/03/2016 05:02 AM, Jaggi, Manish wrote:
You need to publish the layer somewhere public (e.g. github), and then
how to publish the layer to git.yoctoproject.org instead of github ?
Do you have a reason to have your layer on git.yoctoproject.org instead
of any other repo service? There i
On 04/06/2016 06:52 PM, Burton, Ross wrote:
Regarding python3, whenever I change the "--with-python" option to
something other than "python2.7" then I get an error.
You need to change the inherits to pull in python3native. Sadly
flipping between py2 and py3 isn't trivial.
I think 'g
On 04/07/2016 04:35 PM, Burton, Ross wrote:
Yeah, that. :) Annoyingly it's not just a PACKAGECONFIG due to how
python-native works.
Yeah, the annoying side effect is that every python thingy needs to be
packaged twice - not so visible in oe-core, but very visible in
meta-oe's meta-python:
On 04/07/2016 07:58 PM, Chris Trobridge wrote:
http://cgit.openembedded.org/meta-openembedded/tree/meta-python/recipes-devtools/python
>
> Will be fixed by deprecating python 2, of course.
>
> Alex
Is there a shorter term solution that's generally applicable, like a
separate python3-gobjec
Hello,
here is the information about gobject introspection that should be placed
to the release notes of the upcoming yocto release.
1. Introduction
This Yocto release adds support for generating and packaging GObject
introspection data. GObject introspection data is a description of the API
pr
Hello,
here is the information about gobject introspection that should be placed
to the release notes of the upcoming yocto release.
1. Introduction
This Yocto release adds support for generating and packaging GObject
introspection data. GObject introspection data is a description of the API
pro
On 04/26/2016 11:05 AM, Zhenhua Luo wrote:
Any ideas as to why "qemu-ppc64 crashes out immediately"?
I can confirm the build ends in a segfault when I tried building
gobject-introspection for the t1042d4rdb-64b machine.
*/[Luo Zhenhua-B19537] This is a gobject-introspection support issue of
QEM
On 04/12/2018 12:44 PM, Richard Collins wrote:
I've inherited a Yocto project that I know to be an old version. So one
of my tasks is to update to the latest version. Before I do this I would
like to know what version I have. The only information I can find is the
bitbake version, BB_VERSION
On 04/12/2018 03:11 PM, Richard Collins wrote:
I get the following for DISTRO.
DISTRO = "yogurt"
DISTRO_VERSION = "BSP-Yocto-RK3288-PD17.1.1"
Can't find any reference to yogurt so I assume this is something the
supplier of our SOM's has done. Looking on their Wiki it seems to be
On 04/12/2018 06:19 AM, atulkumar singh wrote:
These days we are hearing a lot about artificial intelligence and now
every company whichever domain it belongs works in AI.
Either it's about automotive(Autonomous driving), Surveillance(Object
detection) or IOT.
So as the industry is moving toward
On 05/01/2018 05:23 AM, Paul Eggleton wrote:
The Recipe Reporting System (RRS - live instance at
http://recipes.yoctoproject.org) was originally developed as a fork of
the layer index (live instance at http://layers.openembedded.org) - this
set of changes rebases it on top of master and makes the
On 05/02/2018 04:53 PM, Irving ST wrote:
Thank you for your help and explanations. Unfortunately just removing
ptest doesn't make it build.
This is the error when I tried bitbake core-image-minimal:
ERROR: Nothing PROVIDES 'readline' (but
/home/irving/srcgit/poky/meta/recipes-devtools/python/pyt
On 05/03/2018 01:42 PM, Paulo Neves wrote:
# Add ROOTFS_RPM_DEBUG to the documentation;
I'd rather get rid of it, the less variables the better :)
# Detect if we are running with debug output and enable the debugging
output. This is the most elegant solution but I do not know how to
detect if
On 05/03/2018 04:37 PM, Peter Kjellerstedt wrote:
# Have dnf always print in verbose mode and print the output to
bb.debug instead of bb.note.
I think this is the best solution actually.
I disagree with changing bb.note to bb.debug for this. It is very good
to be able to look in log.do_rootfs
On 05/04/2018 03:42 PM, Paulo Neves wrote:
I will propose a patch with a default bb.debug, and always have the
verbose on dnf. Let's see how it affects the performance. I cannot
test this in a docker container because of the problems described
below:
In the mean time I found what was happening w
On 05/04/2018 03:41 PM, Alexander Kanavin wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1537564
Obviously you and anyone else affected need to make noise in the redhat
bugzilla, otherwise they're likely to keep this low priority.
On 05/04/2018 03:50 PM, Scott Rifenbark wrote:
If ROOTFS_RPM_DEBUG should be a documented variable in the Yocto Project
Reference Manual, could someone please provide me with some base
explanation of the variable and any usage specifics?
No need, we're going to remove it.
Alex
--
On 05/07/2018 12:03 PM, Mirza Krak wrote:
I have also been bitten by rpm performance issues in docker and glad
that I found this. I am in the process of verifying above (on pyro
branch).
Is this patch on its way to pyro and rocko branches?
As far as I know, no. You are welcome to backport and
On 05/08/2018 12:33 PM, Peter Kjellerstedt wrote:
FYI, the already applied patch only solves half the problem. I have an
updated version that solves all of it that I am preparing for publication.
I only need to make some verifications first...
I just found that out as well. Lua is not relevant,
On 05/08/2018 05:55 PM, Iván Castell wrote:
Is this a bug related with curl or ca-certificates recipe? What should
be the right way to fix it?
Fetching and installing packages over the network during image creation
is not supported or tested in YP. You need to build them locally, with
recipes
On 05/09/2018 09:29 AM, Iván Castell wrote:
But I am not fetching nor installing packages over the network during
image creation. I just build an image using local recipes (standard
procedure). One of those local recipes sets up a remote repository for
rpm packages (adding /etc/yum.repos.d/yoct
On 05/10/2018 11:59 AM, Piotr Piwko wrote:
For 'read-only-rootfs' image feature, tweaks are done in functions
executed after generating rootfs.
meta/classes/rootfs-postcommands.bbclass:ROOTFS_POSTPROCESS_COMMAND
+= '${@bb.utils.contains("IMAGE_FEATURES", "read-only-rootfs",
"r
On 05/17/2018 12:17 PM, Steve Pavao wrote:
I am trying to build for raspberrypi3 near head of sumo. I get the following
troublesome warning fairly often since I started doing some builds in sumo and
master the past week.:
WARNING: core-image-minimal-1.0-r0 do_populate_sdk: The postinstall inte
On 05/18/2018 12:06 AM, mamta0...@yahoo.com wrote:
Apologies if these are basic questions but thought this will be the
best place to find answers to the point
So our requirement is to build open source packages in Linux, windows
and Mac on a build system. Currently we have an internal build sys
On 05/22/2018 03:27 PM, techi eth wrote:
Can anyone give me hint on above point. I think it will be something
basic while populating SDK's.
Please let me know if any information needed.
Can I give you a tip? Introduce yourself properly. What is your name,
what company you work for, and what
On 05/26/2018 09:27 PM, Michael Gloff wrote:
Remove -std=gnu++98 from QMAKE_CXXFLAGS and add where
necessary.
Thanks, pushed to master.
Alex
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
2018-06-01 8:46 GMT+03:00 Damien LEFEVRE :
> For the same MACHINE I create the following images:
> - myimage-production
> - myimage-rnd
> - myimage-retail
>
> The production one has production assisted tools for flashing peripheral HW,
> testing vital HW components, writing some serial numbers, etc
I have to say defining multiple distros and then tweaking recipes according
to those definitions is not a good practice, as recipes should generally
only access DISTRO_FEATURES and otherwise be distro-agnostic. The above
iptables scenario should be handled with different image recipes, which
pull i
Hey Alexander,
> you seem to have a good understanding on the concepts.
> Would you say that:
>
> > A build always builds a single distro
>
> is somewhat of a rule?
>
>
>
>
> On Fri, Jun 1, 2018 at 11:24 AM, Alexander Kanavin > wrote:
>
>> I ha
2018-06-01 13:38 GMT+03:00 Alan Martinovic :
> Building them at the same time causes an issue:
>
> Traceback (most recent call lastd):
> File "/home/alan/workspace/senic-os-dev/oe/scripts/lib/wic/filemap.py",
> line 120, in _open_image_file
> self._f_image = open(self._image_path, 'rb')
>
ot;)
>
> but it's not printing anything even when running bitbake with -DDDvvv
>
> On Fri, Jun 1, 2018 at 12:52 PM, Alexander Kanavin
> wrote:
>> 2018-06-01 13:38 GMT+03:00 Alan Martinovic :
>>> Building them at the same time causes an issue:
>>>
>>&
You start by defining 'works'. It can be anything from quickly
building an image and booting it on the target hardware to see a login
prompt, to running a massive test suite and achieving 100% pass rate.
Alex
2018-06-12 2:14 GMT+03:00 Ricardo Ramirez :
> Thanks for the reply, Khem!
>
> What steps
On 06/12/2018 04:07 PM, Ricardo Ramirez wrote:
You are right. I didn't define a clear scope for what I wanted to
validate. Apologies about that imprecision.
If possible, I'd like to divide the validation process into three stages
1. The system has a clean boot up process
2. The system is test
2018-06-14 7:02 GMT+03:00 Tim Hammer :
>
> My changes for U-Boot are not working as expected. I am wondering- did I use
> devtool incorrectly?
>
> I used 'devtool modify' to create a working copy of the vendor's u-boot and
> copied & modified files to add support for my custom board. I did my work
2018-06-15 2:11 GMT+03:00 Peter Kjellerstedt :
> * `devtool modify -w `
> * Modify some file, e.g., add some comment to the Makefile.
> * Commit it with subject "Change 1"
> * Repeat the two steps above two more times, increasing the number in
> the subject each time.
> * `devtool finish `
> * E
2018-06-24 20:44 GMT+02:00 Selvaraj V :
> I had looked at the Python 3.5 recipe for using it as a template but adding
> to my troubles there are patches mentioned in the recipe. How do I find
> which patches to include if I am starting to write the recipes for python
> 3.6 ?. Can I know the procedu
How to do this is specific to each project. Generally, you want the
target recipe to depend on the native recipe (so that the necessary
native tools show up in the target sysroot), and then you need to
study the build system of the upstream component project (makefiles
etc.) to see how it can be in
I do not recommend that you copy the binary over; it's better to clearly
separate native and target. Just patch the makefile.
Alex
2018-07-07 13:30 GMT+02:00 Timm :
> Am 07.07.2018 um 12:17 schrieb Alexander Kanavin:
>
> How to do this is specific to each project. Generally
If the issue is that openssl is 'out of date', then oe-core already
provides a 1.1 version that can be selected via PREFERRED_VERSION as
well.
What is the specific need for the 3rd party version?
Alex
2018-07-08 0:41 GMT+02:00 Burton, Ross :
> Presumably you've a recipe for the vendor openssl.
Just fix the build issue. Look into how opensslconf.h gets created and
where the -32 suffix comes from and why the included file is absent.
Seriously - that is less effort than trying to make Yocto do what it really
was not designed for, and certainly takes less than one week to resolve.
Also, yo
of my emails (still included here below) w.r.t.
> where the issue came from. It's coming from application code outside of
> Yocto that is built as 32-bit apps, while Poky/BSP are built in 64-bit.
>
>
>
> ________
> From: Alexander Kanavin
&g
e
or make a super-minimal image which doesn't pull in 64 bit openssl.
Alex
2018-07-09 20:16 GMT+02:00 Alexander Kanavin :
> The error message you've provided is caused by an openssl header
> referring to another header file that doesn't exist. It does not come
> from ap
Yes. Implement a class and inherit it from the recipes.
Alex
2018-07-10 20:50 GMT+02:00 Michael Habibi :
> I was wondering if there is a way I can apply a global modification to all
> recipes in a layer? For instance, we have our own layer for our changes that
> sit on top of the base Yocto/OE la
You probably need to do this for openssl 1.1 as well as it soon will
be the default.
Alex
2018-07-12 0:42 GMT+02:00 Juro Bystricky :
> Patch to allow building openssl for Windows.
> openssl can also become part of SDK, i.e:
>
> SDKMACHINE="x86_64-mingw32"
> MACHINE = "qemux86-64"
> TOOLCHAIN_HOST
You are building something that requires openssl 1.0 (most likely
openssh, which is not compatible with 1.1). You have to exclude it
from your builds first.
Alex
2018-07-16 3:19 GMT+02:00 Russell Peterson :
> Hello,
>
> I’m looking to change to openssl version 1.1. I’m using the rocko branch.
>
2018-07-18 13:37 GMT+02:00 Zoran Stojsavljevic :
> do_install() {
> install -d ${D}${bindir}
> install -m 0755 cannelloni ${D}${bindir}
> }
You are installing only the executable binary here, but not the
corresponding library. Just remove the do_install function altogether,
and cmake class
This page has a tip on what might be causing 'git ls-remote':
https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_create_my_own_source_download_mirror_.3F
Alex
2018-07-21 10:32 GMT+02:00 MOHAMMAD RASIM :
> Hi, is there a way I can run a bitbake build offline? I have all the
> required source
Note that we programmatically create the rpm spec files, and there is
currently no support for writing changelogs into them.
Generally, hand-crafted changelogs are just a maintenance burden, if you ask me.
Alex
2018-07-23 20:49 GMT+02:00 Burton, Ross :
> On 23 July 2018 at 18:30, Vikram Chhibber
2018-07-26 14:56 GMT+02:00 Ayoub Zaki :
> Is it possible to define a MACHINE configuration with a 64 Bit kernel and 32
> Bit user space ?
>
> The user space should not be using a x32 ABI.
I think (but I am not sure), that you can do it with multilib. Define
a configuration like this:
https://gith
You don't need to check out a specific tag. Just switch to the latest
commit in the branch you want (e.g. sumo).
Alex
2018-08-09 14:39 GMT+02:00 Dhanush K.S :
> Hello,
>
> I am currently trying to migrate from Yocto 1.8 Poky Fido 13.0.0 to Yocto
> 2.5.
>
> After cloning the Poky repository, I was
My apologies, but do not use $DATETIME in your version strings. It's a
seriously bad idea that goes against Yocto's philosophy - that
everything that goes into a build is deterministic and does not change
on the fly. Instead, define and update the date and time statically
through config files. If y
Give the two recipes different names - app-release_1.0.bb and app-latest_git.bb
Alex
2018-08-10 15:36 GMT+02:00 Mauro Ziliani :
> Hi all
>
> I need to do this scenario.
>
> I have 2 image recipes:
>
> - final.bb
>
> - testing.bb
>
> final.bb and testing.bb install the same application name app.
>
2018-08-10 16:50 GMT+02:00 Marc Ferland :
> | Processing files: pylon-5.0.12-r0.aarch64
> | *** buffer overflow detected ***:
> /home/vagrant/build/tmp/work/aarch64-poky-linux/pylon/5.0.12-r0/recipe-sysroot-native/usr/bin/rpmbuild
> terminated
> | Aborted (core dumped)
This is not a yocto issue, b
I see this in the commit history:
As was previously announced, anything older than 4.14 is being
dropped in the master/release branches to better support newer
processors and to ensure that safe/secure kernels are the
defaults for all builds. The time required to update the older
2018-08-18 11:06 GMT+02:00 Sarayu Sivanandam :
> | make[2]: *** [docbook2man.html] Segmentation fault (core dumped)
> | make[2]: *** Waiting for unfinished jobs
> | Makefile:458: recipe for target 'api.html' failed
> | make[2]: *** [api.html] Segmentation fault (core dumped)
> | Makefile:458:
2018-08-16 16:07 GMT+02:00 Nader Hariri :
> Hi, I am new to Yocto. I am working on ptest-runner.
>
> 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
>
> DISTR
2018-08-20 14:07 GMT+02:00 Nader Hariri :
> So, contrary to what is stated in the ptest wiki and the yocto
> documentation, using EXTRA_IMAGE_FEATURES doesn't install ptests packages
> (from ptest-enabled recipes) in my image, and I can't figure out why ..
You can run 'bitbake -e ' to figure out
2018-08-20 15:16 GMT+02:00 Seth Bollinger :
> We've been seeing the following warning for a while now. Is this expected?
>
> WARNING: manuf-image-1.0-r0 do_rootfs: Intentionally failing postinstall
> scriptlets of ['coreutils'] to defer them to first boot is deprecated.
> Please place them into pk
2018-08-20 15:36 GMT+02:00 Nader Hariri :
> I ran 'bitbake -e ' as you have suggested. I can see from the logs
> that the variable IMAGE_FEATURES does get appended the value of
> ${EXTRA_IMAGE_FEATURES}, however I still have no -ptest packages in my
> image. Is there anything wrong in my logs?
>
>
2018-08-20 15:56 GMT+02:00 Pandey, Kamal :
> cd
> /home/iepl/work/yocto_build/poky/build/tmp/work/aarch64-pdm3-linux/firefox/52.9.0esr-r0/firefox-52.9.0esr/firefox-build-dir
>
>
> | /home/iepl/work/yocto_build/poky/build/tmp/work/aarch64-
> pdm3-linux/firefox/52.9.0esr-r0/firefox-52.9.0esr/configu
f/bitbake.conf:806
> # "${EXTRA_IMAGE_FEATURES}"
> # pre-expansion value:
> # " ${EXTRA_IMAGE_FEATURES}"
> IMAGE_FEATURES=" ptest-pkgs"
>
> As we can see, I still have the suspicious space but it has shrunk from 2
> spaces to 1 space. And -p
2018-08-20 20:45 GMT+02:00 :
> We are encountering a build problem after migrating to Poky 2.3 and Pseudo
> 1.8.1, and need help to resolve this.
> It is hampering our development efforts, forcing us to rebuild images
> frequently.
>
> Background:
> Our build applies SELinux file contexts, durin
2018-08-22 15:58 GMT+02:00 :
> I should add that the same problem exists in Poky 2.5, and top of Pseudo git
> repo. The problem was introduced, best I can tell, was when the entire
> Pseudo database structure was rewritten. As a result of the major overhaul
> messing with patches is problemat
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:
> locale
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-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
>
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 su
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 image
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 amalga
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.
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 most
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
>
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 ar
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
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:
>
> M
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 h
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)
> +
> +
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 = "1.
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 correctly
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 S
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 th
> 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 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 f
wlib3.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
1 - 100 of 393 matches
Mail list logo
