Date   

How to add Percona Server for MySQL to poky 2.7.1

B.Sathish Kumar
 

Hi,

Does anyone have tried adding Percona Server for MySQL to poky 2.7.1 ?
URL reference - https://www.percona.com/doc/percona-server/8.0/installation.html

Any suggestion to (easily) include this package with its dependencies ?

Thanks.
::DISCLAIMER::
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
________________________________


[meta-security][PATCH] bastille: Deleted redundant inherit to fix error when enable multilib.

zhengruoqin
 

There is no need to inherit module-base. Because this inherit will stop
bastille to build to lib32-bastille.

Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
---
recipes-security/bastille/bastille_3.2.1.bb | 2 --
1 file changed, 2 deletions(-)

diff --git a/recipes-security/bastille/bastille_3.2.1.bb b/recipes-security/bastille/bastille_3.2.1.bb
index e9accb5..0290cae 100644
--- a/recipes-security/bastille/bastille_3.2.1.bb
+++ b/recipes-security/bastille/bastille_3.2.1.bb
@@ -9,8 +9,6 @@ DEPENDS = "virtual/kernel"
RDEPENDS_${PN} = "perl bash tcl perl-module-getopt-long perl-module-text-wrap lib-perl perl-module-file-path perl-module-mime-base64 perl-module-file-find perl-module-errno perl-module-file-glob perl-module-tie-hash-namedcapture perl-module-file-copy perl-module-english perl-module-exporter perl-module-cwd libcurses-perl coreutils"
FILES_${PN} += "/run/lock/subsys/bastille"

-inherit module-base
-
SRC_URI = "http://sourceforge.net/projects/bastille-linux/files/bastille-linux/3.2.1/Bastille-3.2.1.tar.bz2 \
file://AccountPermission.pm \
file://FileContent.pm \
--
2.17.1


[ptest-runner][PATCH v2] Fix inappropriate ioctl when detaching tty

Tero Kinnunen
 

Fixes error

ERROR: Unable to detach from controlling tty, Inappropriate ioctl for device

when running multiple ptests

ptest-runner a b

or when invoked over ssh single command, like

$ ssh localhost ptest-runner

For ssh case, fd 0 is not a tty. (isatty(0) is false).
When running multiple ptests, deattach for parent needs to be
done only once.

Signed-off-by: Tero Kinnunen <tero.kinnunen@vaisala.com>
---
utils.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/utils.c b/utils.c
index a8ba190..a4e190e 100644
--- a/utils.c
+++ b/utils.c
@@ -437,6 +437,9 @@ run_ptests(struct ptest_list *head, const struct ptest_options opts,
break;
}
fprintf(fp, "START: %s\n", progname);
+ if (isatty(0) && ioctl(0, TIOCNOTTY) == -1) {
+ fprintf(fp, "ERROR: Unable to detach from controlling tty, %s\n", strerror(errno));
+ }
PTEST_LIST_ITERATE_START(head, p)
char *ptest_dir = strdup(p->run_ptest);
if (ptest_dir == NULL) {
@@ -444,9 +447,6 @@ run_ptests(struct ptest_list *head, const struct ptest_options opts,
break;
}
dirname(ptest_dir);
- if (ioctl(0, TIOCNOTTY) == -1) {
- fprintf(fp, "ERROR: Unable to detach from controlling tty, %s\n", strerror(errno));
- }

if ((pgid = getpgid(0)) == -1) {
fprintf(fp, "ERROR: getpgid() failed, %s\n", strerror(errno));
--
2.25.1


Upgrading a group of packages

aensminger@...
 

Hello! I'm new to yocto, and working in an inherited system, and a first time poster, so forgive any ignorance.

I'm looking for a way to group packages together, and specify the sub-package versions such that you can upgrade them all together. My approach so far has been to create a group package, let's say in a recipe called group-one_1.0.bb.  This recipe has PR = "r1" defines RDEPENDS = "package-a (=1.0) package-b (=1.3)" as a way of making sure these are installed with the specified versions. We use opkg as the package manager, so I am expecting `opkg install group-one` to also install/upgrade package-a to 1.0 and package-b to 1.3, but it's not doing that. If package-b is already installed at 1.0, it stays at 1.0.

Is there some built-in approach to this type of organization, or some best-practices around the way to go about it?

Thanks much,
Alex Ensminger


Re: Add application with library to target

Khem Raj
 

On 7/8/20 2:37 AM, Kjeld Flarup via lists.yoctoproject.org wrote:
I have a functioning Yocto build today, but two of the recipes are
optional. An application and a library.
I would like to split my build in two. 

One that contains the basic system with kernel rootfs etc.
A second that just contains the application and the library

If I just had the application, it would be simple just to use the SDK
and generate the application. 
But when adding the library, things starts to be more complex. 

I would also like to use my existing recipe with dependencies etc. 

What is the best approach

* Can this be done with the ADT?
* Can a layer solve it
* Do I need to do it all manually with the SDK
I think eSDK might be good fit for your usecase.

https://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-extensible

--
Regards 
Kjeld Flarup
DEIF A/S



Re: [ptest-runner][PATCH] Fix inappropriate ioctl when detaching tty

Anibal Limon
 



On Wed, 8 Jul 2020 at 01:46, Tero Kinnunen <tero.kinnunen@...> wrote:
On Tue, Jul 7, 2020 at 06:49 AM, Anibal Limon wrote:
First thanks for the patch, Is there an option to test for isatty(fd) for run ioctl instead?.
Hi Anibal,

    if (isatty(0) && ioctl(0, TIOCNOTTY) == -1)

would help for ssh case but not to errors between tests. There fd 0 is a tty but detach should
be done only once. Now it is inside loop. It could work if it was also moved outside the loop,
before PTEST_LIST_ITERATE_START?

Agree, Add isatty(0) and move that validation outside the loop.

Anibal
 

Kind regards,

    - Tero


DNF package reinstallation

Hugh Boddington
 

I’ve got a fresh image, hot off the press with a clean install from dunfell (febbe2944c…).  I deploy it to my target machine as a fresh install, overwriting the whole storage array.  I’m using DNF as my package manager and I copy the packages from the build output to my web server.  On the target machine, I run ‘dnf upgrade’ and it hits the package repo and tells me that there’s a number of packages that need to be ‘reinstalled’.  No upgrades, conflicts etc – just reinstalled.  The packages don’t appear to have much in common – some are packages from my layers, some are unmodified poky packages.  I cannot figure out why dnf thinks they need to be reinstalled when it’s a fresh install and there’s only one version of everything.  I also can’t figure out the magic incantation to get dnf to tell me how it arrived at this conclusion.

 

Can anyone shed any light on this problem?  It’s driving me mad.  If I allow it to reinstall the packages and re-run ‘dnf upgrade’ I just get the same reinstallation list.


Re: ERROR: iso-codes-4.4-r0

Mikko Rapeli
 

Hi,

On Wed, Jul 08, 2020 at 07:52:30AM -0700, Pankaj Vinadrao Joshi wrote:
I am trying to build yocto image for RPI4 but i am getting following error

pankaj@exaleap-Inspiron-3584:~/raspberrypi4_image$ bitbake core-image-sato
Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:09:59
Parsing of 2198 .bb files complete (0 cached, 2198 parsed). 3282 targets, 147 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.46.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "raspberrypi4"
DISTRO               = "poky"
DISTRO_VERSION       = "3.1"
TUNE_FEATURES        = "arm vfp cortexa7 neon vfpv4 thumb callconvention-hard"
TARGET_FPU           = "hard"
meta
meta-poky
meta-yocto-bsp       = "dunfell:9c8049068406532c3dd5d8906c595218b0fefd40"
meta-oe
meta-python
meta-networking
meta-multimedia      = "dunfell:e413c1ef621688e69bb7830bb3151ed23b30b73e"
meta-raspberrypi     = "master:5ac6f013339b0b1ab2d71f9f6af48a186e126c19"

Initialising tasks: 100% |###################################################################################################################################################################| Time: 0:00:18
Sstate summary: Wanted 1395 Found 0 Missed 1395 Current 1738 (0% match, 55% complete)
NOTE: Executing Tasks
WARNING: iso-codes-4.4-r0 do_fetch: Failed to fetch URL git://salsa.debian.org/iso-codes-team/iso-codes.git;protocol=http, attempting MIRRORS if available
ERROR: iso-codes-4.4-r0 do_fetch: Fetcher failure: Unable to find revision 38edb926592954b87eb527124da0ec68d2a748f3 in branch master even from upstream
ERROR: iso-codes-4.4-r0 do_fetch: Fetcher failure for URL: 'git://salsa.debian.org/iso-codes-team/iso-codes.git;protocol=http'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/pankaj/raspberrypi4_image/tmp/work/all-poky-linux/iso-codes/4.4-r0/temp/log.do_fetch.24501
ERROR: Task (/home/pankaj/Yocto-practice/poky/meta/recipes-support/iso-codes/iso-codes_4.4.bb:do_fetch) failed with exit code '1'

can someone help me how i can resolve this error?
Debian developers changed branch names in their repository.

Fixed in latest master and dunfell branches so either update or cherry-pick the
changes:

https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=dunfell&id=c253fd28ad26b4996666b0794dfee1d59c14e3ca

https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=75e91b8e52ec77398e6b0fc09456e971662d9d7e

Cheers,

-Mikko


Re: ERROR: iso-codes-4.4-r0

Quentin Schulz
 

Hi Pankaj,

On Wed, Jul 08, 2020 at 07:52:30AM -0700, Pankaj Vinadrao Joshi wrote:
I am trying to build yocto image for RPI4 but i am getting following error

pankaj@exaleap-Inspiron-3584:~/raspberrypi4_image$ bitbake core-image-sato
Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:09:59
Parsing of 2198 .bb files complete (0 cached, 2198 parsed). 3282 targets, 147 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.46.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "raspberrypi4"
DISTRO               = "poky"
DISTRO_VERSION       = "3.1"
TUNE_FEATURES        = "arm vfp cortexa7 neon vfpv4 thumb callconvention-hard"
TARGET_FPU           = "hard"
meta
meta-poky
meta-yocto-bsp       = "dunfell:9c8049068406532c3dd5d8906c595218b0fefd40"
meta-oe
meta-python
meta-networking
meta-multimedia      = "dunfell:e413c1ef621688e69bb7830bb3151ed23b30b73e"
meta-raspberrypi     = "master:5ac6f013339b0b1ab2d71f9f6af48a186e126c19"

Initialising tasks: 100% |###################################################################################################################################################################| Time: 0:00:18
Sstate summary: Wanted 1395 Found 0 Missed 1395 Current 1738 (0% match, 55% complete)
NOTE: Executing Tasks
WARNING: iso-codes-4.4-r0 do_fetch: Failed to fetch URL git://salsa.debian.org/iso-codes-team/iso-codes.git;protocol=http, attempting MIRRORS if available
ERROR: iso-codes-4.4-r0 do_fetch: Fetcher failure: Unable to find revision 38edb926592954b87eb527124da0ec68d2a748f3 in branch master even from upstream
ERROR: iso-codes-4.4-r0 do_fetch: Fetcher failure for URL: 'git://salsa.debian.org/iso-codes-team/iso-codes.git;protocol=http'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/pankaj/raspberrypi4_image/tmp/work/all-poky-linux/iso-codes/4.4-r0/temp/log.do_fetch.24501
ERROR: Task (/home/pankaj/Yocto-practice/poky/meta/recipes-support/iso-codes/iso-codes_4.4.bb:do_fetch) failed with exit code '1'

can someone help me how i can resolve this error?
Update your dunfell branch (should be at commit
c253fd28ad26b4996666b0794dfee1d59c14e3ca)

Quentin


ERROR: iso-codes-4.4-r0

Pankaj Vinadrao Joshi
 

I am trying to build yocto image for RPI4 but i am getting following error 

pankaj@exaleap-Inspiron-3584:~/raspberrypi4_image$ bitbake core-image-sato
Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:09:59
Parsing of 2198 .bb files complete (0 cached, 2198 parsed). 3282 targets, 147 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
 
Build Configuration:
BB_VERSION           = "1.46.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "raspberrypi4"
DISTRO               = "poky"
DISTRO_VERSION       = "3.1"
TUNE_FEATURES        = "arm vfp cortexa7 neon vfpv4 thumb callconvention-hard"
TARGET_FPU           = "hard"
meta                 
meta-poky            
meta-yocto-bsp       = "dunfell:9c8049068406532c3dd5d8906c595218b0fefd40"
meta-oe              
meta-python          
meta-networking      
meta-multimedia      = "dunfell:e413c1ef621688e69bb7830bb3151ed23b30b73e"
meta-raspberrypi     = "master:5ac6f013339b0b1ab2d71f9f6af48a186e126c19"
 
Initialising tasks: 100% |###################################################################################################################################################################| Time: 0:00:18
Sstate summary: Wanted 1395 Found 0 Missed 1395 Current 1738 (0% match, 55% complete)
NOTE: Executing Tasks
WARNING: iso-codes-4.4-r0 do_fetch: Failed to fetch URL git://salsa.debian.org/iso-codes-team/iso-codes.git;protocol=http, attempting MIRRORS if available
ERROR: iso-codes-4.4-r0 do_fetch: Fetcher failure: Unable to find revision 38edb926592954b87eb527124da0ec68d2a748f3 in branch master even from upstream
ERROR: iso-codes-4.4-r0 do_fetch: Fetcher failure for URL: 'git://salsa.debian.org/iso-codes-team/iso-codes.git;protocol=http'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/pankaj/raspberrypi4_image/tmp/work/all-poky-linux/iso-codes/4.4-r0/temp/log.do_fetch.24501
ERROR: Task (/home/pankaj/Yocto-practice/poky/meta/recipes-support/iso-codes/iso-codes_4.4.bb:do_fetch) failed with exit code '1'

can someone help me how i can resolve this error?


Re: Configuring UIO to handle GPIO interrupt #yocto #linux

Quentin Schulz
 

Hi Scott,

On Wed, Jul 08, 2020 at 07:15:17AM -0700, sdw@inea.com wrote:
Dear Yocto community,

I am hoping that you can provide advice on configuring UIO to handle a GPIO interrupt from user space. I found an excellent summary at https://yurovsky.github.io/2014/10/10/linux-uio-gpio-interrupt.html and have tried to follow it as well as I can, being a newcomer to Yocto and embedded Linux.

We are using a Variscite DART-MX8M-MINI development kit, with the i.MX8M Mini processor on a System-on-Module. I have enabled spidev, which I am using to communicate with an ADS1299 EEG analog front end from TI. It generates a “data ready” interrupt DRDY# (active low). I’d like to be able to handle this falling-edge interrupt by connecting it to a GPIO (GPIO1_0) and either read() or poll() to wait for an interrupt, and can then read the acquired data using /dev/spidev0.0.

In my device tree, I have added the following under my &ecspi1 node. I am not certain this is the correct place to add this information, or if I can simply add it within the device tree “root” node “/ {“. I would appreciate your advice on the best place add this information!
// Added for DRDY# interrupt on GPIO1_0 from user space
user_io@0 {
compatible = "mydevice,generic-uio,ui_pdrv";
status = "okay";
interrupt-parent = <&gpio1>;
interrupts = <0 IRQ_TYPE_EDGE_FALLING>;
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_user_io>;
};

Under my dts &iomuxc node, the various pinctrl groups are defined. I added the following for GPIO1_0:
// Added for DRDY# interrupt on GPIO1_0 from user space
pinctrl_user_io: user_io-0 {
fsl,pins = <
MX8MM_IOMUXC_GPIO1_IO00_GPIO1_IO0 0x1c0
>;
};
This should configure the pin to enable a pull-up.

I have modified my kernel .config file via 'bitbake -c menuconfig virtual/kernel', and it contains the following entries:
CONFIG_UIO=y
CONFIG_UIO_PDRV_GENIRQ=m

The “y” setting for CONFIG_UIO was evidently due to other dependencies in the provided configuration. I then built the SD card image using 'bitbake fsl-image-qt5', and programmed it onto my SD card.
Up till there, this discussion would probably fit some kernel
communities more than the Yocto one.

A few things though:

- Bear in mind that using bitbake -c menuconfig virtual/kernel, the
changes aren't permanent. If there's a clean rebuild of the kernel for
some reason, your changes will be overwritten, you need to create a
patch for it (or take a defconfig) and add it to your kernel recipe (or
fork the kernel repo and add your own defconfig),

- Modules aren't shipped by default by Yocto, so you need either to
add kernel-modules to IMAGE_INSTALL or probably smarter to have it in
your machine configuration file in MACHINE_EXTRA_RRECOMMENDS, this will
install **all** kernel modules created by yocto,
or just add kernel-module-uio-pdrv-genirq (probably, don't know the exact
name of it) the same way to only have uio,

Quentin


Configuring UIO to handle GPIO interrupt #yocto #linux

sdw@...
 

Dear Yocto community,

I am hoping that you can provide advice on configuring UIO to handle a GPIO interrupt from user space. I found an excellent summary at https://yurovsky.github.io/2014/10/10/linux-uio-gpio-interrupt.html and have tried to follow it as well as I can, being a newcomer to Yocto and embedded Linux.

We are using a Variscite DART-MX8M-MINI development kit, with the i.MX8M Mini processor on a System-on-Module. I have enabled spidev, which I am using to communicate with an ADS1299 EEG analog front end from TI. It generates a “data ready” interrupt DRDY# (active low). I’d like to be able to handle this falling-edge interrupt by connecting it to a GPIO (GPIO1_0) and either read() or poll() to wait for an interrupt, and can then read the acquired data using /dev/spidev0.0.

In my device tree, I have added the following under my &ecspi1 node. I am not certain this is the correct place to add this information, or if I can simply add it within the device tree “root” node “/ {“. I would appreciate your advice on the best place add this information!
// Added for DRDY# interrupt on GPIO1_0 from user space
user_io@0 {
compatible = "mydevice,generic-uio,ui_pdrv";
status = "okay";
interrupt-parent = <&gpio1>;
interrupts = <0 IRQ_TYPE_EDGE_FALLING>;
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_user_io>;
};

Under my dts &iomuxc node, the various pinctrl groups are defined. I added the following for GPIO1_0:
// Added for DRDY# interrupt on GPIO1_0 from user space
pinctrl_user_io: user_io-0 {
fsl,pins = <
MX8MM_IOMUXC_GPIO1_IO00_GPIO1_IO0 0x1c0
>;
};
This should configure the pin to enable a pull-up.

I have modified my kernel .config file via 'bitbake -c menuconfig virtual/kernel', and it contains the following entries:
CONFIG_UIO=y
CONFIG_UIO_PDRV_GENIRQ=m

The “y” setting for CONFIG_UIO was evidently due to other dependencies in the provided configuration. I then built the SD card image using 'bitbake fsl-image-qt5', and programmed it onto my SD card.

However, when I boot the board up, I cannot see /dev/uio0 or run the modprobe command as specified in the description at the link provided above:
root@imx8mm-var-dart:~# ls /dev/u*
/dev/ubi_ctrl /dev/udev_network_queue /dev/uhid /dev/uinput /dev/urandom root@imx8mm-var-dart:~# modprobe uio_pdrv_genirq of_id="mydevice,generic-uio,ui_pdrv"
modprobe: FATAL: Module uio_pdrv_genirq not found in directory /lib/modules/4.19.35-imx8mm+ge6d3e3fefe4e

I used grep to look for “uio” in the /lib/modules directory, and only found the following:
root@imx8mm-var-dart:/lib/modules/4.19.35-imx8mm+ge6d3e3fefe4e# grep -RnI uio .
./modules.builtin:270:kernel/drivers/uio/uio.ko

I am stumped, and think I must have something wrong in my .dts file, my .config file, or in the packages/libraries added to the Yocto image. Do you have any suggestions for how to diagnose/fix this problem? I can provide my .config file, .dts file, or any other information, but I am not sure how they should be added for access by the group.

UIO apparently is a "preferred" way to handle writing simple device drivers from user space. Do I need to add something to Yocto to enable UIO and UIO_PDRV_GENIRQ?

Thank you for your help, and kind regards,
Scott


Re: Broken dunfell branch

Stefano Babic
 

Hi Guy,

On 08.07.20 15:15, Guy Morand wrote:
Hallo Yocto deveopers!

For our daily release, we build from the latest dunfell branch. I would
like to thank and congratulate you because we have been doing so for
over a year and the build never broke because of poky/OE meta layers!

However, we recently got some errors:

ERROR: mtd-utils-2.1.1-r0 do_patch: Command Error: 'quilt --quiltrc
/mnt/sdb/buildAgent/work/8161e17a85bb6b69/build/tmp/work/armv7vet2hf-neon-scewo-linux-gnueabi/mtd-utils/2.1.1-r0/recipe-sysroot-native/etc/quiltrc
push' exited with 0  Output:
Applying patch 0001-mtd-utils-Fix-return-value-of-ubiformat.patch
patching file ubi-utils/ubiformat.c
Hunk #1 FAILED at 550.
Hunk #2 FAILED at 643.
Hunk #3 FAILED at 669.
3 out of 3 hunks FAILED -- rejects in file ubi-utils/ubiformat.c
Patch 0001-mtd-utils-Fix-return-value-of-ubiformat.patch can be
reverse-applied
ERROR: Logfile of failure stored in:
/mnt/sdb/buildAgent/work/8161e17a85bb6b69/build/tmp/work/armv7vet2hf-neon-scewo-linux-gnueabi/mtd-utils/2.1.1-r0/temp/log.do_patch.23641

ERROR: Task
(/mnt/sdb/buildAgent/work/8161e17a85bb6b69/meta-layers/poky/meta/recipes-devtools/mtd/mtd-utils_git.bb:do_patch)
failed with exit code '1'

It seems the faulty commit is:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=dunfell&id=994783b52e5c0a97000b8b643c8fd80d81069097


For now I simply build from the previous commit and everything is fine.
Not sure if someone already noticed that or if there is something wrong
with my setup?
Do you have meta-swupdate in your layers, too, and are you using -master
(see commit ece400ed5) ?

Best regards,
Stefano Babic

Best regards,

Guy Morand



--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================


Re: Broken dunfell branch

Martin Jansa
 

This 0001-mtd-utils-Fix-return-value-of-ubiformat.patch patch was recently backported to dunfell in

check with "bitbake -e mtd-utils" to see which other layer in your build adds the same patch or changes SRCREV to newer commit which already contains the same change from upstream.

On Wed, Jul 8, 2020 at 3:15 PM Guy Morand <guy@...> wrote:
Hallo Yocto deveopers!

For our daily release, we build from the latest dunfell branch. I would
like to thank and congratulate you because we have been doing so for
over a year and the build never broke because of poky/OE meta layers!

However, we recently got some errors:

ERROR: mtd-utils-2.1.1-r0 do_patch: Command Error: 'quilt --quiltrc
/mnt/sdb/buildAgent/work/8161e17a85bb6b69/build/tmp/work/armv7vet2hf-neon-scewo-linux-gnueabi/mtd-utils/2.1.1-r0/recipe-sysroot-native/etc/quiltrc
push' exited with 0  Output:
Applying patch 0001-mtd-utils-Fix-return-value-of-ubiformat.patch
patching file ubi-utils/ubiformat.c
Hunk #1 FAILED at 550.
Hunk #2 FAILED at 643.
Hunk #3 FAILED at 669.
3 out of 3 hunks FAILED -- rejects in file ubi-utils/ubiformat.c
Patch 0001-mtd-utils-Fix-return-value-of-ubiformat.patch can be
reverse-applied
ERROR: Logfile of failure stored in:
/mnt/sdb/buildAgent/work/8161e17a85bb6b69/build/tmp/work/armv7vet2hf-neon-scewo-linux-gnueabi/mtd-utils/2.1.1-r0/temp/log.do_patch.23641
ERROR: Task
(/mnt/sdb/buildAgent/work/8161e17a85bb6b69/meta-layers/poky/meta/recipes-devtools/mtd/mtd-utils_git.bb:do_patch)
failed with exit code '1'

It seems the faulty commit is:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=dunfell&id=994783b52e5c0a97000b8b643c8fd80d81069097

For now I simply build from the previous commit and everything is fine.
Not sure if someone already noticed that or if there is something wrong
with my setup?

Best regards,

Guy Morand


Broken dunfell branch

Guy Morand <guy@...>
 

Hallo Yocto deveopers!

For our daily release, we build from the latest dunfell branch. I would like to thank and congratulate you because we have been doing so for over a year and the build never broke because of poky/OE meta layers!

However, we recently got some errors:

ERROR: mtd-utils-2.1.1-r0 do_patch: Command Error: 'quilt --quiltrc /mnt/sdb/buildAgent/work/8161e17a85bb6b69/build/tmp/work/armv7vet2hf-neon-scewo-linux-gnueabi/mtd-utils/2.1.1-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0 Output:
Applying patch 0001-mtd-utils-Fix-return-value-of-ubiformat.patch
patching file ubi-utils/ubiformat.c
Hunk #1 FAILED at 550.
Hunk #2 FAILED at 643.
Hunk #3 FAILED at 669.
3 out of 3 hunks FAILED -- rejects in file ubi-utils/ubiformat.c
Patch 0001-mtd-utils-Fix-return-value-of-ubiformat.patch can be reverse-applied
ERROR: Logfile of failure stored in: /mnt/sdb/buildAgent/work/8161e17a85bb6b69/build/tmp/work/armv7vet2hf-neon-scewo-linux-gnueabi/mtd-utils/2.1.1-r0/temp/log.do_patch.23641
ERROR: Task (/mnt/sdb/buildAgent/work/8161e17a85bb6b69/meta-layers/poky/meta/recipes-devtools/mtd/mtd-utils_git.bb:do_patch) failed with exit code '1'

It seems the faulty commit is:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=dunfell&id=994783b52e5c0a97000b8b643c8fd80d81069097

For now I simply build from the previous commit and everything is fine. Not sure if someone already noticed that or if there is something wrong with my setup?

Best regards,

Guy Morand


Add application with library to target

Kjeld Flarup
 

I have a functioning Yocto build today, but two of the recipes are optional. An application and a library.
I would like to split my build in two. 

One that contains the basic system with kernel rootfs etc.
A second that just contains the application and the library

If I just had the application, it would be simple just to use the SDK and generate the application. 
But when adding the library, things starts to be more complex. 

I would also like to use my existing recipe with dependencies etc. 

What is the best approach
  • Can this be done with the ADT?
  • Can a layer solve it
  • Do I need to do it all manually with the SDK

--
Regards 
Kjeld Flarup
DEIF A/S


Re: iso-codes project

Martin Jansa
 

Hi,

having both would be useful, but you have to ask upstream iso-codes developers why they also removed master, OE DL_DIR just followed what they did in upstream, which unfortunately includes pruning the master branch, still referenced by older releases.

Cheers,

On Wed, Jul 8, 2020 at 8:55 AM Michael Nazzareno Trimarchi <michael@...> wrote:
Hi Martin

On Wed, Jul 8, 2020 at 8:36 AM Martin Jansa <martin.jansa@...> wrote:
>
> Hi,
>
> it's know issue already fixed in master, see
> https://lists.openembedded.org/g/openembedded-architecture/message/1108
> thud is pretty much out of support and probably won't be fixed there, you should be able to easily fix it from .bbappend in one of your layers.
>

Why just don't continue to have both? I think was even re-history. I
will give a try

Michael

> Regards,
>
> On Wed, Jul 8, 2020 at 7:57 AM Michael Nazzareno Trimarchi <michael@...> wrote:
>>
>> Hi all
>>
>> anyone has problem on iso-codes in thud. Seems that project was
>> changed and not possible to download with the actual configuration
>>
>> Michael
>>
>> --
>> | Michael Nazzareno Trimarchi                     Amarula Solutions BV |
>> | COO  -  Founder                                      Cruquiuskade 47 |
>> | +31(0)851119172                                 Amsterdam 1018 AM NL |
>> |                  [`as] http://www.amarulasolutions.com               |
>>



--
| Michael Nazzareno Trimarchi                     Amarula Solutions BV |
| COO  -  Founder                                      Cruquiuskade 47 |
| +31(0)851119172                                 Amsterdam 1018 AM NL |
|                  [`as] http://www.amarulasolutions.com               |


Re: iso-codes project

Michael Nazzareno Trimarchi
 

Hi Martin

On Wed, Jul 8, 2020 at 8:36 AM Martin Jansa <martin.jansa@gmail.com> wrote:

Hi,

it's know issue already fixed in master, see
https://lists.openembedded.org/g/openembedded-architecture/message/1108
thud is pretty much out of support and probably won't be fixed there, you should be able to easily fix it from .bbappend in one of your layers.
Why just don't continue to have both? I think was even re-history. I
will give a try

Michael

Regards,

On Wed, Jul 8, 2020 at 7:57 AM Michael Nazzareno Trimarchi <michael@amarulasolutions.com> wrote:

Hi all

anyone has problem on iso-codes in thud. Seems that project was
changed and not possible to download with the actual configuration

Michael

--
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO - Founder Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
| [`as] http://www.amarulasolutions.com |


--
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO - Founder Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
| [`as] http://www.amarulasolutions.com |


Re: [ptest-runner][PATCH] Fix inappropriate ioctl when detaching tty

Tero Kinnunen
 

On Tue, Jul 7, 2020 at 06:49 AM, Anibal Limon wrote:
First thanks for the patch, Is there an option to test for isatty(fd) for run ioctl instead?.
Hi Anibal,

    if (isatty(0) && ioctl(0, TIOCNOTTY) == -1)

would help for ssh case but not to errors between tests. There fd 0 is a tty but detach should
be done only once. Now it is inside loop. It could work if it was also moved outside the loop,
before PTEST_LIST_ITERATE_START?

Kind regards,

    - Tero


Re: iso-codes project

Masahiko Kimoto
 

The project seems to change master branch name to 'main'.

Please try to add ';branch=main' into SRC_URI.

Regards,

From: "Michael Nazzareno Trimarchi" <michael@amarulasolutions.com>
Subject: [yocto] iso-codes project
Date: Wed, 8 Jul 2020 07:56:44 +0200

> Hi all
>
> anyone has problem on iso-codes in thud. Seems that project was
> changed and not possible to download with the actual configuration
>
> Michael
>
> --
> | Michael Nazzareno Trimarchi Amarula Solutions BV |
> | COO - Founder Cruquiuskade 47 |
> | +31(0)851119172 Amsterdam 1018 AM NL |
> | [`as] http://www.amarulasolutions.com |

----------------------------------------------------------------------
木本 雅彦 / Masahiko Kimoto, Ph.D.
E-mail: kimoto@ohnolab.org URL: http://www.ohnolab.org/~kimoto

3541 - 3560 of 53453