Trying to produce c++ versions of dmalloc libraries.The dmalloc recipe dmalloc_5.5.2.bb looks to be configured to build the c++ versions with: 'EXTRA_OECONF += "--enable-threads --enable-cxx

Current Dev Position: YP 3.4 M2 Next Deadline: 12th July 2021 YP 3.4 M2 build Next Team Meetings: Bug Triage meeting Thursday July 22nd at 7:30am PDT

Thanks...

Not deleting the source tree is the default behaviour. It sounds like you've inherited rm_work, so if you want to not delete build trees after completion then add the recipe name to

Thanks Richard, I suspect you're right. I'm using fuse-overlayfs which I'm mounting with the 'noxattrs' option because the host is Fedora and its SELinux configuration interferes with yocto in other

Hi Alex, RP, Mark, I did some research on the subject in order to try to figure out what is going on. 1) I come to a similar conclusion with what found, but tried to look a bit deeper for the

All, YP M+ or high bugs which moved to a new milestone in WW29 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 12937 Consistent naming scheme for

All, The below were the owners of enhancements or bugs closed during the last

All, Below is the list as of top 50 bug owners as of the end of WW29 of who have open medium or higher bugs and enhancements against YP 3.4. There are 72 possible work days left until the final

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

From 59ed46416217e0c0b44203bc58e472e4068dba83 Mon Sep 17 00:00:00 2001 From: Mingrui Ren <jiladahe1997@...> Date: Mon, 19 Jul 2021 23:02:19 +0800 Subject: [PATCH v2] Add a new

What flag do I set in order to keep the source code for a recipe being built within the build tree after compilation ? Thanks, Steve

Support for 'minnowboard' and 'up_squared_32' BOARDS have been

This updated code-base should be compatible with Django 3.1 and obviously 3.2 (but not 3.0 or earlier). Django 3.2 requires Python 3.6+. With the upgrade to Celery 5, it is safer to

In celery 5, the --workdir argument must come before the 'worker' subcommand. Without this, celery cannot load the layerindex module and this causes the celery container to continually

New in Django 3.2 To quiet warnings, set DEFAULT_AUTO_FIELD to the default value 'django.db.models.AutoField' NOTE: The default value for newly created Django 3.2 projects is

Upgrade to the latest Django 3.2.x LTS for extended support up until April 2024. Signed-off-by: Tim Orling <timothy.t.orling@...> --- requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1

* Add - Amber Elliot - Tim Orling Signed-off-by: Tim Orling <timothy.t.orling@...> --- templates/layerindex/about.html | 2 ++ 1 file changed, 2 insertions(+) diff --git

Since we are on a "modern" version of Python in Debian buster container (3.7) and a modern version of Django (3.1.x) we should be able to run with the latest of all dependencies. Signed-off-by: Tim

10.2 was based on Ubuntu bionic 18.04, bumping to 10.3 as it is the first release on Ubuntu focal 20.04 Signed-off-by: Tim Orling <timothy.t.orling@...> --- docker-compose.yml | 2 +- 1 file