Date   

Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

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 the triage page under the appropriate heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 392 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.4”, “3.5, "3.99" and "Future", the more pressing/urgent issues being in "3.4" and then “3.5”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am on the first Tuesday (PDT)

Stephen Jolley
 

All,

 

Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (10/5) 

 

Yocto Project Technical Team Meeting: We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional):

Yocto IRC: https://web.libera.chat/#yocto 

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

 

When            Monthly from 8am to 9am on the first Tuesday Pacific Time

Where           Zoom Meeting: https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09

 

We are tracking the minutes at: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit?pli=1 Please request access if you want to assist in editing them.  The world should have view access.

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: virtual/egl on Raspberry Pi 4

Khem Raj
 

It should have automatically found user land package as one of providers but if it is not doing so that means it’s being ignored because it’s not compatible arch or something 
Are you compiling 32bit mode ? 


On Mon, Oct 4, 2021 at 4:08 PM Greg Wilson-Lindberg <GWilson@...> wrote:
Hi Khem,
Yes, the Raspberry Pi boards do use closed source drivers. What I need is how do I include the proper package that will bring in the necessary virtual/egl for the Raspberry Pi 4.

Greg
> -----Original Message-----
> From: Khem Raj <raj.khem@...>
> Sent: Monday, October 4, 2021 14:17
> To: Greg Wilson-Lindberg <GWilson@...>;
> yocto@...
> Subject: Re: [yocto] virtual/egl on Raspberry Pi 4
>
>
>
> On 10/4/21 12:39 PM, Greg Wilson-Lindberg wrote:
> > Hello list,
> >
> > I'm working on a Qt supplied boot2qt Yocto build currently based on
> > Zeus that is running on a Raspberry Pi 4. I recently updated the qt
> > version to 5.15.6 and Qt changed something in the Yocto configuration
> > that they are using and now one of the recipes that we use is failing
> > saying that in needs 'virtual/egl' but that it is not provided by any recipe.
> >
> > In the searching that I have done I have found that the raspberry pi 4
> > is particular on which package supplies the virtual/egl but I haven't
> > seen anything that indicates what I should do to re-enable it.
> >
> > Can anyone tell me what I need to do to enable the correct driver to
> > get virtual/egl provided on the Raspberry Pi 4? Or maybe even better,
> > how I could search through the packages that are enabled on the old
> > and new Yocto trees so that I can figure out what changed between the
> > releases and re-enable the virtual/egl.
> >
>
> it should be provided by userland package if you are using closed source
> graphics driver.
>
> > Best Regards,
> >
> > Greg Wilson-Lindberg
> >
> >
> >
> >
> >


Re: virtual/egl on Raspberry Pi 4

Greg Wilson-Lindberg
 

Hi Khem,
Yes, the Raspberry Pi boards do use closed source drivers. What I need is how do I include the proper package that will bring in the necessary virtual/egl for the Raspberry Pi 4.

Greg

-----Original Message-----
From: Khem Raj <raj.khem@...>
Sent: Monday, October 4, 2021 14:17
To: Greg Wilson-Lindberg <GWilson@...>;
yocto@...
Subject: Re: [yocto] virtual/egl on Raspberry Pi 4



On 10/4/21 12:39 PM, Greg Wilson-Lindberg wrote:
Hello list,

I'm working on a Qt supplied boot2qt Yocto build currently based on
Zeus that is running on a Raspberry Pi 4. I recently updated the qt
version to 5.15.6 and Qt changed something in the Yocto configuration
that they are using and now one of the recipes that we use is failing
saying that in needs 'virtual/egl' but that it is not provided by any recipe.

In the searching that I have done I have found that the raspberry pi 4
is particular on which package supplies the virtual/egl but I haven't
seen anything that indicates what I should do to re-enable it.

Can anyone tell me what I need to do to enable the correct driver to
get virtual/egl provided on the Raspberry Pi 4? Or maybe even better,
how I could search through the packages that are enabled on the old
and new Yocto trees so that I can figure out what changed between the
releases and re-enable the virtual/egl.
it should be provided by userland package if you are using closed source
graphics driver.

Best Regards,

Greg Wilson-Lindberg





Re: Meta-raspberrypi - how to configure device tree for MCP251x

Chris Tapp
 

Hi Khem,

There is nothing in /boot once the system has started, but if I mount /dev/mmcblk0p1 I can see a config.txt that includes:

     dtparam=spi=on 
     dtoverlay=mcp2515-can0,oscillator=16000000,interrupt=25 
     dtoverlay=mcp2515-can1,oscillator=16000000,interrupt=23 

This is what I could expect.

On a quick scan, this appears to be the same as the one in tmp/deploy/images/raspberrypi4/bootfiles - the timestamp for this file indicated it was old, so I had manually cleaned and rebuilt rpi-bootfiles for changes to RPI_EXTRA_CONFIG to propagate.

However, if I bring the CAN interface up:

ip link set can1 up type can bitrate 100000

and look in /proc/interrupts, I see:

 66:          0          0          0          0  pinctrl-bcm2835  25 Level     spi0.0

even though can1 is on spi0.1.

--

On 4 Oct 2021, at 17:49, Khem Raj <raj.khem@...> wrote:

can you check boot/config.txt and see fi your changes are there in your target ?

On Mon, Oct 4, 2021 at 1:21 AM Chris Tapp <opensource@...> wrote:

Sorry, I meant to add that I have tried adding the following to local.conf:

RPI_EXTRA_CONFIG = ' \n \
   dtparam=spi=on \n \
   dtoverlay=mcp2515-can0,oscillator=16000000,interrupt=25 \n \
   dtoverlay=mcp2515-can1,oscillator=16000000,interrupt=23 \n \
   '

However, this did not make any difference to the interrupts.

Since then, I have manually changed mcp2515-can1-overlay.dts in the kernel build tree (after running bitbake - c do_configure virtual/kernel) and rebuilt the kernel / image. This does result in the interrupt mapping changing, and both CAN channels then operate correctly.

Does anyone know why RPI_EXTRA_CONFIG doesn’t appear to be taking effect?

--

Chris Tapp
opensource@...
www.keylevel.com

----
You can tell you're getting older when your car insurance gets real cheap!

On 1 Oct 2021, at 22:38, Chris Tapp <opensource@...> wrote:

I am having trouble getting the Waveshare 2-CH CAN HAT working with an RPI4. Channel 0 does not come up, channel 1 does, but it will only send one message (eventually reporting "write: No buffer space available”) and not receive anything.

Looking at the mcp2515-can0-overlay.dts and mcp2515-can1-overlay.dts device tree files in /tmp/work-shared/raspberrypi4/kernel-source/arch/arm/boot/dts/overlays/, it looks as if the interrupts are not mapped as required for the board.

     DTS               HAT
CAN0  brcm,pins = <25>  PIN23
CAN1  brcm,pins = <25>  PIN25

This doesn’t look right, and seems consistent with the behaviour I am seeing.

I would also like to check the device chip select signals, but I can't see how (if) they are mapped in the dts files.

How can I override these settings when I build the image?

--

Chris Tapp
opensource@...
www.keylevel.com










Re: virtual/egl on Raspberry Pi 4

Khem Raj
 

On 10/4/21 12:39 PM, Greg Wilson-Lindberg wrote:
Hello list,
I'm working on a Qt supplied boot2qt Yocto build currently based on Zeus that is running on a Raspberry Pi 4. I recently updated the qt version to 5.15.6 and Qt changed something in the Yocto configuration that they are using and now one of the recipes that we use is failing saying that in needs 'virtual/egl' but that it is not provided by any recipe.
In the searching that I have done I have found that the raspberry pi 4 is particular on which package supplies the virtual/egl but I haven't seen anything that indicates what I should do to re-enable it.
Can anyone tell me what I need to do to enable the correct driver to get virtual/egl provided on the Raspberry Pi 4? Or maybe even better, how I could search through the packages that are enabled on the old and new Yocto trees so that I can figure out what changed between the releases and re-enable the virtual/egl.
it should be provided by userland package if you are using closed source graphics driver.

Best Regards,
Greg Wilson-Lindberg


virtual/egl on Raspberry Pi 4

Greg Wilson-Lindberg
 

Hello list,

I'm working on a Qt supplied boot2qt Yocto build currently based on Zeus that is running on a Raspberry Pi 4. I recently updated the qt version to 5.15.6 and Qt changed something in the Yocto configuration that they are using and now one of the recipes that we use is failing saying that in needs 'virtual/egl' but that it is not provided by any recipe.

 

In the searching that I have done I have found that the raspberry pi 4 is particular on which package supplies the virtual/egl but I haven't seen anything that indicates what I should do to re-enable it.

 

Can anyone tell me what I need to do to enable the correct driver to get virtual/egl provided on the Raspberry Pi 4? Or maybe even better, how I could search through the packages that are enabled on the old and new Yocto trees so that I can figure out what changed between the releases and re-enable the virtual/egl.

 

Best Regards,

Greg Wilson-Lindberg

 


Building a native package that includes tools + u-boot binaries

jpdoyon@...
 

I am trying to create a first install package for our device, which would contain an install tool binary, and the required files to install.  In our case, that would be

 

From imx-usb_loader recipe:

imx_usb

imx_usb.conf

mx6_usb_rom.conf

mx6_usb_sdp_spl.conf

 

From u-boot recipe:

u-boot.img

SPL

uEnv.txt

 

The idea would be for the recipe to generate a tarball with all of that  and a script, that would automate the USB download project (the script: “install.sh” is already done, and is obviously out of scope for this question)

 

So I created a new recipe (box1-usb-loader.bb) which depends on both u-boot and imx-usb-loader.  But I can’t seem to get the u-boot target files listed above to appear in my recipe-sysroot directory. 

 

I’ve been scouring the web for a day now, and I’ve found plenty of people asking about seemingly related issues, but nothing that actually gets me nearer.  From what I could find, I’m missing something in my u-boot.bbappend to stage the three files I need, but everything I’ve tried has failed.  The most promising post got me to add this:

 

 

SYSROOT_DIRS += "${D}/boot"

 

do_stage () {

                install -d ${D}/boot

    install -m 0644 ${WORKDIR}/package/boot/u-boot.img ${D}/boot

    install -m 0644 ${WORKDIR}/package/boot/SPL ${D}/boot

    install -m 0644 ${WORKDIR}/package/boot/uEnv.txt ${D}/boot

}

 

sysroot_stage_all_append () {                                    

    sysroot_stage_dir ${D}/boot ${SYSROOT_DESTDIR}/boot

}

 

 

But it didn’t succeed.

 

Thanks for any help you may provide.

 

Sincerely,

 

Jean-Pierre Doyon


Re: Meta-raspberrypi - how to configure device tree for MCP251x

Khem Raj
 

can you check boot/config.txt and see fi your changes are there in your target ?

On Mon, Oct 4, 2021 at 1:21 AM Chris Tapp <opensource@...> wrote:

Sorry, I meant to add that I have tried adding the following to local.conf:

RPI_EXTRA_CONFIG = ' \n \
dtparam=spi=on \n \
dtoverlay=mcp2515-can0,oscillator=16000000,interrupt=25 \n \
dtoverlay=mcp2515-can1,oscillator=16000000,interrupt=23 \n \
'

However, this did not make any difference to the interrupts.

Since then, I have manually changed mcp2515-can1-overlay.dts in the kernel build tree (after running bitbake - c do_configure virtual/kernel) and rebuilt the kernel / image. This does result in the interrupt mapping changing, and both CAN channels then operate correctly.

Does anyone know why RPI_EXTRA_CONFIG doesn’t appear to be taking effect?

--

Chris Tapp
opensource@...
www.keylevel.com

----
You can tell you're getting older when your car insurance gets real cheap!

On 1 Oct 2021, at 22:38, Chris Tapp <opensource@...> wrote:

I am having trouble getting the Waveshare 2-CH CAN HAT working with an RPI4. Channel 0 does not come up, channel 1 does, but it will only send one message (eventually reporting "write: No buffer space available”) and not receive anything.

Looking at the mcp2515-can0-overlay.dts and mcp2515-can1-overlay.dts device tree files in /tmp/work-shared/raspberrypi4/kernel-source/arch/arm/boot/dts/overlays/, it looks as if the interrupts are not mapped as required for the board.

DTS HAT
CAN0 brcm,pins = <25> PIN23
CAN1 brcm,pins = <25> PIN25

This doesn’t look right, and seems consistent with the behaviour I am seeing.

I would also like to check the device chip select signals, but I can't see how (if) they are mapped in the dts files.

How can I override these settings when I build the image?

--

Chris Tapp
opensource@...
www.keylevel.com








[meta-security][PATCH] sssd: FIX QA error

Armin Kuster
 

ERROR: sssd-2.5.2-r0 do_package_qa: QA Issue: sssd rdepends on dbus-dev [dev-deps]
ERROR: sssd-2.5.2-r0 do_package_qa: QA Issue: sssd rdepends on ding-libs-dev [dev-deps]

Signed-off-by: Armin Kuster <akuster808@...>
---
recipes-security/sssd/sssd_2.5.2.bb | 1 +
1 file changed, 1 insertion(+)

diff --git a/recipes-security/sssd/sssd_2.5.2.bb b/recipes-security/sssd/sssd_2.5.2.bb
index 76d6e03..33166be 100644
--- a/recipes-security/sssd/sssd_2.5.2.bb
+++ b/recipes-security/sssd/sssd_2.5.2.bb
@@ -132,3 +132,4 @@ FILES:${PN}-dev = " ${includedir}/* ${libdir}/*la ${libdir}/*/*la"
INSANE_SKIP:${PN} = "dev-so"

RDEPENDS:${PN} = "bind bind-utils dbus libldb libpam"
+RDEPENDS:${PN}-dev = "dbus-dev ding-libs-dev"
--
2.25.1


Re: Shared lib symlinks in target image

Richard Purdie
 

On Sun, 2021-10-03 at 01:55 +0000, Lijun Chen wrote:
Hi,

When I build a yocto image, I added some packages into IMAGE_INSTALL, such as
boost, thrift, etc. I notice in the target OS image, the shared libs don't the
symlinks. But in the SDK image, the symlinks are there. For example,
lrwxrwxrwx 1 root root       22 Oct  2 16:41 libboost_filesystem-mt.so ->
libboost_filesystem.so
lrwxrwxrwx 1 root root       29 Oct  2 16:41 libboost_filesystem.so ->
libboost_filesystem.so.1.75.0

Is there a way to add the symlinks to the target image as well?
With the symlinks, I assume we can run an old application even the dependent
lib is a newer version?
The symlinks will be in the XXX-dev packages so boost-dev probably has them for
boost. They aren't needed on target unless you're compiling things which is why
they're separated out.

Cheers,

Richard


Re: Shared lib symlinks in target image

Khem Raj
 


Libraries have another symlink which looks something like libfoo.so.1 and 2 etc that is the one which should be used by apps 

On Mon, Oct 4, 2021 at 6:12 AM Lijun Chen <lijchen@...> wrote:

I have an app built in a different environment that has lower versioned libs, such as boost. I was wondering if on the target there are symlinks to those libs, whether the app can be run on a target that has newer libs without resbuild against a matched env. Seems that is not viable.


From: Khem Raj <raj.khem@...>
Sent: Saturday, October 2, 2021 11:23:58 PM
To: Lijun Chen
Cc: yocto@...
Subject: Re: [yocto] Shared lib symlinks in target image
 
On Sat, Oct 2, 2021 at 6:55 PM Lijun Chen <lijchen@...> wrote:
>
> Hi,
>
>
> When I build a yocto image, I added some packages into IMAGE_INSTALL, such as boost, thrift, etc. I notice in the target OS image, the shared libs don't the symlinks. But in the SDK image, the symlinks are there. For example,
>
> lrwxrwxrwx 1 root root       22 Oct  2 16:41 libboost_filesystem-mt.so -> libboost_filesystem.so
> lrwxrwxrwx 1 root root       29 Oct  2 16:41 libboost_filesystem.so -> libboost_filesystem.so.1.75.0
>
> Is there a way to add the symlinks to the target image as well?
>
>
> With the symlinks, I assume we can run an old application even the dependent lib is a newer version?
>

unversioned symlinks should not be used they are there to be used for
linking during build time. Unless you need to do builds on targets you
really do not need them
so explain you usecase. Are you trying to build stuff on device ?

>
> Thanks,
>
> Lijun
>
> ________________________________
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
>
>
>

This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.


Re: Shared lib symlinks in target image

Lijun Chen
 

I have an app built in a different environment that has lower versioned libs, such as boost. I was wondering if on the target there are symlinks to those libs, whether the app can be run on a target that has newer libs without resbuild against a matched env. Seems that is not viable.


From: Khem Raj <raj.khem@...>
Sent: Saturday, October 2, 2021 11:23:58 PM
To: Lijun Chen
Cc: yocto@...
Subject: Re: [yocto] Shared lib symlinks in target image
 
On Sat, Oct 2, 2021 at 6:55 PM Lijun Chen <lijchen@...> wrote:
>
> Hi,
>
>
> When I build a yocto image, I added some packages into IMAGE_INSTALL, such as boost, thrift, etc. I notice in the target OS image, the shared libs don't the symlinks. But in the SDK image, the symlinks are there. For example,
>
> lrwxrwxrwx 1 root root       22 Oct  2 16:41 libboost_filesystem-mt.so -> libboost_filesystem.so
> lrwxrwxrwx 1 root root       29 Oct  2 16:41 libboost_filesystem.so -> libboost_filesystem.so.1.75.0
>
> Is there a way to add the symlinks to the target image as well?
>
>
> With the symlinks, I assume we can run an old application even the dependent lib is a newer version?
>

unversioned symlinks should not be used they are there to be used for
linking during build time. Unless you need to do builds on targets you
really do not need them
so explain you usecase. Are you trying to build stuff on device ?

>
> Thanks,
>
> Lijun
>
> ________________________________
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
>
>
>

This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.


Re: Meta-raspberrypi - how to configure device tree for MCP251x

Chris Tapp
 

Sorry, I meant to add that I have tried adding the following to local.conf:

RPI_EXTRA_CONFIG = ' \n \
    dtparam=spi=on \n \
    dtoverlay=mcp2515-can0,oscillator=16000000,interrupt=25 \n \
    dtoverlay=mcp2515-can1,oscillator=16000000,interrupt=23 \n \
    '

However, this did not make any difference to the interrupts.

Since then, I have manually changed mcp2515-can1-overlay.dts in the kernel build tree (after running bitbake - c do_configure virtual/kernel) and rebuilt the kernel / image. This does result in the interrupt mapping changing, and both CAN channels then operate correctly.

Does anyone know why RPI_EXTRA_CONFIG doesn’t appear to be taking effect?

--

Chris Tapp

----
You can tell you're getting older when your car insurance gets real cheap!

On 1 Oct 2021, at 22:38, Chris Tapp <opensource@...> wrote:

I am having trouble getting the Waveshare 2-CH CAN HAT working with an RPI4. Channel 0 does not come up, channel 1 does, but it will only send one message (eventually reporting "write: No buffer space available”) and not receive anything.

Looking at the mcp2515-can0-overlay.dts and mcp2515-can1-overlay.dts device tree files in /tmp/work-shared/raspberrypi4/kernel-source/arch/arm/boot/dts/overlays/, it looks as if the interrupts are not mapped as required for the board.

      DTS               HAT
CAN0  brcm,pins = <25>  PIN23
CAN1  brcm,pins = <25>  PIN25

This doesn’t look right, and seems consistent with the behaviour I am seeing.

I would also like to check the device chip select signals, but I can't see how (if) they are mapped in the dts files.

How can I override these settings when I build the image?






Re: Shared lib symlinks in target image

Khem Raj
 

On Sat, Oct 2, 2021 at 6:55 PM Lijun Chen <lijchen@...> wrote:

Hi,


When I build a yocto image, I added some packages into IMAGE_INSTALL, such as boost, thrift, etc. I notice in the target OS image, the shared libs don't the symlinks. But in the SDK image, the symlinks are there. For example,

lrwxrwxrwx 1 root root 22 Oct 2 16:41 libboost_filesystem-mt.so -> libboost_filesystem.so
lrwxrwxrwx 1 root root 29 Oct 2 16:41 libboost_filesystem.so -> libboost_filesystem.so.1.75.0

Is there a way to add the symlinks to the target image as well?


With the symlinks, I assume we can run an old application even the dependent lib is a newer version?
unversioned symlinks should not be used they are there to be used for
linking during build time. Unless you need to do builds on targets you
really do not need them
so explain you usecase. Are you trying to build stuff on device ?


Thanks,

Lijun

________________________________
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.



Shared lib symlinks in target image

Lijun Chen
 

Hi,


When I build a yocto image, I added some packages into IMAGE_INSTALL, such as boost, thrift, etc. I notice in the target OS image, the shared libs don't the symlinks. But in the SDK image, the symlinks are there. For example,

lrwxrwxrwx 1 root root       22 Oct  2 16:41 libboost_filesystem-mt.so -> libboost_filesystem.so
lrwxrwxrwx 1 root root       29 Oct  2 16:41 libboost_filesystem.so -> libboost_filesystem.so.1.75.0

Is there a way to add the symlinks to the target image as well?


With the symlinks, I assume we can run an old application even the dependent lib is a newer version?


Thanks,

Lijun


This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.


Re: gcov support for target in Yocto

Lijun Chen
 

Thank


From: Khem Raj <raj.khem@...>
Sent: Friday, September 24, 2021 12:53:26 AM
To: Lijun Chen
Cc: yocto@...
Subject: Re: [yocto] gcov support for target in Yocto
 
On Thu, Sep 23, 2021 at 9:53 AM Lijun Chen <lijchen@...> wrote:
>
> Hi,
>
>
> Anybody knows how to enable gcov support for the target in Yocto?
>

IMAGE_INSTALL += "gcov gcov-symlinks"

>
> Thanks,
>
> Lijun
>
> ________________________________
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
>
>
>

This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.


[meta-security][PATCH v2] swtpm: update to 0.6.1

Kristian Klausen <kristian@...>
 

swtpm no longer depends on Python[1] so the dependencies have been
removed.

"inherit perlnative" has been added due to (in oe-core):
deda455b3c ("bitbake.conf: drop pod2man from hosttools")

Some leftover dependencies have also been removed, ex: tpm-tools
required in the past by swtpm_setup.sh (<0.4.0)[2].

[1] https://github.com/stefanberger/swtpm/issues/437
[2] https://github.com/stefanberger/swtpm/commit/eee8cb5dfb13f87140dddda3=
8f65bf61aff19508

Signed-off-by: Kristian Klausen <kristian@...>
---
V2:
Squashed chnanges from https://lists.yoctoproject.org/g/yocto/topic/86012=
566
(decided to still use RRECOMMENDS for swtpm-create-tpmca deps)
Fix build error due to missing expect (expect -> expect-native)
Changed socat to socat-native

Building tested with:
bitbake swtpm && bitbake swtpm-native (with and without gnutls)

.../swtpm/swtpm-wrappers-native.bb | 12 ++++------
.../swtpm/{swtpm_0.5.2.bb =3D> swtpm_0.6.1.bb} | 23 ++++++++-----------
2 files changed, 14 insertions(+), 21 deletions(-)
rename meta-tpm/recipes-tpm/swtpm/{swtpm_0.5.2.bb =3D> swtpm_0.6.1.bb} (=
69%)

diff --git a/meta-tpm/recipes-tpm/swtpm/swtpm-wrappers-native.bb b/meta-t=
pm/recipes-tpm/swtpm/swtpm-wrappers-native.bb
index 644f3ac..bb93374 100644
--- a/meta-tpm/recipes-tpm/swtpm/swtpm-wrappers-native.bb
+++ b/meta-tpm/recipes-tpm/swtpm/swtpm-wrappers-native.bb
@@ -1,6 +1,6 @@
SUMMARY =3D "SWTPM - OpenEmbedded wrapper scripts for native swtpm tools=
"
LICENSE =3D "MIT"
-DEPENDS =3D "swtpm-native tpm-tools-native net-tools-native"
+DEPENDS =3D "swtpm-native"
=20
inherit native
=20
@@ -14,23 +14,19 @@ do_create_wrapper () {
for i in `find ${bindir} ${base_bindir} ${sbindir} ${base_sbindir} -=
name 'swtpm*' -perm /+x -type f`; do
exe=3D`basename $i`
case $exe in
- swtpm_setup.sh)
+ swtpm_setup)
cat >${WORKDIR}/swtpm_setup_oe.sh <<EOF
#! /bin/sh
#
-# Wrapper around swtpm_setup.sh which adds parameters required to
+# Wrapper around swtpm_setup which adds parameters required to
# run the setup as non-root directly from the native sysroot.
=20
PATH=3D"${bindir}:${base_bindir}:${sbindir}:${base_sbindir}:\$PATH"
export PATH
=20
-# tcsd only allows to be run as root or tss. Pretend to be root...
-exec env ${FAKEROOTENV} ${FAKEROOTCMD} swtpm_setup.sh --config ${STAGING=
_DIR_NATIVE}/etc/swtpm_setup.conf "\$@"
+exec swtpm_setup --config ${STAGING_DIR_NATIVE}/etc/swtpm_setup.conf "\$=
@"
EOF
;;
- swtpm_setup)
- true
- ;;
*)
cat >${WORKDIR}/${exe}_oe.sh <<EOF
#! /bin/sh
diff --git a/meta-tpm/recipes-tpm/swtpm/swtpm_0.5.2.bb b/meta-tpm/recipes=
-tpm/swtpm/swtpm_0.6.1.bb
similarity index 69%
rename from meta-tpm/recipes-tpm/swtpm/swtpm_0.5.2.bb
rename to meta-tpm/recipes-tpm/swtpm/swtpm_0.6.1.bb
index 912e939..c7fc131 100644
--- a/meta-tpm/recipes-tpm/swtpm/swtpm_0.5.2.bb
+++ b/meta-tpm/recipes-tpm/swtpm/swtpm_0.6.1.bb
@@ -3,14 +3,11 @@ LICENSE =3D "BSD-3-Clause"
LIC_FILES_CHKSUM =3D "file://LICENSE;md5=3Dfe8092c832b71ef20dfe4c6d3decb=
3a8"
SECTION =3D "apps"
=20
-DEPENDS =3D "libtasn1 coreutils-native expect socat glib-2.0 net-tools-n=
ative libtpm libtpm-native"
+# expect-native, socat-native, coreutils-native and net-tools-native are=
reportedly only required for the tests
+DEPENDS =3D "libtasn1 coreutils-native expect-native socat-native glib-2=
.0 net-tools-native libtpm json-glib"
=20
-# configure checks for the tools already during compilation and
-# then swtpm_setup needs them at runtime
-DEPENDS:append =3D " tpm-tools-native expect-native socat-native python3=
-pip-native python3-cryptography-native"
-
-SRCREV =3D "e59c0c1a7b4c8d652dbb280fd6126895a7057464"
-SRC_URI =3D "git://github.com/stefanberger/swtpm.git;branch=3Dstable-0.5=
\
+SRCREV =3D "98187d24fe14851653a7c46eb16e9c5f0b9beaa1"
+SRC_URI =3D "git://github.com/stefanberger/swtpm.git;branch=3Dstable-0.6=
\
file://ioctl_h.patch \
file://oe_configure.patch \
"
@@ -19,7 +16,7 @@ PE =3D "1"
S =3D "${WORKDIR}/git"
=20
PARALLEL_MAKE =3D ""
-inherit autotools pkgconfig python3native
+inherit autotools pkgconfig perlnative
=20
TSS_USER=3D"tss"
TSS_GROUP=3D"tss"
@@ -28,7 +25,10 @@ PACKAGECONFIG ?=3D "openssl"
PACKAGECONFIG +=3D "${@bb.utils.contains('DISTRO_FEATURES', 'selinux', '=
selinux', '', d)}"
PACKAGECONFIG +=3D "${@bb.utils.contains('BBFILE_COLLECTIONS', 'filesyst=
ems-layer', 'cuse', '', d)}"
PACKAGECONFIG[openssl] =3D "--with-openssl, --without-openssl, openssl"
-PACKAGECONFIG[gnutls] =3D "--with-gnutls, --without-gnutls, gnutls"
+# expect, bash, tpm2-pkcs11-tools (tpm2_ptool), tpmtool and certtool is
+# used by swtpm-create-tpmca (the last two is provided by gnutls)
+# gnutls is required by: swtpm-create-tpmca, swtpm-localca and swtpm_cer=
t
+PACKAGECONFIG[gnutls] =3D "--with-gnutls, --without-gnutls, gnutls, gnut=
ls, expect bash tpm2-pkcs11-tools"
PACKAGECONFIG[selinux] =3D "--with-selinux, --without-selinux, libselinu=
x"
PACKAGECONFIG[cuse] =3D "--with-cuse, --without-cuse, fuse"
PACKAGECONFIG[seccomp] =3D "--with-seccomp, --without-seccomp, libseccom=
p"
@@ -41,14 +41,11 @@ USERADD_PARAM:${PN} =3D "--system -g ${TSS_GROUP} --h=
ome-dir \
--no-create-home --shell /bin/false ${BPN}"
=20
=20
-PACKAGES =3D+ "${PN}-python"
-FILES:${PN}-python =3D "${PYTHON_SITEPACKAGES_DIR}"
-
PACKAGE_BEFORE_PN =3D "${PN}-cuse"
FILES:${PN}-cuse =3D "${bindir}/swtpm_cuse"
=20
INSANE_SKIP:${PN} +=3D "dev-so"
=20
-RDEPENDS:${PN} =3D "libtpm expect socat bash tpm-tools python3 python3-c=
ryptography python3-twisted"
+RDEPENDS:${PN} =3D "libtpm"
=20
BBCLASSEXTEND =3D "native nativesdk"
--=20
2.25.1


Re: [meta-tpm][v2][PATCH] swtpm: fix build issues of missing expect

Armin Kuster
 

On 10/1/21 4:06 PM, Kristian Klausen wrote:
Den Fri, Oct 01, 2021 at 15:25:17 -0700 skrev Armin Kuster:
Signed-off-by: Armin Kuster <akuster808@...>

--
V2]
Only need expect-native
Clean up PACKAGECONFGI[gnutils] to conform to spec
---
meta-tpm/recipes-tpm/swtpm/swtpm_0.6.1.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta-tpm/recipes-tpm/swtpm/swtpm_0.6.1.bb b/meta-tpm/recipes-tpm/swtpm/swtpm_0.6.1.bb
index 807c02b..0087367 100644
--- a/meta-tpm/recipes-tpm/swtpm/swtpm_0.6.1.bb
+++ b/meta-tpm/recipes-tpm/swtpm/swtpm_0.6.1.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=fe8092c832b71ef20dfe4c6d3decb3a8"
SECTION = "apps"

# coreutils-native and net-tools-native are reportedly only required for the tests
-DEPENDS = "libtasn1 coreutils-native expect socat glib-2.0 net-tools-native libtpm json-glib"
+DEPENDS = "libtasn1 coreutils-native expect-native socat glib-2.0 net-tools-native libtpm json-glib"

SRCREV = "98187d24fe14851653a7c46eb16e9c5f0b9beaa1"
SRC_URI = "git://github.com/stefanberger/swtpm.git;branch=stable-0.6 \
@@ -28,7 +28,7 @@ PACKAGECONFIG[openssl] = "--with-openssl, --without-openssl, openssl"
# expect, bash, tpm2-pkcs11-tools (tpm2_ptool), tpmtool and certtool is
# used by swtpm-create-tpmca (the last two is provided by gnutls)
# gnutls is required by: swtpm-create-tpmca, swtpm-localca and swtpm_cert
-PACKAGECONFIG[gnutls] = "--with-gnutls, --without-gnutls, gnutls, gnutls, expect bash tpm2-pkcs11-tools"
+PACKAGECONFIG[gnutls] = "--with-gnutls, --without-gnutls, gnutls, gnutls expect bash tpm2-pkcs11-tools"
Hi Armin

Support for RRECOMMENDS in the PACKAGECONFIG was added some years
ago[1][2]. Whatever they should be RRECOMMENDS or RDEPENDS I'm not sure
about (I don't think swtpm-create-tpmca is a hard requirement for most
people).

If you like I can squash the changes into my own patch and resend it.
Please do, that sounds great.

-armin

[1] https://git.openembedded.org/openembedded-core/commit/?id=ec96c985ce1c888c3ce3c4d964d7a106c3c88a5c
[2] https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-PACKAGECONFIG

Cheers,
Kristian

PACKAGECONFIG[selinux] = "--with-selinux, --without-selinux, libselinux"
PACKAGECONFIG[cuse] = "--with-cuse, --without-cuse, fuse"
PACKAGECONFIG[seccomp] = "--with-seccomp, --without-seccomp, libseccomp"
--
2.25.1



How to include PostgreSQL development stuff in SDK?

tboeckel
 

Hi everybody!

I successfully built an image for an ARM based system running a PostgreSQL server and client by adding the packages "postgresql" and "postgresql-client". However, so far I failed to make the development stuff (libpq-fe.h, pg_config, etc) available in the generated SDK.

Usuallly one uses pg_config to obtain the required include path (pg_config --includedir), the required compiler flags for C and C++ (pg_config --cflags and pg_config --cppflags) as well as the required linker flags (pg_config --libdir and pg_config --ldflags). However, I get the warning during compilation of my own programs:

cc1plus: warning: include location "/usr/include/postgresql" is unsafe for cross-compilation [-Wpoison-system-directories]

Obviously the native pg_config binary of my Ubuntu system is called and hence causes references to the local installation of the libpq-dev package of my Ubuntu system instead of a pg_config binary provided by the SDK. Even worse, the SDK just includes the pg_config binary for the ARM platform, but not for x86_64.

The only way to silence these warnings is to include -Wno-poison-system-directories in my compiler flags. But this is something I really like to avoid. Who knows whether the PostgreSQL development stuff of my local Ubuntu system will always be compatible to the one for the ARM system?

Unfortunately I had no luck including the PostgreSQL development stuff in the SDK. I already tried 'TOOLCHAIN_HOST_TASK_append = " nativesdk-postgresql"', but this ends in an error message like this:

ERROR: Nothing RPROVIDES 'nativesdk-postgresql' (but /opt/PHYTEC_BSPs/yocto_imx7/sources/poky/meta/recipes-core/meta/buildtools-tarball.bb, /opt/PHYTEC_BSPs/yocto_imx7/sources/poky/meta/recipes-core/meta/uninative-tarball.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'nativesdk-postgresql' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['nativesdk-postgresql']
ERROR: Required build target 'fsl-image-qt5' has no buildable providers.
Missing or unbuildable dependency chain was: ['fsl-image-qt5', 'buildtools-tarball', 'nativesdk-postgresql']

Adding 'PACKAGECONFIG_append_pn-nativesdk += " postgresql"' also does not cause the x86_64 binary of pg_config to be included in the SDK. I assume this causes the ARM binary to be included, but this cannot be used on an x86_64 system.

I searched lots of sites for a solution already, but so far I only found hints how to add packages in general, but nothing in respect to this specific issue.

Can anybody please point out what I am doing wrong or what I need to change to solve this issue?

Many thanks in advance!

Mit freundlichem Gruß
best regards

iNOEX GmbH
Thore Böckelmann
Software Design

Mit freundlichen Grüßen / Kind regards 
i. A. Thore Böckelmann

 

iNOEX GmbH | Maschweg 70 | 49324 Melle | Germany | www.inoex.de

Dipl.-Inform. Thore Böckelmann
Software Engineering
thore.boeckelmann@...

FON +49 5422 60507-958 | FAX +49 5422 60507-101

 

Follow us on   

 


iNOEX GmbH
Innovationen und Ausruestungen fuer die Extrusionstechnik

Geschaeftsfuehrer / Managing Director: Martin Deters, Jan Lohoff 
Sitz der Gesellschaft / Headquarter: Maschweg 70, D-49324 Melle
Registergericht / Register: Amtsgericht Osnabrück
Handelsregisternummer / Registration number: HRB 207338

Bitte beachten Sie die Datenschutzinformationen

2881 - 2900 of 57793