|
Yocto Project Virtual Summit 2020 - CFP Open
Reyna, David
Hello all!
Yocto Project is pleased to announce the Yocto Project Virtual Summit 2020, a technical conference for engineers, open source technologists, students and academia in the OSS space.
Organized in conjunction with ELCE 2020, this 2-day event is where individuals will learn about Yocto Project’s direction — including, but not limited to, new releases, development tools, features — get training on the next wave of embedded Linux technologies,
and network with their industry peers, Yocto Project maintainers and experts.
FORMAT: The class will be presented in Zoom. It will be highly interactive with experienced teachers from around the world, and includes chat sessions, side rooms, teaching assistants, and hands-on exercises
with live class accounts.
1) Yocto Project Virtual Summit
DATE: Thursday, October 29 and Friday, October 30, 2020
TIME: 12.00PM-GMT to 8.00PM-GMT (5AM to 1PM in PST time, 8AM-4PM in EDT time, 5.30PM-1.30AM in India), as per ELCE
LOCATION: Zoom
COST: $40 USD
REGISTRATION: Go to the ELCE registration site and add Yocto Project Summit as part of your registration (when the extra events become available)
EVENT INFORMATION: https://pretalx.com/yocto-project-summit-2020
2) Yocto Project Virtual Summit - Call For Papers (CFP)
The CFP is now open. Become a presenter yourself and share your expertise!
CFP Closes: 11:59 PM PST on Monday, September 21, 2020
CFP Notifications: Monday, September 28, 2020
Slide Due Date: Monday, October 26, 2020
Submit your proposals here: https://pretalx.com/yocto-project-summit-2020/cfp
CFP list of sample topics:
Best regards,
Yocto Project Advocacy Team
If you have any questions or issues, contact us at: conferences@...
|
|
|
|
Yocto Project Virtual Summit 2020 - CFP Open
Reyna, David
Hello all!
Yocto Project is pleased to announce the Yocto Project Virtual Summit 2020, a technical conference for engineers, open source technologists, students and academia in the OSS space.
Organized in conjunction with ELCE 2020, this 2-day event is where individuals will learn about Yocto Project’s direction — including, but not limited to, new releases, development tools, features — get training on the next wave of embedded Linux technologies,
and network with their industry peers, Yocto Project maintainers and experts.
FORMAT: The class will be presented in Zoom. It will be highly interactive with experienced teachers from around the world, and includes chat sessions, side rooms, teaching assistants, and hands-on exercises
with live class accounts.
1) Yocto Project Virtual Summit
DATE: Thursday, October 29 and Friday, October 30, 2020
TIME: 12.00PM-GMT to 8.00PM-GMT (5AM to 1PM in PST time, 8AM-4PM in EDT time, 5.30PM-1.30AM in India), as per ELCE
LOCATION: Zoom
COST: $40 USD
REGISTRATION: Go to the ELCE registration site and add Yocto Project Summit as part of your registration (when the extra events become available)
EVENT INFORMATION: https://pretalx.com/yocto-project-summit-2020
2) Yocto Project Virtual Summit - Call For Papers (CFP)
The CFP is now open. Become a presenter yourself and share your expertise!
CFP Closes: 11:59 PM PST on Monday, September 21, 2020
CFP Notifications: Monday, September 28, 2020
Slide Due Date: Monday, October 26, 2020
Submit your proposals here: https://pretalx.com/yocto-project-summit-2020/cfp
CFP list of sample topics:
Best regards,
Yocto Project Advocacy Team
If you have any questions or issues, contact us at: conferences@...
|
|
|
|
Yocto Technical Team Minutes, Engineering Sync, for September 1, 2020
Trevor Woerner
Yocto Technical Team Minutes, Engineering Sync, for September 1, 2020
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are made to ensure the below is accurate and valid. However, errors sometimes happen. If any errors or omissions are found, please feel free to reply to this email with any corrections. == attendees == Trevor Woerner, Stephen Jolly, Jan-Simon Möller, Alejandro H, Bruce Ashfield, Armin Kuster, Richard Purdie, David Reyna, Steve Sakoman, Michael Halstead, Ross Burton, Paul Barker, Mark Morton, Scott Murray, Jeremy Puhlman, Joshua Watt, Jon Mason, Randy MacLeod == notes == - entered m3 feature freeze - working on a couple patches for 3.2 - bitbake server startup changed to avoid recently discovered issues will wait for 3.3 to make default - one more round of recipe upgrades before m3 build (later this week) - -fno-common back to gcc10 default - still some AB issues - looking for help with unassigned bugs == general == RP: list of 3.2 things: Mark’s hash equivalency prserv fix RP: where are we with bind? Armin: haven’t gotten around to sending them RP: please do so RP: want to get more of the AUH upgrades in too. RP: Alex has queued up the rest. RP: high priority bitbake bug on startup that needs to go in docs changes, we want to cut over to sphinx before m3 TrevorW: what’s the -fno-common issue? RP: gcc changed defaults with gcc10, caused namespaces to overlap (and code builds to fail), we temporarily switched away from the new default, waited for upstream and created patches, now we can switch back to gcc10’s default Joshua: what still needs to be done with the docs? RP: check Nico’s doc. right now: mostly marking up the code sections. please coordinate on the mailing list PaulB: will be giving a talk at the upcoming Linaro Connect on license compliance with Yocto, Linaro Connect (virtual) is supposed to be free to attend this year RP: i’ve heard that YP was mentioned at last week’s Plumbers, does anyone know when/where it could have been mentioned? (various): not sure Scott: I don’t see Khem here, maybe he was talking about it? TrevorW: Alistair Francis is a contributor to YP and RISC-V, it could have been brought up in relation to that. the RISC-V YP BSP carries a lot of patches Randy: Saul Wold is joining WR today! RP: glad to hear he’s returning to YP |
|
|
|
Re: RootFS Size increase during Migration
On Thu, Sep 3, 2020 at 10:18 PM Aashik Aswin <thisisaash9698@...> wrote:
Enable buildhistory in both builds https://www.yoctoproject.org/docs/3.1/dev-manual/dev-manual.html#enabling-and-disabling-build-history once you have it enabled build the images (assuming you are building in two different workspaces ) you can diff installed-package-sizes.txt from two builds and it should give you some hints, if you are switching the build in same workspace between two releases then you can do two builds and inside buildhistory folder run git show cmd which should show you delta between last two builds Thanks, |
|
|
|
RootFS Size increase during Migration
Aashik Aswin
Hi Developers, I am migrating my code from Yocto Thud (4.19) Kernel to Yocto Zeus (5.4) Kernel. The recipes and conf files are essentially the same, but I am seeing a substantial increase in the RootFS Size and Subsequent final image size (Close to 40 MB). Any idea on how we can debug this or where we can start for inspecting why the image size increase. Thanks, Aashik |
|
|
|
@prashant2314
Hi,
I'm using Rocko yocto for my project, in this when I'm including dahdi-linux I'm getting unneeded files error. Error logs: ERROR: dahdi-linux-3.1.0-r0 do_package: QA Issue: dahdi-linux: Files/directories were installed but not shipped in any package: /usr/lib /usr/lib/hotplug /usr/lib/hotplug/firmware /lib/firmware /lib/firmware/dahdi-fw-te133.bin /lib/firmware/dahdi-fw-tc400m.bin /lib/firmware/dahdi-fw-oct6114-256.bin /lib/firmware/.dahdi-fw-oct6114-032-1.05.01 /lib/firmware/dahdi-fw-te436.bin /lib/firmware/dahdi-fw-a8b.bin /lib/firmware/.dahdi-fw-tc400m-MR6.12 /lib/firmware/.dahdi-fw-a8a-1d0017 /lib/firmware/.dahdi-fw-a8b-1f001e /lib/firmware/.dahdi-fw-hx8-2.06 /lib/firmware/dahdi-fw-te435.bin /lib/firmware/dahdi-fw-hx8.bin /lib/firmware/.dahdi-fw-te436-10017 /lib/firmware/.dahdi-fw-te820-1.76 /lib/firmware/dahdi-fw-te820.bin /lib/firmware/dahdi-fw-te134.bin /lib/firmware/dahdi-fw-a4a.bin /lib/firmware/.dahdi-fw-te435-13001e /lib/firmware/dahdi-fw-a8a.bin /lib/firmware/dahdi-fw-oct6114-128.bin /lib/firmware/.dahdi-fw-oct6114-064-1.05.01 /lib/firmware/dahdi-fw-oct6114-064.bin /lib/firmware/.dahdi-fw-te133-7a001e /lib/firmware/.dahdi-fw-vpmoct032-1.12.0 /lib/firmware/.dahdi-fw-a4a-a0017 /lib/firmware/.dahdi-fw-oct6114-128-1.05.01 /lib/firmware/.dahdi-fw-oct6114-256-1.05.01 /lib/firmware/dahdi-fw-oct6114-032.bin /lib/firmware/dahdi-fw-vpmoct032.bin /lib/firmware/.dahdi-fw-a4b-d001e /lib/firmware/dahdi-fw-a4b.bin /lib/firmware/.dahdi-fw-te134-780017 **Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.** dahdi-linux: 36 installed and not shipped files. [installed-vs-shipped] ERROR: dahdi-linux-3.1.0-r0 do_package: Fatal QA errors found, failing task. ERROR: dahdi-linux-3.1.0-r0 do_package: Function failed: do_package ERROR: Logfile of failure stored in: /home/prashant/P_DIALT/RENESAS/RZ_G2E /Yocto_for_experiments/rzg2_bsp/build/tmp/work/ek874-poky-linux/dahdi-linux/3.1.0-r0/temp/log.do_package.9978 ERROR: Task (/home/prashant/P_DIALT/RENESAS/RZ_G2E/Yocto_for_experiments/rzg2_bsp/build/../meta-telephony/recipes-isdn/dahdi-linux/dahdi-linux_3.1.0.bb:do_package) failed with exit code '1' NOTE: Tasks Summary: Attempted 4969 tasks of which 4968 didn't need to be rerun and 1 failed. I've tried these method also "https://www.yoctoproject.org/pipermail/yocto/2016-January/028127.html" "https://stackoverflow.com/questions/49748528/yocto-files-directories-were-installed-but-not-shipped-in-any-package" in **dahdi-linux_3.1.0.bb** file, then also I'm facing same issue. please assist me to solve this. Regard, Prashant Singh |
|
|
|
Marek Belisko
On Thu, Sep 3, 2020 at 8:56 AM <kilian.brandt@...> wrote:
Shared recipe should be the same as one from meta-oe :). So you can include it in your image and it should be build then. BR, marek -- as simple and primitive as possible ------------------------------------------------- Marek Belisko - OPEN-NANDRA Freelance Developer Ruska Nova Ves 219 | Presov, 08005 Slovak Republic Tel: +421 915 052 184 skype: marekwhite twitter: #opennandra web: http://open-nandra.com |
|
|
|
kilian.brandt@...
Hi Khem, thanks for your reply! Now I am a bit confused. Marek has send me another recipe:
Do you know if that is allready fixed for kernel 5,2+ ? Best regards! |
|
|
|
[meta-cgl][PATCH] pacemaker: Fix build with -fno-common
Yu, Mingli
From: Mingli Yu <mingli.yu@...>
Starting with GCC >= 10.x, -fno-common is used as default instead of -fcommon. Make the function definiton extern to fix the build failure. Set the default OCF_ROOT_DIR to $libdir/ocf to make the resource agents components more compatible. Signed-off-by: Mingli Yu <mingli.yu@...> --- .../0001-Mark-declaration-with-extern.patch | 46 +++++++++++++++++++ ...maker-set-OCF_ROOT_DIR-to-libdir-ocf.patch | 32 +++++++++++++ .../recipes-cgl/pacemaker/pacemaker_2.0.3.bb | 2 + 3 files changed, 80 insertions(+) create mode 100644 meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-Mark-declaration-with-extern.patch create mode 100644 meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-pacemaker-set-OCF_ROOT_DIR-to-libdir-ocf.patch diff --git a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-Mark-declaration-with-extern.patch b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-Mark-declaration-with-extern.patch new file mode 100644 index 0000000..5729447 --- /dev/null +++ b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-Mark-declaration-with-extern.patch @@ -0,0 +1,46 @@ +From e1abd3b7c7a0122813e4d0abdb079df10104882c Mon Sep 17 00:00:00 2001 +From: Mingli Yu <mingli.yu@...> +Date: Thu, 3 Sep 2020 04:44:09 +0000 +Subject: [PATCH] Mark declaration with extern + +Fixes build with gcc 10+ + +Upstream-Status: Pending + +Signed-off-by: Mingli Yu <mingli.yu@...> +--- + daemons/attrd/pacemaker-attrd.h | 4 ++-- + daemons/execd/pacemaker-execd.h | 2 +- + 2 files changed, 3 insertions(+), 3 deletions(-) + +diff --git a/daemons/attrd/pacemaker-attrd.h b/daemons/attrd/pacemaker-attrd.h +index cc8e29ee1..76778915e 100644 +--- a/daemons/attrd/pacemaker-attrd.h ++++ b/daemons/attrd/pacemaker-attrd.h +@@ -106,8 +106,8 @@ typedef struct attribute_value_s { + gboolean seen; + } attribute_value_t; + +-crm_cluster_t *attrd_cluster; +-GHashTable *attributes; ++extern crm_cluster_t *attrd_cluster; ++extern GHashTable *attributes; + + #define attrd_send_ack(client, id, flags) \ + crm_ipcs_send_ack((client), (id), (flags), "ack", __FUNCTION__, __LINE__) +diff --git a/daemons/execd/pacemaker-execd.h b/daemons/execd/pacemaker-execd.h +index 4a52d9183..dab3ccdbe 100644 +--- a/daemons/execd/pacemaker-execd.h ++++ b/daemons/execd/pacemaker-execd.h +@@ -20,7 +20,7 @@ + # include <gnutls/gnutls.h> + # endif + +-GHashTable *rsc_list; ++extern GHashTable *rsc_list; + + typedef struct lrmd_rsc_s { + char *rsc_id; +-- +2.26.2 + diff --git a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-pacemaker-set-OCF_ROOT_DIR-to-libdir-ocf.patch b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-pacemaker-set-OCF_ROOT_DIR-to-libdir-ocf.patch new file mode 100644 index 0000000..1ff9c7d --- /dev/null +++ b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker/0001-pacemaker-set-OCF_ROOT_DIR-to-libdir-ocf.patch @@ -0,0 +1,32 @@ +From 3ca78a6441eefc26f18211375b18205ed6fc28c6 Mon Sep 17 00:00:00 2001 +From: Mingli Yu <mingli.yu@...> +Date: Thu, 3 Sep 2020 05:26:36 +0000 +Subject: [PATCH] pacemaker: set OCF_ROOT_DIR to $libdir/ocf + +* Set the default OCF_ROOT_DIR to $libdir/ocf + to make the resource agents components more + compatible + +Upstream-Status: Pending + +Signed-off-by: Mingli Yu <mingli.yu@...> +--- + configure.ac | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/configure.ac b/configure.ac +index 58d39cdc0..eb4275560 100644 +--- a/configure.ac ++++ b/configure.ac +@@ -315,7 +315,7 @@ dnl This defaults to /usr/lib rather than libdir because it's determined by the + dnl OCF project and not pacemaker. Even if a user wants to install pacemaker to + dnl /usr/local or such, the OCF agents will be expected in their usual + dnl location. However, we do give the user the option to override it. +-OCF_ROOT_DIR="/usr/lib/ocf" ++OCF_ROOT_DIR="$libdir/ocf" + AC_ARG_WITH([ocfdir], + [AS_HELP_STRING([--with-ocfdir=DIR], + [OCF resource agent root directory (advanced option: changing this may break other cluster components unless similarly configured) @<:@/usr/lib/ocf@:>@])], +-- +2.26.2 + diff --git a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_2.0.3.bb b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_2.0.3.bb index 9b63acd..56f3bc4 100644 --- a/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_2.0.3.bb +++ b/meta-cgl-common/recipes-cgl/pacemaker/pacemaker_2.0.3.bb @@ -16,6 +16,8 @@ DEPENDS = "corosync libxslt libxml2 gnutls resource-agents libqb python3-native" SRC_URI = "git://github.com/ClusterLabs/${BPN}.git \ file://0006-Fix-tools-Fix-definition-of-curses_indented_printf.patch \ file://0001-Fix-python3-usage.patch \ + file://0001-Mark-declaration-with-extern.patch \ + file://0001-pacemaker-set-OCF_ROOT_DIR-to-libdir-ocf.patch \ file://volatiles \ file://tmpfiles \ " -- 2.26.2 |
|
|
|
Re: Query on building applications and catch exceptions across different shared libraries
On Wed, Sep 2, 2020 at 8:06 PM SIMON BABY <simonkbaby@...> wrote:
OK please add it to your CXXFLAGS and see if it helps.
|
|
|
|
Re: Query on building applications and catch exceptions across different shared libraries
SIMON BABY
No I am not using -fexceptions compiler flag .
toggle quoted message
Show quoted text
Rgds Simon On Wednesday, September 2, 2020, Khem Raj <raj.khem@...> wrote: On Wed, Sep 2, 2020 at 5:18 PM SIMON BABY <simonkbaby@...> wrote: |
|
|
|
Re: Query on building applications and catch exceptions across different shared libraries
On Wed, Sep 2, 2020 at 5:18 PM SIMON BABY <simonkbaby@...> wrote:
are you using -fexceptions to compile your application ? regards |
|
|
|
Query on building applications and catch exceptions across different shared libraries
SIMON BABY
Hello, I have an issue with my throw , catch code in c++. If i throw an error after the openssl library call, my application crashes. If my application wishes to throw and catch exceptions across different shared libraries do we have any specific settings I can add in my bitbake recipe? regards Simon |
|
|
|
On Wed, Sep 2, 2020 at 4:32 AM Marek Belisko <marek.belisko@...> wrote:
in this case you might be lucky we already have recipe http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/socketcan/can-isotp_git.bb?h=master its blacklisted because it needs work to fix build on 5.2+ kernel I would really appreciate any help ! Best regards,marek |
|
|
|
Marek Belisko
On Wed, Sep 2, 2020 at 1:13 PM <kilian.brandt@...> wrote:
PLease take a look at : https://www.yoctoproject.org/docs/2.6/kernel-dev/kernel-dev.html#working-with-out-of-tree-modules where it is described how to compile out of tree modules. marek |
|
|
|
kilian.brandt@...
Hey community,
I'm trying to use this library [can-isotp][1] on a Jetson TX2 Board. The version of the running OS is: 0.0.8 (dunfell).
From the docs of the library I get the following instructions:
```
DOWNLOAD and BUILD
1. Download repository and enter the repositories root directory
git clone https://github.com/hartkopp/can-isotp.git
cd can-isotp
2. Build ISO-TP kernel module
Ensure build dependencies are installed. E.g. for Debian (or Ubuntu):
sudo apt-get install build-essential linux-headers-$(uname -r)
To build:
(you need to be in the repositories root path)
make
To install (optional):
sudo make modules_install
3. When the PF_CAN core module is loaded ('modprobe can') the ISO-TP module
can be loaded into the kernel with
insmod ./net/can/can-isotp.ko
When the can-isotp.ko module has been installed into the Linux Kernels
modules directory (e.g. with 'make modules_install') the module should
load automatically when opening a CAN_ISOTP socket.
```
I have some questions about that procedure. Can anybody give me an hint on how to install this module? Do I have to create a completly new yocto image or is there any way to install kernel modules afterwards? I tried to copy the folder onto the TX2 and install it by hand, but (as to be expected) the make command is not found. I would really appreciate any help ! Best regards, [1]: https://github.com/hartkopp/can-isotp |
|
|
|
[PATCH yocto-autobuilder-helper] scripts/send-qa-email: Update to dedicated push capable domain
Michael Halstead
Signed-off-by: Michael Halstead <mhalstead@...>
--- scripts/send-qa-email | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/send-qa-email b/scripts/send-qa-email index abc17e2..f38c876 100755 --- a/scripts/send-qa-email +++ b/scripts/send-qa-email @@ -70,10 +70,10 @@ if 'poky' in repos and os.path.exists(resulttool) and args.results_dir: elif basebranch: cloneopts = ["--branch", basebranch] try: - subprocess.check_call(["git", "clone", "git@...:yocto-testresults", tempdir, "--depth", "5"] + cloneopts) + subprocess.check_call(["git", "clone", "git@...:yocto-testresults", tempdir, "--depth", "5"] + cloneopts) except subprocess.CalledProcessError: print("No comparision branch found, falling back to master") - subprocess.check_call(["git", "clone", "git@...:yocto-testresults", tempdir, "--depth", "5"]) + subprocess.check_call(["git", "clone", "git@...:yocto-testresults", tempdir, "--depth", "5"]) # If the base comparision branch isn't present regression comparision won't work # at least until we can tell the tool to ignore internal branch information -- 2.26.2 |
|
|
|
Yocto Project Status WW35'20
Stephen Jolley
Current Dev Position: YP 3.2 M3 Next Deadline: YP 3.2 M3 Feature Freeze - Now
Next Team Meetings:
Key Status/Updates:
You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.
YP 3.2 Milestone Dates:
Planned upcoming dot releases:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|
|
|
Re: Recipies version of incoming October Gatesgarth release.
On Tue, 1 Sep 2020 at 13:16, Yocto_user <avinashyadav94it@...> wrote:
I don't think any of us have crystal balls to predict the exact package versions we'll be using in October for the next release. We're close to the feature freeze point but high priority recipe updates could still be taken after that time. Why do you think you need this information? If you explain your concerns hopefully we can find a different way to provide the answers you need. -- Paul Barker Konsulko Group |
|
|
|
Recipies version of incoming October Gatesgarth release.
Yocto_user
Hi,
Is there any way to know all the recipes version detail that will come with Yocto 3.2 Gatesgarth ?? |
|
|