|
Re: Adding modules to Apache2 during build
On 2020-12-01 3:02 p.m.,
mailings@... wrote:
Hello all:
I looked at the apache source briefly and those modules do not appear to be part of apache2. From an ubuntu system:$ apt info libapache2-mod-authnz-external | grep Homepage Homepage: http://code.google.com/p/mod-auth-external and there's nothing in the layer index: so it looks like you'll have to write a recipe to build these
modules. https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded Thanks, ../Randy
build. I've tried adding these to my local.conf in the line above and even tried it in my IMAGE_INSTALL_append section. When I add it to PACKAGECONFIG_pn-php I get a "do_configure: QA Issue" that it is an invalid packageconfig. If I put it in IMAGE_INSTALL_appeng I get an error that nothing provides the packages.
-- # Randy MacLeod # Wind River Linux
|
|
|
|
Re: #yocto zeus X11 keyboard
#yocto
Monsees, Steven C (US)
Does anyone know how to work through this issue, so as to resolve the conflict generated ? Can I modify recipe or replace with a functionally equivalent package ? Running on Intel 64 based platform...
|
|
|
|
Disable/Enable DHCLIENT in Yocto
Aashik Aswin
Hi Developers, I am trying to add DHCLIENT package to my Yocto Zeus Build.
However If we include "dhcp-client" package in yocto, the dhclient takes the priority over existing Busy box udhcpc and starts during the init. My box basically uses UDHCPC for getting the IPs and my intention is to install dhclient only on a need-to-use basis. is there a way where we can prevent DHCLIENT to run on init unless invoked manually ? Please let me know Thanks in advance, Aashik
|
|
|
|
Vijay Rakesh Munganda
Hi Quentin Schulz & Ross,
Thanks for the information. Based on meta-aws I had written the recipe and do_compile has completed. Now I want to install demos in to the build which are located at tmp/work/aarch64-poky-linux/aws/1.0-r0/git/demos/mqtt/mqtt_demo_mutual_auth, so how do I write do_install? ( https://github.com/aws/aws-iot-device-sdk-embedded-C/tree/main/demos/mqtt/mqtt_demo_mutual_auth ) do_install() {
install -d ${D}${bindir}
install -m 0755 mqtt_demo_mutual_auth ${D}${bindir}
} Does above code works? Thanks & Regards, VR.
|
|
|
|
Re: #yocto
#yocto
Monsees, Steven C (US)
Thanks you, this should help...
toggle quoted messageShow quoted text
-----Original Message-----
From: yocto@... [mailto:yocto@...] On Behalf Of Nicolas Jeker Sent: Wednesday, December 02, 2020 4:22 AM To: yocto@... Subject: Re: [yocto] #yocto *** WARNING *** EXTERNAL EMAIL -- This message originates from outside our organization. Hi Steve On Tue, 2020-12-01 at 20:06 +0000, Monsees, Steven C (US) via lists.yoctoproject.org wrote: I'm not sure to what lines you refer by "banner", so I just wrote my thoughts to both below. Both are probably produced by getty, either util-linux-agetty or systemd-getty. Thanks,This "banner" output is the content of /etc/issue (which gets installed by the base-file package). -sh: cannot set terminal process group (1137): Inappropriate ioctl forThe error you see about the shell is probably getty failing to open a shell. Maybe this could be relevant: https://unix.stackexchange.com/questions/338214/error-trying-to-run-agetty-in-a-runit-based-linux-installation .
|
|
|
|
Quentin Schulz
Hi VR,
On Wed, Dec 02, 2020 at 03:27:51AM -0800, vijayrakeshmunganda@... wrote: Hi Quentin Schulz,You need to put the SDK filename into SRC_URI as well otherwise Yocto does not fetch it from the files directory. Also, Ross had a good suggestion too, please check that the recipe or a similar one does not exist already in meta-aws (or other layers). Quentin
|
|
|
|
Vijay Rakesh Munganda
Hi Quentin Schulz, ERROR: aws-1.0-r0 do_configure: Execution of '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/aws/1.0-r0/temp/run.do_configure.28296' failed with exit code 1: -- The C compiler identification is GNU 9.3.0 -- Check for working C compiler: /home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/aws/1.0-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/aarch64-poky-linux-gcc -- Check for working C compiler: /home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/aws/1.0-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/aarch64-poky-linux-gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Found OpenSSL: /home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/aws/1.0-r0/recipe-sysroot-native/usr/lib/libcrypto.so (found version "1.1.1g") -- Looking for pthread.h -- Looking for pthread.h - found -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE Downloading the Amazon Root CA certificate... % Total % Received % Xferd Average Speed Time Time Time Current Download Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (77) error setting certificate verify locations: CAfile: /home/bl-docker/rity/bsp/tmp/work/x86_64-linux/curl-native/7.69.1-r0/recipe-sysroot-native/etc/ssl/certs/ca-certificates.crt CApath: none Downloading the Baltimore Cybertrust Root CA certificate... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (77) error setting certificate verify locations: CAfile: /home/bl-docker/rity/bsp/tmp/work/x86_64-linux/curl-native/7.69.1-r0/recipe-sysroot-native/etc/ssl/certs/ca-certificates.crt CApath: none CMake Error at demos/defender/defender_demo_json/CMakeLists.txt:6 (include): include could not find load file: /home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/aws/1.0-r0/libraries/standard/coreMQTT/mqttFilePaths.cmake CMake Error at demos/defender/defender_demo_json/CMakeLists.txt:9 (include): include could not find load file: /home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/aws/1.0-r0/libraries/standard/backoffAlgorithm/backoffAlgorithmFilePaths.cmake CMake Error at demos/defender/defender_demo_json/CMakeLists.txt:12 (include): include could not find load file: /home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/aws/1.0-r0/libraries/standard/coreJSON/jsonFilePaths.cmake (Similar errors continued for few files) Thanks & Regards, VR
|
|
|
|
Re: qt5 directory not creating using qt5.15.0 master branch
Martin Jansa
See QT_DIR_NAME variable in meta-qt5 and b716195f609de6547cfdfadfd4fd25292a6bbf09 commit which changed the default value.
On Wed, Dec 2, 2020 at 5:03 AM sateesh m <sateesh0457@...> wrote: Hi Guys,
|
|
|
|
Quentin Schulz
Hi VR,
On Wed, Dec 02, 2020 at 02:02:39AM -0800, vijayrakeshmunganda@... wrote: Hi,If you don't give us the log, we won't be able to help you. SUMMARY = "AWS IoT SDK EMBEDDED C"Where is the sdk? You need to add it into your SRC_URI (you can also just pass a URL to a git repo or tarball download link). Quentin
|
|
|
|
Ross Burton <ross@...>
I suggest looking at meta-aws (https://github.com/aws/meta-aws) to see
toggle quoted messageShow quoted text
if that has a recipe already, and if it doesn't use one of the recipes there as a starting point. Ross
On Wed, 2 Dec 2020 at 10:02, <vijayrakeshmunganda@...> wrote:
|
|
|
|
Vijay Rakesh Munganda
Hi,
I'm trying to write a recipe to install AWS SDK into the build(https://github.com/aws/aws-iot-device-sdk-embedded-C), but I complete don't know how to do it. Based on online example https://github.com/joaocfernandes/Learn-Yocto/blob/master/develop/Recipe-CMake.md I have written my recipe file and download the sdk into files folder of my recipe. When I run build do_configure got failed. SUMMARY = "AWS IoT SDK EMBEDDED C" SECTION = "examples"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
SRC_URI = "file://CMakeLists.txt"
S = "${WORKDIR}"
inherit cmake
EXTRA_OECMAKE = ""
I know it is wrong, but kindly please someone help to write it correctly, thank you. Thanks & Regards, VR
|
|
|
|
Re: #yocto
#yocto
Nicolas Jeker
Hi Steve
On Tue, 2020-12-01 at 20:06 +0000, Monsees, Steven C (US) via lists.yoctoproject.org wrote: I'm not sure to what lines you refer by "banner", so I just wrote my thoughts to both below. Both are probably produced by getty, either util-linux-agetty or systemd-getty. Thanks,This "banner" output is the content of /etc/issue (which gets installed by the base-file package). -sh: cannot set terminal process group (1137): Inappropriate ioctlThe error you see about the shell is probably getty failing to open a shell. Maybe this could be relevant: https://unix.stackexchange.com/questions/338214/error-trying-to-run-agetty-in-a-runit-based-linux-installation .
|
|
|
|
qt5 directory not creating using qt5.15.0 master branch
sateesh m
Hi Guys,
I am trying to build qt support image to my yocto .I am using meta-qt5 master sources,after build its not creating qt5 directory path in the /usr/lib path as well as /usr/share/path but . but when i build x86 its created x86 i got : $ /usr/share/qt5$ ls $usr/lib/qt5/bin$ ls can you please help me if anyone knows this issue. thanks in advance. Regards, Sateesh
|
|
|
|
Re: Raspberry PI enabling MMC1
chuck kamas
Thank you all. That is good information to know! However, I already had a custom machine config that I was able to drop the overlay into. Once I had the correct overlay enabling the sdio, the SD card works!
Thanks again for all of your help.
On 11/20/20 4:22 AM, Erik Boto wrote:
On Thu, Nov 19, 2020 at 7:21 PM chuck kamas via lists.yoctoproject.org <chuckkamas=yahoo.com@...> wrote:Making some progress here! I added a compiled version of the attached device tree and now the mmc1 shows up in my yocto image! Yes! Now I need to find out the secret magic in that tree that I need to add...If I'm not mistaken that should be done by appending RPI_KERNEL_DEVICETREE_OVERLAYS. If you don't have your own custom machine configuration where this could be added, try adding the following to local.conf: RPI_KERNEL_DEVICETREE_OVERLAYS_append = " overlays/sdio.dtbo " Cheers, ErikChuck On 11/18/20 7:59 PM, chuck kamas via lists.yoctoproject.org wrote: Raj, I found out how to debug the boot process of the PI from: https://github.com/raspberrypi/documentation/blob/master/hardware/raspberrypi/bootmodes/README.md by turning on the boot code debug. sed -i -e "s/BOOT_UART=0/BOOT_UART=1/" bootcode.bin I found out that the sdio overlay does not exist! MESS:00:00:07.868162:0: dtdebug: Failed to open overlay file 'overlays/sdio.dtbo' MESS:00:00:07.874093:0: Failed to load overlay 'sdio' MESS:00:00:07.878881:0: brfs: File read: /mfs/sd/overlays/sdio.dtbo MESS:00:00:07.891322:0: brfs: File read: /mfs/sd/cmdline.txt So what am I missing on how to turn on the sdio on GPIO22-27? Is it not an overlay and instead a driver/other code/linux config that needs to be set? Chuck On 11/17/20 4:29 PM, chuck kamas via lists.yoctoproject.org wrote: Raj, Thanks for taking the time to respond. I thought of that too. My custom Yocto build has the line to turn on the sdio in it: dtoverlay=sdio,poll_once=off I have attached the entire file: config.txt.yocto However, the Rasbian image does not have any mention of the dtoverlay for the sdio. Curious. See config.txt attached. Thanks for the help! Chuck On 11/17/20 12:08 AM, Khem Raj wrote: On Mon, Nov 16, 2020 at 11:43 PM chuck kamas via lists.yoctoproject.org <chuckkamas=yahoo.com@...> wrote: Hi all, I have been spinning my wheels for two days trying to discover how to enable MMC1 on a CM3. This is the one on GPIO22-27. I can boot Rasbian on the CM3 and it inits the MMC1 and its pins just fine. I can read/write to my SD card from it etc. However, when I build yocto it leaves the GPIOS22-27 in gpio mode and does not set them to MMC1 mode. I have tried changing the device tree as described here: https://stackoverflow.com/questions/44702426/how-to-setup-an-own-device-tree-for-a-raspberrypi-in-yocto That compiles and add the .dtbo to my build, but still the GPIOS are not set to MMC1 mode. cat /sys/kernel/debug/pinctrl/*gpio*/pinmux-pins Pinmux settings per pin Format: pin (name): mux_owner gpio_owner hog? .... pin 22 (gpio22): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 23 (gpio23): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 24 (gpio24): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 25 (gpio25): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 26 (gpio26): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 27 (gpio27): (MUX UNCLAIMED) (GPIO UNCLAIMED) ..... I have looked at: https://ralimtek.com/raspberry%20pi/electronics/software/raspberry_pi_secondary_sd_card/ Any ideas of where to look next to turn on the sdio would be appreciated! what does /boot/config.txt look like on raspbian and yocto built images Chuck
|
|
|
|
Re: #yocto
#yocto
Monsees, Steven C (US)
I still haven’t been able to track this down, can someone tell me in what package is the banner output generated ?
Thanks, Steve
From: yocto@... [mailto:yocto@...]
On Behalf Of Monsees, Steven C (US) via lists.yoctoproject.org
Sent: Wednesday, November 18, 2020 8:08 AM To: yocto@... Subject: [yocto] #yocto
***
WARNING
***
I was going through the kernel boot output and saw the following output, can someone tell me why this might be popping up and how I might modify configuration to resolve? : . . LIMWS (BAE LIMWS base distro) 3.0.4 sbcb-default ttyS0
-sh: cannot set terminal process group (1137): Inappropriate ioctl for device -sh: no job control in this shell . .
Thanks, Steve
|
|
|
|
Adding modules to Apache2 during build
mailings@...
Hello all:
Thank you to all who post to help on the list. I have been helped so many times by just doing a search here. I do have a question that I have been unable to solve on my own... I have Apache2 and PHP installed and functional. I have also included "PAM" using: PACKAGECONFIG_pn-php = " sqlite3 imap opcache openssl ${@bb.utils.filter('DISTRO_FEATURES', 'ipv6 pam', d)} apache2" However, I need to add "libapache2-mod-authnz-external", "pwauth", and "libapache2-mod-authz-unixgroup" to my build. I've tried adding these to my local.conf in the line above and even tried it in my IMAGE_INSTALL_append section. When I add it to PACKAGECONFIG_pn-php I get a "do_configure: QA Issue" that it is an invalid packageconfig. If I put it in IMAGE_INSTALL_appeng I get an error that nothing provides the packages. I know I'm missing something or not thinking of this correctly. Maybe it's not that I need to add a new package, but a module feature to Apache2? If someone could point me to where I can find an answer, I would appreciate it. Thanks much. -Joe
|
|
|
|
Re: [docs] Yocto Project Technical Documentation Request For Quote
On Tue, Dec 1, 2020 at 7:32 PM akuster808 <akuster808@...> wrote:
Good idea. I've done it now! -armin
|
|
|
|
Re: [docs] Yocto Project Technical Documentation Request For Quote
On 11/30/20 11:42 PM, Nicolas Dechesne wrote:
hi there,Should this be posted on the YP Jobs page? -armin
|
|
|
|
Yocto Project Status WW48'20
Stephen Jolley
Current Dev Position: YP 3.3 M1 development Next Deadline: 7th December 2020 YP 3.3 M1 build
Next Team Meetings:
Key Status/Updates:
Ways to contribute:
YP 3.3 Milestone Dates:
Planned upcoming dot releases:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|
|
|
Re: QA notification for completed autobuilder build (yocto-3.1.4.rc1)
Sangeeta Jain
Hello all,
toggle quoted messageShow quoted text
This is the full report for yocto-3.1.4.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high milestone defects. new issue found BUG id:14138 - [QA 3.1.4 RC1] failure in oe-core manual test: test_bitbake_devshell Bugs verified: BUG id:14071 - [QA 3.1.3 RC1] failure in ptest : perl.t/re/pat Verified Fixed. Existing bugs observed in this release: BUG id:14055 - [QA 3.2 M3 RC1] failure in oe-core manual test: test_dependency_explorer_is_launched ======= Bugs ======== https://bugzilla.yoctoproject.org/show_bug.cgi?id=14138 https://bugzilla.yoctoproject.org/show_bug.cgi?id=14071 https://bugzilla.yoctoproject.org/show_bug.cgi?id=14055 Thanks, Sangeeta
-----Original Message-----
|
|
|