[yocto] [meta-security][PATCH] ccs-tools:Fix build error when enable multilib.

[zhengruoqin]

ERROR: lib32-ccs-tools-1.8.4-r0 do_install: oe_runmake failed
ERROR: lib32-ccs-tools-1.8.4-r0 do_install: Execution of
'/build-armv8/tmp/work/armv7ahf-neon-mllib32-linux-gnueabi/lib32-ccs-tools/1.8.4-r0/temp/run.do_install.22368'
failed with exit code 1:
make: *** No rule to make target 'install'.  Stop.
WARNING: exit code 1 from a shell command.

Signed-off-by: Zheng Ruoqin 
---
 recipes-mac/ccs-tools/ccs-tools_1.8.4.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-mac/ccs-tools/ccs-tools_1.8.4.bb 
b/recipes-mac/ccs-tools/ccs-tools_1.8.4.bb
index 2e37c0b..79af6a5 100644
--- a/recipes-mac/ccs-tools/ccs-tools_1.8.4.bb
+++ b/recipes-mac/ccs-tools/ccs-tools_1.8.4.bb
@@ -13,7 +13,7 @@ SRC_URI = 
"http://osdn.dl.sourceforge.jp/tomoyo/49693/${BPN}-${PV}-${DS}.tar.gz;
 SRC_URI[md5sum] = "8eb96a7680bfa9c8f6de55502c44"
 SRC_URI[sha256sum] = 
"c358b80a2ea77a9dda79dc2a056dae3acaf3a72fcb8481cfb1cd1f16746324b4"
 
-S = "${WORKDIR}/${PN}"
+S = "${WORKDIR}/${BPN}"
 
 inherit features_check
 
-- 
2.17.1



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49894): https://lists.yoctoproject.org/g/yocto/message/49894
Mute This Topic: https://lists.yoctoproject.org/mt/75350154/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW27!

[Stephen Jolley]

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


richard.pur...@linuxfoundation.org

7


akuster...@gmail.com

2


ks...@saye.org

1


nicolas.deche...@linaro.org

1


jpewhac...@gmail.com

1


Grand Total

12

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49893): https://lists.yoctoproject.org/g/yocto/message/49893
Mute This Topic: https://lists.yoctoproject.org/mt/75347813/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 3.2

[Stephen Jolley]

All,

 

Below is the list as of top 39 bug owners as of the end of WW27 of who have
open medium or higher bugs and enhancements against YP 3.2.   There are 82
possible work days left until the final release candidates for YP 3.2 needs
to be released.


Who

Count


david.re...@windriver.com

10


mark.mor...@windriver.com

9


r...@burtonini.com

7


bluelightn...@bluelightning.org

7


richard.pur...@linuxfoundation.org

6


mich...@yoctoproject.org

5


qi.c...@windriver.com

5


yi.z...@windriver.com

3


rpj...@crashcourse.ca

3


raj.k...@gmail.com

3


jon.ma...@arm.com

3


trevor.gamb...@windriver.com

2


alejan...@enedino.org

2


ycnakaj...@gmail.com

2


timothy.t.orl...@intel.com

2


sakib.sa...@windriver.com

2


jpewhac...@gmail.com

2


mark.ha...@kernel.crashing.org

2


jae...@xilinx.com

2


mostthings...@gmail.com

2


kai.k...@windriver.com

2


dl...@gmx.de

2


kerg...@gmail.com

2


randy.macl...@windriver.com

2


kai.ruh...@live.com

1


limon.ani...@gmail.com

1


de...@denix.org

1


liu.min...@gmail.com

1


bruce.ashfi...@gmail.com

1


changqing...@windriver.com

1


matthew.z...@windriver.com

1


b...@stusta.de

1


matt.ranos...@konsulko.com

1


hongxu@windriver.com

1


maxime.roussinbelan...@gmail.com

1


jpuhl...@mvista.com

1


naveen.kumar.sa...@intel.com

1


martin.ja...@gmail.com

1


chee.yang@intel.com

1


Grand Total

102

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49892): https://lists.yoctoproject.org/g/yocto/message/49892
Mute This Topic: https://lists.yoctoproject.org/mt/75347741/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] 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

 

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 343
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.1", "3.2, "3.99" and "Future", the more pressing/urgent issues
being in "3.1" and then "3.2".

 

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...@gmail.com
 ) 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...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49891): https://lists.yoctoproject.org/g/yocto/message/49891
Mute This Topic: https://lists.yoctoproject.org/mt/75347719/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [yocto-autobuilder-helper][dunfell 0/6] Pull request (cover letter only)

[Steve Sakoman]

The following changes since commit 2e8b103c4fb3b6aa07c271e716d057d71b7fa543:

  config.json: add st...@sakoman.com to QA email list (2020-06-10 18:23:06 
+0100)

are available in the Git repository at:

  git://git.yoctoproject.org/yocto-autobuilder-helper contrib/sakoman
  
http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder-helper/log/?h=contrib/sakoman

Richard Purdie (3):
  config.json: Ensure trigger-build and trigger-build-posttrigger match
layer setup
  config.json: Use buildtools from 3.2 M1 to fix bugs in openssl
reporting
  scripts/publish-artefacts: Convert md5sum to sha256sum

Ross Burton (1):
  config.json: generate the buildtools tarballs for aarch64

Tummalapalli, Vineela (1):
  publish-artefacts: Improve sha256 checksum handling

Vineela (1):
  scripts/utils.py: Convert md5sum to sha256sum for layer tarballs

 config.json   |  5 ++-
 scripts/publish-artefacts | 94 ---
 scripts/utils.py  |  2 +-
 3 files changed, 53 insertions(+), 48 deletions(-)

-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49890): https://lists.yoctoproject.org/g/yocto/message/49890
Mute This Topic: https://lists.yoctoproject.org/mt/75346782/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] [PATCH] bcm-2xxx-rpi: adjuest kernel config for bcm-2xxx-rpi BSP in kernel-cache

[Bruce Ashfield]

merged

Bruce

On Sun, Jul 5, 2020 at 10:15 PM  wrote:
>
> From: Limeng 
>
> In order to match with latest kernel v5.4, some kernel configs
> need to be updated.
>
> Signed-off-by: Meng Li 
> ---
>  bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg | 42 ++-
>  1 file changed, 41 insertions(+), 1 deletion(-)
>
> diff --git a/bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg 
> b/bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg
> index ca4be139..a5060364 100755
> --- a/bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg
> +++ b/bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg
> @@ -43,6 +43,12 @@ CONFIG_CPU_IDLE=y
>  CONFIG_CPU_IDLE_GOV_MENU=y
>  CONFIG_ARM_CPUIDLE=y
>
> +#
> +# CPU frequency
> +#
> +CONFIG_CPUFREQ_DT=y
> +CONFIG_ARM_RASPBERRYPI_CPUFREQ=y
> +
>  # MTD devices
>  CONFIG_MTD=y
>  CONFIG_MTD_BLOCK=m
> @@ -72,6 +78,7 @@ CONFIG_I2C_CHARDEV=m
>  CONFIG_I2C_BCM2708=m
>  CONFIG_I2C_BCM2835=m
>  CONFIG_I2C_GPIO=m
> +CONFIG_I2C_MUX_PINCTRL=m
>  CONFIG_EEPROM_AT24=m
>
>  # SPI device
> @@ -95,6 +102,7 @@ CONFIG_DRM_LOAD_EDID_FIRMWARE=y
>  CONFIG_DRM_UDL=m
>  CONFIG_DRM_VC4=m
>  CONFIG_DRM_V3D=m
> +CONFIG_DRM_VC4_HDMI_CEC=y
>
>  #PCIe Bus support
>  CONFIG_PCI=y
> @@ -115,6 +123,12 @@ CONFIG_USB_DWCOTG=y
>  CONFIG_USB_XHCI_HCD=y
>  CONFIG_USB_PCI=y
>
> +#
> +# Input Device
> +#
> +CONFIG_INPUT_TOUCHSCREEN=y
> +CONFIG_TOUCHSCREEN_RASPBERRYPI_FW=m
> +
>  #Media support
>  CONFIG_MEDIA_CAMERA_SUPPORT=y
>  CONFIG_MEDIA_ANALOG_TV_SUPPORT=y
> @@ -130,11 +144,13 @@ CONFIG_VIDEO_EM28XX_V4L2=m
>  CONFIG_VIDEO_EM28XX_ALSA=m
>  CONFIG_VIDEO_EM28XX_DVB=m
>  CONFIG_VIDEO_BCM2835=m
> +CONFIG_VIDEO_CODEC_BCM2835=m
> +CONFIG_VIDEO_ISP_BCM2835=m
>  CONFIG_V4L_PLATFORM_DRIVERS=y
>
>  # Thermal configuration
>  CONFIG_THERMAL=y
> -CONFIG_BCM2835_THERMAL=y
> +CONFIG_BCM2711_THERMAL=y
>
>  # MMC/SD/SDIO Card Drivers
>  CONFIG_MMC=y
> @@ -207,8 +223,14 @@ CONFIG_SND_BCM2708_SOC_FE_PI_AUDIO=m
>  CONFIG_SND_BCM2708_SOC_ALLO_BOSS_DAC=m
>  CONFIG_SND_BCM2708_SOC_ALLO_DIGIONE=m
>  CONFIG_SND_BCM2708_SOC_ALLO_KATANA_DAC=m
> +CONFIG_SND_BCM2708_SOC_HIFIBERRY_DACPLUSHD=m
> +CONFIG_SND_BCM2708_SOC_JUSTBOOM_BOTH=m
> +CONFIG_SND_AUDIOINJECTOR_ISOLATED_SOUNDCARD=m
>  CONFIG_SND_PISOUND=m
>  CONFIG_SND_BCM2835=m
> +CONFIG_SND_SOC_CS4271_I2C=m
> +CONFIG_SND_SOC_MA120X0P=m
> +CONFIG_SND_SOC_MAX98357A=m
>
>  # GPIO Support
>  CONFIG_MFD_CORE=y
> @@ -249,6 +271,22 @@ CONFIG_REGULATOR_ARIZONA_LDO1=m
>  CONFIG_REGULATOR_ARIZONA_MICSUPP=m
>  CONFIG_REGULATOR_GPIO=y
>
> +# Clock configuration
> +CONFIG_CLK_RASPBERRYPI=y
> +
> +#
> +# DMABUF options
> +#
> +CONFIG_DMABUF_HEAPS=y
> +CONFIG_DMABUF_HEAPS_SYSTEM=y
> +CONFIG_DMABUF_HEAPS_CMA=y
> +
> +#
> +# Multifunction device
> +#
> +CONFIG_MFD_SYSCON=y
> +CONFIG_MFD_WM5102=y
> +
>  # Misc configuration
>  CONFIG_BINFMT_MISC=m
>  CONFIG_BRCM_CHAR_DRIVERS=y
> @@ -269,3 +307,5 @@ CONFIG_LOGITECH_FF=y
>  CONFIG_LOGIRUMBLEPAD2_FF=y
>  CONFIG_LOGIG940_FF=y
>  CONFIG_SENSORS_RPI_POE_FAN=m
> +CONFIG_LEDS_CLASS=y
> +CONFIG_NEW_LEDS=y
> --
> 2.17.1
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8796): 
https://lists.yoctoproject.org/g/linux-yocto/message/8796
Mute This Topic: https://lists.yoctoproject.org/mt/75325940/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto]: [kernel v5.4/standard/bcm-2xxx-rpi]: bcm-2xxx-rpi: upgrade patches for raspberrypi 4b platform

[Bruce Ashfield]

On Sun, Jul 5, 2020 at 2:36 AM  wrote:
>
> From: Limeng 
>
> Hi Bruce,
>
> There are some new patches merged into upstream raspberrypi sdk kernel, 
> branch rpi-5.4.y.
> So, I get the latest patches from raspberry pi git repo 
> https://github.com/raspberrypi/linux.git rpi-5.4.y,
> and intend to merge them into linux-yocto, branch v5.4/standard/bcm-2xxx-rpi.
>
> Could you please help merge these patches into linux-ycoto kernel, branch is 
> v5.4/standard/bcm-2xxx-rpi?
> The 621 patches are in my public repo 
> https://github.com/limeng-linux/linux-yocto-5.4.git, branch 
> v5.4/standard/bcm-2xxx-rpi
>

I've grabbed and merged the branch.

Bruce

>
> diffstat info as below.
>
>  /arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 
>  759
>  /arch/arm/boot/dts/bcm2711.dtsi| 
> 2028 -
>  /arch/arm/boot/dts/bcm2838-rpi-4-b.dts | 
>  134
>  /arch/arm/boot/dts/bcm2838.dtsi| 
>  732
>  /drivers/media/platform/bcm2835/Kconfig| 
>   69
>  /drivers/media/platform/bcm2835/Makefile   | 
>6
>  /drivers/media/platform/bcm2835/bcm2835-unicam.c   
> |11748 +-
>  /drivers/media/platform/bcm2835/vc4-regs-unicam.h  | 
>  506
>  /drivers/pci/controller/pcie-brcmstb-bounce.c  | 
>  558
>  /drivers/pci/controller/pcie-brcmstb-bounce.h  | 
>   32
>  /drivers/pci/controller/pcie-brcmstb-bounce64.c| 
>  568
>  /drivers/pci/controller/pcie-brcmstb.c | 
> 2147 -
>  Documentation/devicetree/bindings/display/brcm,bcm-vc4.txt | 
>  174
>  Documentation/devicetree/bindings/i2c/i2c-brcmstb.txt  | 
>   26
>  Documentation/devicetree/bindings/media/i2c/imx219.txt | 
>   59
>  arch/arm/boot/dts/bcm2711-rpi.dtsi | 
>7
>  arch/arm/boot/dts/bcm2838-rpi.dtsi | 
>   25
>  arch/arm/boot/dts/overlays/bmp085_i2c-sensor-overlay.dts   | 
>   23
>  arch/arm/boot/dts/overlays/i2c0-bcm2708-overlay.dts| 
>   14
>  arch/arm/boot/dts/overlays/i2c1-bcm2708-overlay.dts| 
>9
>  arch/arm/boot/dts/overlays/pi3-act-led-overlay.dts | 
>1
>  arch/arm/boot/dts/overlays/pi3-disable-bt-overlay.dts  | 
>1
>  arch/arm/boot/dts/overlays/pi3-disable-wifi-overlay.dts| 
>1
>  arch/arm/boot/dts/overlays/pi3-miniuart-bt-overlay.dts | 
>1
>  arch/x86/include/asm/dma-direct.h  | 
>9
>  b/Documentation/ABI/testing/sysfs-driver-w1_therm  | 
>  124
>  b/Documentation/devicetree/bindings/clock/brcm,bcm2711-dvp.yaml| 
>   47
>  b/Documentation/devicetree/bindings/clock/raspberrypi,firmware-clocks.yaml | 
>   39
>  b/Documentation/devicetree/bindings/display/brcm,bcm2835-dpi.yaml  | 
>   72
>  b/Documentation/devicetree/bindings/display/brcm,bcm2835-dsi0.yaml | 
>   84
>  b/Documentation/devicetree/bindings/display/brcm,bcm2835-hdmi.yaml | 
>  200
>  b/Documentation/devicetree/bindings/display/brcm,bcm2835-hvs.yaml  | 
>   37
>  b/Documentation/devicetree/bindings/display/brcm,bcm2835-pixelvalve0.yaml  | 
>   45
>  b/Documentation/devicetree/bindings/display/brcm,bcm2835-txp.yaml  | 
>   37
>  b/Documentation/devicetree/bindings/display/brcm,bcm2835-v3d.yaml  | 
>   42
>  b/Documentation/devicetree/bindings/display/brcm,bcm2835-vc4.yaml  | 
>   35
>  b/Documentation/devicetree/bindings/display/brcm,bcm2835-vec.yaml  | 
>   44
>  b/Documentation/devicetree/bindings/i2c/brcm,brcmstb-i2c.yaml  | 
>   99
>  b/Documentation/devicetree/bindings/media/i2c/imx219.yaml  | 
>  114
>  b/Documentation/devicetree/bindings/media/i2c/imx290.txt   | 
>   64
>  b/Documentation/devicetree/bindings/media/i2c/imx477.yaml  | 
>  113
>  b/Documentation/devicetree/bindings/media/i2c/irs1125.txt  | 
>   48
>  b/Documentation/devicetree/bindings/media/rpivid_hevc.yaml | 
>   72
>  b/Documentation/devicetree/bindings/thermal/brcm,avs-ro-thermal.yaml   | 
>   45
>  b/Documentation/fb/modedb.rst  | 
>3
>  b/Documentation/media/kapi/v4l2-subdev.rst | 
>   53
>  b/Documentation/media/uapi/v4l/biblio.rst  | 
>9
>  b/Documentation/media/uapi/v4l/buffer.rst  | 
>   13
>  b/Documentation/media/uapi/v4l/dev-subdev.rst 

[yocto] 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. (7/7)  

 

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: http://webchat.freenode.net/?channels=#yocto

 

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

 

WhenMonthly from 8am to 8:30am on the first Tuesday Pacific Time

Where   Zoom Meeting: https://zoom.us/j/990892712 

 

We are tracking the minutes at:
https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9d
DH4/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...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49889): https://lists.yoctoproject.org/g/yocto/message/49889
Mute This Topic: https://lists.yoctoproject.org/mt/75341767/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-yocto] [linux-yocto v4.19/standard/preempt-rt/base][PATCH] workqueue: Fix incompatible pointer type error

[Bruce Ashfield]

Sorry for the delay.

I've grabbed and merged this now.

I was also updating the -stable version for 4.19 and ran into yet more
-rt conflicts. Looking at other -rt versions, the resolutions look
correct .. but I've gone ahead and pushed in parallel to some build
tests. So please submit patches if I have broken something (again).

Bruce

On Tue, Jun 30, 2020 at 9:30 AM Daniel Dragomir
 wrote:
>
> Use raw_spin_unlock_irq instead spin_unlock_irq to avoid incompatible
> pointer type error on preempt-rt branch:
>
> kernel/workqueue.c:4176:17: error: passing argument 1 of 'rt_spin_lock'
> from incompatible pointer type [-Werror=incompatible-pointer-types]
> |  4176 |   spin_lock_irq(_mayday_lock);
> |   | ^~~
> |   | |
> |   | raw_spinlock_t * {aka struct raw_spinlock *}
> include/linux/spinlock_rt.h:40:40: note: in definition of macro 'spin_lock'
> |40 | #define spin_lock(lock)   rt_spin_lock(lock)
> |   |^~~~
> kernel/workqueue.c:4176:3: note: in expansion of macro 'spin_lock_irq'
> |  4176 |   spin_lock_irq(_mayday_lock);
> |   |   ^
> include/linux/spinlock_rt.h:21:49: note: expected 'spinlock_t *'
> {aka 'struct spinlock *'} but argument is of type 'raw_spinlock_t *'
> {aka 'struct raw_spinlock *'}
> |21 | extern void __lockfunc rt_spin_lock(spinlock_t *lock);
> |   | ^~~~
>
> Signed-off-by: Daniel Dragomir 
> ---
>  kernel/workqueue.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> index d88d11cfbad5..75f59299dd06 100644
> --- a/kernel/workqueue.c
> +++ b/kernel/workqueue.c
> @@ -4173,9 +4173,9 @@ void destroy_workqueue(struct workqueue_struct *wq)
> struct worker *rescuer = wq->rescuer;
>
> /* this prevents new queueing */
> -   spin_lock_irq(_mayday_lock);
> +   raw_spin_lock_irq(_mayday_lock);
> wq->rescuer = NULL;
> -   spin_unlock_irq(_mayday_lock);
> +   raw_spin_unlock_irq(_mayday_lock);
>
> /* rescuer will empty maydays list before exiting */
> kthread_stop(rescuer->task);
> --
> 2.17.1
>
> 



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#8794): 
https://lists.yoctoproject.org/g/linux-yocto/message/8794
Mute This Topic: https://lists.yoctoproject.org/mt/75213396/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-security][PATCH 1/5] python3-oauth2client: add recipe

[akuster]

On 7/5/20 12:03 PM, Konrad Weihmann wrote:
> I think some RDEPENDS entries are missing, by looking at
> https://github.com/googleapis/oauth2client/blob/master/setup.py
>
> install_requires = [
>     'httplib2>=0.9.1',
>     'pyasn1>=0.1.7',
>     'pyasn1-modules>=0.0.5',
>     'rsa>=3.1.4',
>     'six>=1.6.1',
> ]
>
> same applies to the other added recipes of this series
hmm, OK. I did not run into issues for the main app I am after
supporting.  Thanks for the feedback.

-armin
>
> On 05.07.20 20:58, akuster wrote:
>> diff --git a/recipes-python/python/python3-oauth2client_4.1.3.bb
>> b/recipes-python/python/python3-oauth2client_4.1.3.bb
>> new file mode 100644
>> index 000..b84b4ca
>> --- /dev/null
>> +++ b/recipes-python/python/python3-oauth2client_4.1.3.bb
>> @@ -0,0 +1,9 @@
>> +SUMMARY = "Add version info to file paths."
>> +SECTION = "devel/python"
>> +LICENSE = "Apache-2.0"
>> +LIC_FILES_CHKSUM =
>> "file://LICENSE;md5=038e1390e94fe637991fa5569daa62bc"
>> +
>> +PYPI_PACKAGE = "oauth2client"
>> +SRC_URI[sha256sum] =
>> "d486741e451287f69568a4d26d70d9acd73a2bbfa275746c535b42098916"
>> +
>> +inherit pypi setuptools3
>>
>>
>>
>>
>
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49887): https://lists.yoctoproject.org/g/yocto/message/49887
Mute This Topic: https://lists.yoctoproject.org/mt/75319308/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] how does the recipe search resolve a recipe name? eg., "opencryptoki"?

[Robert P. J. Day]

i've run across this on occasion -- using  
http://layers.openembedded.org/ to find a given recipe sometimes  
produces answers that don't actually point to the recipe (this seems  
to be a good entry for a FAQ).


went looking for "opencryptoki", and got here:

http://layers.openembedded.org/layerindex/branch/master/recipes/?q=opencryptoki

none of which actually take one to a recipe for that software.  
granted, the summary explains that, "the package contains commands to  
utilize some of the capabilities available in the TPM PKCS#11  
interface implemented in the openCryptoki project," but that's not the  
same thing.


is there some sort of rationale for the search results one might get  
for a given recipe name?


rday



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49886): https://lists.yoctoproject.org/g/yocto/message/49886
Mute This Topic: https://lists.yoctoproject.org/mt/75334535/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] #yocto howto use deltask

[Quentin Schulz]

Hi,

On Mon, Jul 06, 2020 at 04:00:11AM -0700, Hans-Ulrich Schlieben wrote:
> Hi,
> 
> my image build fails with:
> ERROR: ims-image-fieldgate-1.0-r0 do_rootfs: The following packages could not 
> be configured offline and rootfs is read-only: ['apparmor']
> 
> The image build succeeds if i remove the task pkg_postinst_ontarget_${PN} 
> from apparmor_2.13.3.bb.
> 
> I tried to use deltask in my apparmor_2.13.3.bbappend with different settings:
> deltask postinst_ontarget
> deltask postinst
> deltask pkg_postinst
> deltask pkg_postinst_ontarget_
> deltask pkg_postinst_ontarget_apparmor
> deltask pkg_postinst_ontarget_apparmor_2
> 
> and
> 
> postinst_ontarget[noexec] = "1"
> postinst[noexec] = "1"
> pkg_postinst[noexec] = "1"
> pkg_postinst_ontarget_[noexec] = "1"
> pkg_postinst_ontarget_apparmor[noexec] = "1"
> pkg_postinst_ontarget_apparmor_2[noexec] = "1"
> 

What about:

pkg_postinst_ontarget_${PN}() {
:
}

in your bbappend? This should effectively override the task from a
bbappend (except if there are _append for the task).

Can't comment on this being a good solution to your problem but that
should work to remove the content of pkg_postinst_ontarget.

Quentin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49885): https://lists.yoctoproject.org/g/yocto/message/49885
Mute This Topic: https://lists.yoctoproject.org/mt/75330339/21656
Mute #yocto: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] #yocto howto use deltask

[Alexander Kanavin]

You need to look into what the postinst_ontarget actually does, and why can
it only happen on target. Or do not use a readonly rootfs.

Alex

On Mon, 6 Jul 2020 at 13:00, Hans-Ulrich Schlieben <
hu.schlie...@codewrights.de> wrote:

> Hi,
>
> my image build fails with:
> ERROR: ims-image-fieldgate-1.0-r0 do_rootfs: The following packages could
> not be configured offline and rootfs is read-only: ['apparmor']
>
> The image build succeeds if i remove the task pkg_postinst_ontarget_${PN}
> from apparmor_2.13.3.bb.
>
> I tried to use deltask in my apparmor_2.13.3.bbappend with different
> settings:
> deltask postinst_ontarget
> deltask postinst
> deltask pkg_postinst
> deltask pkg_postinst_ontarget_
> deltask pkg_postinst_ontarget_apparmor
> deltask pkg_postinst_ontarget_apparmor_2
>
> and
>
> postinst_ontarget[noexec] = "1"
> postinst[noexec] = "1"
> pkg_postinst[noexec] = "1"
> pkg_postinst_ontarget_[noexec] = "1"
> pkg_postinst_ontarget_apparmor[noexec] = "1"
> pkg_postinst_ontarget_apparmor_2[noexec] = "1"
>
> but to no avail - I always get the rootfs error.
>
> I know how to patch source files. But it seems there is no way to patch a
> recipe.
> My workaround would be to make a copy of the apparmor recipe without the
> postinst part.
>
> Is there a better or another way to do this?
>
> Best regards
>
> hu
>
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49884): https://lists.yoctoproject.org/g/yocto/message/49884
Mute This Topic: https://lists.yoctoproject.org/mt/75330339/21656
Mute #yocto: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] #yocto howto use deltask

[Hans-Ulrich Schlieben]

Hi,

my image build fails with:
ERROR: ims-image-fieldgate-1.0-r0 do_rootfs: The following packages could not 
be configured offline and rootfs is read-only: ['apparmor']

The image build succeeds if i remove the task pkg_postinst_ontarget_${PN} from 
apparmor_2.13.3.bb.

I tried to use deltask in my apparmor_2.13.3.bbappend with different settings:
deltask postinst_ontarget
deltask postinst
deltask pkg_postinst
deltask pkg_postinst_ontarget_
deltask pkg_postinst_ontarget_apparmor
deltask pkg_postinst_ontarget_apparmor_2

and

postinst_ontarget[noexec] = "1"
postinst[noexec] = "1"
pkg_postinst[noexec] = "1"
pkg_postinst_ontarget_[noexec] = "1"
pkg_postinst_ontarget_apparmor[noexec] = "1"
pkg_postinst_ontarget_apparmor_2[noexec] = "1"

but to no avail - I always get the rootfs error.

I know how to patch source files. But it seems there is no way to patch a 
recipe.
My workaround would be to make a copy of the apparmor recipe without the 
postinst part.

Is there a better or another way to do this?

Best regards

hu
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49883): https://lists.yoctoproject.org/g/yocto/message/49883
Mute This Topic: https://lists.yoctoproject.org/mt/75330339/21656
Mute #yocto: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Building a clean image without using sstate-cache

[Quentin Schulz]

Hi,

On Mon, Jul 06, 2020 at 11:08:31AM +0300, Shlomi Vaknin wrote:
> Hi,
> 
> I'm trying to run a clean build without using the sstate-cache shared
> directory, so we can check that everything is working properly and also
> update our sstate-cache shared folder every now and then.
> 
> I have the SSTATE_MIRRORS defined in my site.conf using "?=" operator.
> 
> When I try to export this variable as empty string and then build the
> image, the image is built using the cache.
> 
> How can I override the SSTATE_MIRRORS when running bitbake or run a clean
> build without using sstate-cache?
> 

IIUC, SSTATE_MIRRORS is just a way to prepopulate your local sstate-cache.
So you'd need to have SSTATE_MIRRORS="" but also change SSTATE_DIR to some
path where no sstate-cache is so that the local sstate-cache isn't also
used.

Quentin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49882): https://lists.yoctoproject.org/g/yocto/message/49882
Mute This Topic: https://lists.yoctoproject.org/mt/75328840/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Help creating zeek recipe #yocto

[Quentin Schulz]

Hi Gary,

On Fri, Jul 03, 2020 at 02:22:40PM -0700, gary via lists.yoctoproject.org wrote:
> I would like to create a recipe for zeek (a network security monitoring tool, 
> https://zeek.org/). It fails while compiling because it cannot find a 
> executable that it needs to install called binpac.  binpac is included in the 
> zeek repo and is normally built as part of the zeek build.  I've created a 
> recipe for binpac and included the native class and included binpac-native in 
> the zeek recipe.  The binpac-native builds.
> 
> binpac_git.bb
> 
> SUMMARY = "BinPAC is a high level language for describing protocol parsers 
> and generates C++ code."
> HOMEPAGE = "https://github.com/zeek/binpac;
> 
> LICENSE = "Unknown"
> LIC_FILES_CHKSUM = "file://COPYING;md5=5139995cafc8b5273b85dd8bab509855"
> 
> SRC_URI = "git://g...@github.com/zeek/binpac.git;protocol=ssh"
> 
> # Modify these as desired
> PV = "0.55-8+git${SRCPV}"
> SRCREV = "9c3211ff121ddc677d0ed8bd3a85783f87921cce"
> 
> BBCLASSEXTEND = "native"
> 
> DEPENDS += "bison-native \
> flex-native \
> "
> S = "${WORKDIR}/git"
> 
> inherit distutils
> 

I'm not sure setup.py is supported for the project as it's empty? So
distutils does not look correct to me.

You have a makefile (inherit no classes, that;s the default) or
Cmakelists (inherit cmake) or ./configure (inherit autotools, though it
expects a configure.ac and not a configure directly).

Then, what you want to check is that your binpac binary is installed in
${WORKDIR}/sysroot-dirs. If it's not, you've to find where the binary is
installed (if it is) and fix the Cmake/autotools scripts to install in
the correct directory (one of the directories in STAGING_DIRS as a
"subdirectory" of ${D}) or add said directory to the ones installed in
other recipes' sysroot (STAGING_DIRS).

Quentin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49881): https://lists.yoctoproject.org/g/yocto/message/49881
Mute This Topic: https://lists.yoctoproject.org/mt/75288481/21656
Mute #yocto: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Building a clean image without using sstate-cache

[Shlomi Vaknin]

Hi,

I'm trying to run a clean build without using the sstate-cache shared
directory, so we can check that everything is working properly and also
update our sstate-cache shared folder every now and then.

I have the SSTATE_MIRRORS defined in my site.conf using "?=" operator.

When I try to export this variable as empty string and then build the
image, the image is built using the cache.

How can I override the SSTATE_MIRRORS when running bitbake or run a clean
build without using sstate-cache?

Thanks!
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49880): https://lists.yoctoproject.org/g/yocto/message/49880
Mute This Topic: https://lists.yoctoproject.org/mt/75328840/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-