[oe] UART keyboard as /dev/input?
How can I get a UART keyboard to show up in `/dev/input/`? I believe `inputattach` was the tool that was favored until some years ago, but it appears that it no longer is being used in modern Linux systems. I can't seem to find the replacement for it, however. Apologies if this question isn't suitable for this list. Feel free to suggest me another list. Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] "make clean" on Weston
Neither "bitbake -c clean weston" nor "bitbake -c cleanall weston" seems to
clean the build directory for me.
Is this how it is for autotool project? "make clean" doesn't work either
("no rule to make target clean").
I need my directory cleaned so I can commit only the necessary changes.
/build/workspace/sources/weston$ git status
On branch devtool
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified: Makefile.am
modified: Makefile.in
modified: aclocal.m4
modified: build-aux/compile
modified: build-aux/config.guess
modified: build-aux/config.sub
modified: build-aux/depcomp
modified: build-aux/install-sh
modified: build-aux/ltmain.sh
modified: build-aux/missing
modified: build-aux/test-driver
modified: clients/ivi-shell-user-interface.c
modified: clients/simple-egl.c
modified: clients/simple-touch.c
modified: config.h.in
modified: configure
modified: ivi-shell/hmi-controller.c
modified: ivi-shell/ivi-layout.c
modified: ivi-shell/ivi-shell.c
modified: libweston/input.c
modified: libweston/libinput-device.c
modified: m4/libtool.m4
modified: m4/ltoptions.m4
modified: m4/ltsugar.m4
modified: m4/ltversion.m4
modified: m4/lt~obsolete.m4
Adam
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] devtool add recipe with no srctree / fetchuri?
Got it. Thank you for the prompt response. On Mon, Jul 30, 2018 at 10:18 AM Burton, Ross wrote: > devtool add's primary convenience is how it can examine the source and > write the LICENSE correctly, the correct inherits, etc. If you're > just going to install a few files then just write a recipe from > scratch. > > Ross > > On 30 July 2018 at 15:10, Adam Lee wrote: > > Is it possible to run 'devtool add [recipe-name]' without 'srctree' or > > 'fetchuri'? > > I just want to add a simple recipe with a few files to be installed on > the > > target file system. > > I can directly add a file in my meta-layer, but devtool is probably the > more > > correct approach. > > > > Adam > > > > -- > > ___ > > Openembedded-core mailing list > > openembedded-c...@lists.openembedded.org > > http://lists.openembedded.org/mailman/listinfo/openembedded-core > > > -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] devtool add recipe with no srctree / fetchuri?
Is it possible to run 'devtool add [recipe-name]' without 'srctree' or 'fetchuri'? I just want to add a simple recipe with a few files to be installed on the target file system. I can directly add a file in my meta-layer, but devtool is probably the more correct approach. Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-qt5] Has anyone been able to run minimal-qml (or any Wayland) example?
Perhaps QT Wayland Compositor needs to be backed by a backend that supports underlying graphics driver. Such thing exists for i.Mx6 Vivante [1], but not for AM57xx EVM. [1] http://blog.qt.io/blog/2015/11/17/embedded-linux-news-in-qt-5-6/ On Tue, Mar 6, 2018 at 12:23 PM Adam Lee <adam.yh@gmail.com> wrote: > I'd like to try out a Wayland example [1]. It can be found in > "/usr/share/qt5/examples/wayland". > Unfortunately I have not been able to run it on Rocko with AM57xx EVM from > TI. > Has anyone successfully ran this example application at all..? I just want > to be sure that there is a working example somewhere out there. > > [1] https://doc.qt.io/qt-5.10/qtwaylandcompositor-examples.html > -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-qt5] Has anyone been able to run minimal-qml (or any Wayland) example?
I'd like to try out a Wayland example [1]. It can be found in "/usr/share/qt5/examples/wayland". Unfortunately I have not been able to run it on Rocko with AM57xx EVM from TI. Has anyone successfully ran this example application at all..? I just want to be sure that there is a working example somewhere out there. [1] https://doc.qt.io/qt-5.10/qtwaylandcompositor-examples.html -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-qt5] Problem with /default-qt/tooldir
Building on git #db881bb4917628ad, my images are showing these errors: # qmake qmake: could not exec '/default-qt/tooldir/qmake': No such file or directory # qmlviewer qmlviewer: could not exec '/default-qt/tooldir/qmlviewer': No such file or directory Has anyone else seen this lately? BR, Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-qt5] File name too long error while building qtwebengine
I am on meta-qt5 master (# 06d1c47396508), but this happens on Rocko as well. *| ninja: error: WriteFile(__third_party_WebKit_Source_bindings_modules_v8_bindings_modules_v8_generated_init_partial__home_build_tisdk-rocko-glibc_work_armv7ahf-neon-oe-linux-gnueabi_qtwebengine_5.9.2_gitAUTOINC_c11c2c8981_cfe8* *c60903-r0_build_src_toolchain_target__rule.rsp): Unable to create file. File name too long* | ninja: build stopped: . | Makefile.gn_run:321: recipe for target 'run_ninja' failed | make[3]: *** [run_ninja] Error 1 | make[3]: Leaving directory '/home/build/tisdk-rocko-glibc/work/armv7ahf-neon-oe-linux-gnueabi/qtwebengine/5.9.2+gitAUTOINC+c11c2c8981_cfe8c60903-r0/build/src/core' | Makefile:80: recipe for target 'sub-gn_run-pro-make_first' failed | make[2]: *** [sub-gn_run-pro-make_first] Error 2 | make[2]: Leaving directory '/home/build/tisdk-rocko-glibc/work/armv7ahf-neon-oe-linux-gnueabi/qtwebengine/5.9.2+gitAUTOINC+c11c2c8981_cfe8c60903-r0/build/src/core' | Makefile:78: recipe for target 'sub-core-make_first' failed | make[1]: *** [sub-core-make_first] Error 2 | make[1]: Leaving directory '/home/build/tisdk-rocko-glibc/work/armv7ahf-neon-oe-linux-gnueabi/qtwebengine/5.9.2+gitAUTOINC+c11c2c8981_cfe8c60903-r0/build/src' | Makefile:46: recipe for target 'sub-src-make_first' failed | make: *** [sub-src-make_first] Error 2 | ERROR: oe_runmake failed | WARNING: /home/build/tisdk-rocko-glibc/work/armv7ahf-neon-oe-linux-gnueabi/qtwebengine/5.9.2+gitAUTOINC+c11c2c8981_cfe8c60903-r0/temp/run.do_compile.35312:1 exit 1 from 'exit 1' | ERROR: Function failed: do_compile (log file is located at /home/build/tisdk-rocko-glibc/work/armv7ahf-neon-oe-linux-gnueabi/qtwebengine/5.9.2+gitAUTOINC+c11c2c8981_cfe8c60903-r0/temp/log.do_compile.35312) ERROR: Task (/home/build/tisdk-rocko/sources/meta-qt5/recipes-qt/qt5/qtwebengine_git.bb:do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 1972 tasks of which 1965 didn't need to be rerun and 1 failed. Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] Using QT_DIR_NAME; Correct way of flattening QT5 directory structure?
My system only runs Qt5. Hence no need to have `qmake` and others in `/usr/bin/qt5`. I prefer to have them in `/usr/bin`. JaMa's comment[1] seems to suggest that all it takes is setting `QT_DIR_NAME` to an empty string. With this, I get tonnes of QA errors because `FILES_` paths now contain `//`, which is the right behavior as per the manual[2]. For example: $ bitbake qttools -e | grep FILES_qttools-mkspecs # $FILES_qttools-mkspecs FILES_qttools-mkspecs="/usr/lib//mkspecs " And the corresponding error being this: WARNING: QA Issue: FILES variable for package qttools-mkspecs contains '//' which is invalid. Attempting to fix this but you should correct the metadata. [files-invalid] The build system [seems to] successfully correct the issue, and I see the files in the resulting rootfs. That said, I am either doing something incorrect, or something has to be fixed. [1] http://lists.openembedded.org/pipermail/openembedded-devel/2014-February/094232.html [2] http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-issue-files-invalid -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] Extensible SDK install errors
Great, thanks Randy for the pointer. No need for apology. I fully understand this is a work-in-progress. I just want to stay on par with the development! On Tue, Aug 25, 2015 at 7:33 PM Randy Witt rew...@declaratino.com wrote: On Tue, Aug 25, 2015 at 6:11 PM, Adam Lee adam.yh@gmail.com wrote: Thanks for your comments. I was not running the installer as root. I tried again and specified the install path in my home directory. This time it seems to have gone further, but still failed with this: error: Can't install packagegroup-core-boot-1.0-r17.0@qemuarm: no package provides systemd Perhaps I need to disable systemd from distro features? You could do that, however there is a patch on the list to fix this kind of problem. http://patchwork.openembedded.org/patch/101213/ It may fix your problem until the next release comes out. I'm sorry you've had this trouble. It was just something that was missed in the first version of the extensible sdk. I will also check my user's permission to solve the permission error. On Mon, Aug 24, 2015 at 4:11 AM Paul Eggleton paul.eggle...@linux.intel.com wrote: Hi Adam, On Friday 21 August 2015 15:06:25 Adam Lee wrote: Hello, I built the Extensible SDK on Fido (bitbake core-image-minimal -c populate_sdk_ext). During the installation I get this permission error: $ ./poky-glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-1.8.sh Enter target directory for SDK (default: /opt/poky/1.8): You are about to install the SDK to /opt/poky/1.8. Proceed[Y/n]? Extracting SDK...done Setting it up... Extracting buildtools... ./poky-glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-1.8.sh: line 148: /opt/poky/1.8/environment-setup-armv5e-poky-linux-gnueabi: Permission denied ./poky-glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-1.8.sh: line 151: /opt/poky/1.8/environment-setup-armv5e-poky-linux-gnueabi: Permission denied ./poky-glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-1.8.sh: line 155: /opt/poky/1.8/environment-setup-armv5e-poky-linux-gnueabi: Permission denied mv: cannot move ‘x86_64-nativesdk-libc.tar.bz2’ to ‘/opt/poky/1.8/layers/poky/x86_64-nativesdk-libc.tar.bz2’: Permission denied Preparing build system... sh: 1: cannot create preparing_build_system.log: Permission denied SDK preparation failed: see /opt/poky/1.8/preparing_build_system.log It looks like `/opt/poky/1.8/layers/poky` directory belongs to the root user: $ ls -l /opt/poky/1.8/layers/ total 36 drwxrwxr-x 9 root root 4096 Jun 16 10:25 meta-gnome drwxrwxr-x 9 root root 4096 Jun 15 10:44 meta-multimedia drwxrwxr-x 11 root root 4096 Jun 15 10:44 meta-networking drwxrwxr-x 20 root root 4096 Jun 15 10:44 meta-oe drwxrwxr-x 7 root root 4096 Jun 15 10:44 meta-python drwxrwxr-x 5 root root 4096 Jun 15 10:44 meta-ruby drwxrwxr-x 5 root root 4096 Jun 15 10:44 meta-systemd drwxrwxr-x 11 root root 4096 Jun 15 10:44 meta-xfce drwxrwxr-x 13 root root 4096 Aug 21 14:46 poky I may have missed something obvious. Has anyone seen this? Basically you shouldn't be installing the extensible SDK as root. We ought to be telling you about this up front and we should have a more reasonable default path - these are open bugs and patches are in review on the list to fix them. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Extensible SDK install errors
Thanks for your comments. I was not running the installer as root. I tried again and specified the install path in my home directory. This time it seems to have gone further, but still failed with this: error: Can't install packagegroup-core-boot-1.0-r17.0@qemuarm: no package provides systemd Perhaps I need to disable systemd from distro features? I will also check my user's permission to solve the permission error. On Mon, Aug 24, 2015 at 4:11 AM Paul Eggleton paul.eggle...@linux.intel.com wrote: Hi Adam, On Friday 21 August 2015 15:06:25 Adam Lee wrote: Hello, I built the Extensible SDK on Fido (bitbake core-image-minimal -c populate_sdk_ext). During the installation I get this permission error: $ ./poky-glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-1.8.sh Enter target directory for SDK (default: /opt/poky/1.8): You are about to install the SDK to /opt/poky/1.8. Proceed[Y/n]? Extracting SDK...done Setting it up... Extracting buildtools... ./poky-glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-1.8.sh: line 148: /opt/poky/1.8/environment-setup-armv5e-poky-linux-gnueabi: Permission denied ./poky-glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-1.8.sh: line 151: /opt/poky/1.8/environment-setup-armv5e-poky-linux-gnueabi: Permission denied ./poky-glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-1.8.sh: line 155: /opt/poky/1.8/environment-setup-armv5e-poky-linux-gnueabi: Permission denied mv: cannot move ‘x86_64-nativesdk-libc.tar.bz2’ to ‘/opt/poky/1.8/layers/poky/x86_64-nativesdk-libc.tar.bz2’: Permission denied Preparing build system... sh: 1: cannot create preparing_build_system.log: Permission denied SDK preparation failed: see /opt/poky/1.8/preparing_build_system.log It looks like `/opt/poky/1.8/layers/poky` directory belongs to the root user: $ ls -l /opt/poky/1.8/layers/ total 36 drwxrwxr-x 9 root root 4096 Jun 16 10:25 meta-gnome drwxrwxr-x 9 root root 4096 Jun 15 10:44 meta-multimedia drwxrwxr-x 11 root root 4096 Jun 15 10:44 meta-networking drwxrwxr-x 20 root root 4096 Jun 15 10:44 meta-oe drwxrwxr-x 7 root root 4096 Jun 15 10:44 meta-python drwxrwxr-x 5 root root 4096 Jun 15 10:44 meta-ruby drwxrwxr-x 5 root root 4096 Jun 15 10:44 meta-systemd drwxrwxr-x 11 root root 4096 Jun 15 10:44 meta-xfce drwxrwxr-x 13 root root 4096 Aug 21 14:46 poky I may have missed something obvious. Has anyone seen this? Basically you shouldn't be installing the extensible SDK as root. We ought to be telling you about this up front and we should have a more reasonable default path - these are open bugs and patches are in review on the list to fix them. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] Extensible SDK install errors
Hello, I built the Extensible SDK on Fido (bitbake core-image-minimal -c populate_sdk_ext). During the installation I get this permission error: $ ./poky-glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-1.8.sh Enter target directory for SDK (default: /opt/poky/1.8): You are about to install the SDK to /opt/poky/1.8. Proceed[Y/n]? Extracting SDK...done Setting it up... Extracting buildtools... ./poky-glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-1.8.sh: line 148: /opt/poky/1.8/environment-setup-armv5e-poky-linux-gnueabi: Permission denied ./poky-glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-1.8.sh: line 151: /opt/poky/1.8/environment-setup-armv5e-poky-linux-gnueabi: Permission denied ./poky-glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-1.8.sh: line 155: /opt/poky/1.8/environment-setup-armv5e-poky-linux-gnueabi: Permission denied mv: cannot move ‘x86_64-nativesdk-libc.tar.bz2’ to ‘/opt/poky/1.8/layers/poky/x86_64-nativesdk-libc.tar.bz2’: Permission denied Preparing build system... sh: 1: cannot create preparing_build_system.log: Permission denied SDK preparation failed: see /opt/poky/1.8/preparing_build_system.log It looks like `/opt/poky/1.8/layers/poky` directory belongs to the root user: $ ls -l /opt/poky/1.8/layers/ total 36 drwxrwxr-x 9 root root 4096 Jun 16 10:25 meta-gnome drwxrwxr-x 9 root root 4096 Jun 15 10:44 meta-multimedia drwxrwxr-x 11 root root 4096 Jun 15 10:44 meta-networking drwxrwxr-x 20 root root 4096 Jun 15 10:44 meta-oe drwxrwxr-x 7 root root 4096 Jun 15 10:44 meta-python drwxrwxr-x 5 root root 4096 Jun 15 10:44 meta-ruby drwxrwxr-x 5 root root 4096 Jun 15 10:44 meta-systemd drwxrwxr-x 11 root root 4096 Jun 15 10:44 meta-xfce drwxrwxr-x 13 root root 4096 Aug 21 14:46 poky I may have missed something obvious. Has anyone seen this? Thanks! -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] OpenCV Java binding, and Java JNI
Hello everyone! Has anyone successfully built the OpenCV recipe with Java binding? I don't see any .jar files or shared objects. In the log I see these messages: -- Could NOT find JNI (missing: JAVA_AWT_LIBRARY JAVA_JVM_LIBRARY JAVA_INCLUDE_PATH JAVA_INCLUDE_PATH2 JAVA_AWT_INCLUDE_PATH) -- packages path: lib/python2.7/site-packages -- Java: -- ant: /build/tmp/sysroots/x86_64-linux/usr/bin/ant (ver 1.8.1) -- JNI: NO I looked at my bitbake environment variables, but can't find any of the missing variables above. I'm on Yocto 1.7, and meta-java is on master branch. The host is Ubuntu 15.04. Thanks, Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] Reference to sysroot in PHP packages
On Yocto 1.7.1, running `bitbake php` will show a QA warning: WARNING: QA Issue: php requires /media/Build/master/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/php/5.4.36-r0/image/usr/bin/php, but no providers in its RDEPENDS [file-rdeps] Doing a grep for sysroot within the packages-split directory shows a number of references: root@pine:/media/Build/master/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/php/5.4.36-r0/packages-split# grep media/Build/master/build/tmp/sysroots/x86_64-linux -r . ./php-pear/usr/bin/pear: if test /media/Build/master/build/tmp/sysroots/x86_64-linux/usr/bin/php = '@'php_bin'@'; then ./php-pear/usr/bin/pear: PHP=/media/Build/master/build/tmp/sysroots/x86_64-linux/usr/bin/php ./php-pear/usr/bin/peardev: if test /media/Build/master/build/tmp/sysroots/x86_64-linux/usr/bin/php = '@'php_bin'@'; then ./php-pear/usr/bin/peardev: PHP=/media/Build/master/build/tmp/sysroots/x86_64-linux/usr/bin/php ./php-pear/usr/bin/pecl: if test /media/Build/master/build/tmp/sysroots/x86_64-linux/usr/bin/php = '@'php_bin'@'; then ./php-pear/usr/bin/pecl: PHP=/media/Build/master/build/tmp/sysroots/x86_64-linux/usr/bin/php I believe this problem also results in the failure of populate_sdk task. -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] Packages builds on one MACHINE but not on the other
Hello everyone, I have been trying to put a webserver (nginx) in conjunction with uwsgi on my OMAP4 board. The issue I am having is that uwsgi package (from meta-virtualization / meta-openstack) builds ok on qumu86, but neither on qumuarm nor on my OMAP4 based board. The exact problem is the binary contains an RPATH to the builder's local path. I guess I can disable 'insane' checking, but I am hoping someone can provide some insights as to where to look to solve the issue. Adam DEBUG: Executing python function sstate_task_prefunc DEBUG: Python function sstate_task_prefunc finished DEBUG: Executing python function do_package DEBUG: Executing python function package_get_auto_pr DEBUG: Python function package_get_auto_pr finished DEBUG: Executing python function perform_packagecopy DEBUG: Python function perform_packagecopy finished DEBUG: Executing python function split_and_strip_files DEBUG: runstrip: 'arm-poky-linux-gnueabi-strip' --remove-section=.comment --remove-section=.note '/media/Build/master/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/uwsgi/2.0.4+gitAUTOINC+7604c67018-r0/package/usr/bin/uwsgi' DEBUG: Python function split_and_strip_files finished DEBUG: Executing python function fixup_perms DEBUG: Python function fixup_perms finished DEBUG: Executing python function package_do_split_locales DEBUG: No locale files in this package DEBUG: Python function package_do_split_locales finished DEBUG: Executing python function populate_packages DEBUG: Python function populate_packages finished DEBUG: Executing python function do_package_qa NOTE: DO PACKAGE QA NOTE: Checking Package: uwsgi-staticdev NOTE: Checking Package: uwsgi-dev NOTE: Checking Package: uwsgi-dbg NOTE: arm-poky-linux-gnueabi-objdump -p /media/Build/master/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/uwsgi/2.0.4+gitAUTOINC+7604c67018-r0/packages-split/uwsgi-dbg/usr/bin/.debug/uwsgi NOTE: Checking Package: uwsgi-doc NOTE: Checking Package: uwsgi NOTE: arm-poky-linux-gnueabi-objdump -p /media/Build/master/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/uwsgi/2.0.4+gitAUTOINC+7604c67018-r0/packages-split/uwsgi/usr/bin/uwsgi ERROR: QA Issue: package uwsgi contains bad RPATH /media/Build/master/build/tmp/sysroots/duovero/usr/lib in file /media/Build/master/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/uwsgi/2.0.4+gitAUTOINC+7604c67018-r0/packages-split/uwsgi/usr/bin/uwsgi ERROR: QA run found fatal errors. Please consider fixing them. DEBUG: Python function do_package_qa finished DEBUG: Python function do_package finished ERROR: Function failed: do_package_qa -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] Installing RPM packages in SDK sysroot
Hello everyone, in the section 4.2. Configuring the PMS of the Yocto ADT manual, it describes adding packages to a target sysroot using OPKG. This method works well as documented. However my choice of package manager is Yocto's default - RPM. And I was not able to successfully install RPM packages in the SDK sysroot. Ultimately, I think installing RPM packages using SmartPM fails because the list of installed packages is not included in the SDK sysroot. A deployable image contains a file called Packages in /var/lib/rpm. The SDK sysroot does not have this file and shows 0 installed packages when I run `smart stats`. Note that when I am using OPKG instead of RPM, I have the equivalent package index file in /var/lib/opkg/lists for both sysroot and deployable images. I can still attempt to install a package, but it quite literally wants to rebuild the entire rootfs. For example, running `smart install opencv-dev` warns that it has to install 400 packages. These packages include base-files, bash, m4, make, python-dev etc. So this makes me think that either RPM is not supported in SDK sysroot or the feature is incomplete. It's also possible that I have missed an important detail. I will be looking into the sdk class and the package manager class to see what's really happening. In the meanwhile I'd appreciate if someone can provide some pointers! Thanks, Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] initramfs only supported in x86?
Hi Khem, thanks for your pointers. Just gave that a shot, and my initramfs uImage actually takes longer to boot (at about 9 seconds from cold to user space vs 7 seconds before). Good data point! Adam On Thu, May 15, 2014 at 10:41 PM, Khem Raj raj.k...@gmail.com wrote: On Thu, May 15, 2014 at 1:33 PM, Nicolas Dechesne nicolas.deche...@linaro.org wrote: On Thu, May 15, 2014 at 7:13 PM, Adam Lee adam.yh@gmail.com wrote: Hello everyone, I thought I'd compare the performance of booting rootfs from MMC vs ramdisk (the way Android is doing it). Some says it may possibly take longer in ramdisk because the rootfs has to be first loaded into memory. I'd like to test it out myself. So I discovered core-image-minimal-initramfs, and thought it was exactly what I needed. However the build doesn't go far, because its dependency initramfs-live-install [1] only seems to support x86: live images are for x86 only because it uses syslinux and friends. However you can choose any other image to become initramfs image and bunsle it into kernel you have to use INITRAMFS_IMAGE = your-initramfs-image INITRAMFS_IMAGE_BUNDLE = 1 COMPATIBLE_HOST = (i.86|x86_64).*-linux Is this the limitation of current OE? or am I just looking at the wrong corner? i recently had to build an initrd too, and notice that as well... so i am not sure exactly what that means. I am glad you asked... however if you want to test an initrd, you can simply build *any* image and make sure to build the 'cpio' from IMAGE_FSTYPES. you can then use the generated cpio archive as an inited. -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] initramfs only supported in x86?
Hello everyone, I thought I'd compare the performance of booting rootfs from MMC vs ramdisk (the way Android is doing it). Some says it may possibly take longer in ramdisk because the rootfs has to be first loaded into memory. I'd like to test it out myself. So I discovered core-image-minimal-initramfs, and thought it was exactly what I needed. However the build doesn't go far, because its dependency initramfs-live-install [1] only seems to support x86: COMPATIBLE_HOST = (i.86|x86_64).*-linux Is this the limitation of current OE? or am I just looking at the wrong corner? Thanks, Adam [1]http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/initrdscripts/initramfs-live-install_1.0.bb?h=daisy -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] initramfs only supported in x86?
Hi Nicolas, thanks for your response. I built core-image-minimal in cpio, but the size is whopping 69MB. It will take a couple seconds just to load the image into the memory, which defeats the purpose of using the ramdisk to boot. After watching 300 ms from reset-to-shell boot video [1] using 1.5MB large kernel + rootfs combined, the size of the core-image-minimal feels gargantuan and my boot time of ~7 seconds feels like an eternity. That said, my goal is to reduce the boot time through optimization of the current image. Writing custom boot loader or severely crippling the rootfs is out of scope. So I thought the tested and proven core-image-minimal-initramfs would be a great start. Adam [1] http://www.makelinux.com/emb/fastboot/omap On Thu, May 15, 2014 at 1:33 PM, Nicolas Dechesne nicolas.deche...@linaro.org wrote: On Thu, May 15, 2014 at 7:13 PM, Adam Lee adam.yh@gmail.com wrote: Hello everyone, I thought I'd compare the performance of booting rootfs from MMC vs ramdisk (the way Android is doing it). Some says it may possibly take longer in ramdisk because the rootfs has to be first loaded into memory. I'd like to test it out myself. So I discovered core-image-minimal-initramfs, and thought it was exactly what I needed. However the build doesn't go far, because its dependency initramfs-live-install [1] only seems to support x86: COMPATIBLE_HOST = (i.86|x86_64).*-linux Is this the limitation of current OE? or am I just looking at the wrong corner? i recently had to build an initrd too, and notice that as well... so i am not sure exactly what that means. I am glad you asked... however if you want to test an initrd, you can simply build *any* image and make sure to build the 'cpio' from IMAGE_FSTYPES. you can then use the generated cpio archive as an initrd. -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] initramfs only supported in x86?
ah I spoke too soon. I had extra DISTRO_FEATURES. I removed them and the root is ~2.5MB. Now it's worth a try. Adam On Thu, May 15, 2014 at 3:58 PM, Adam Lee adam.yh@gmail.com wrote: Hi Nicolas, thanks for your response. I built core-image-minimal in cpio, but the size is whopping 69MB. It will take a couple seconds just to load the image into the memory, which defeats the purpose of using the ramdisk to boot. After watching 300 ms from reset-to-shell boot video [1] using 1.5MB large kernel + rootfs combined, the size of the core-image-minimal feels gargantuan and my boot time of ~7 seconds feels like an eternity. That said, my goal is to reduce the boot time through optimization of the current image. Writing custom boot loader or severely crippling the rootfs is out of scope. So I thought the tested and proven core-image-minimal-initramfs would be a great start. Adam [1] http://www.makelinux.com/emb/fastboot/omap On Thu, May 15, 2014 at 1:33 PM, Nicolas Dechesne nicolas.deche...@linaro.org wrote: On Thu, May 15, 2014 at 7:13 PM, Adam Lee adam.yh@gmail.com wrote: Hello everyone, I thought I'd compare the performance of booting rootfs from MMC vs ramdisk (the way Android is doing it). Some says it may possibly take longer in ramdisk because the rootfs has to be first loaded into memory. I'd like to test it out myself. So I discovered core-image-minimal-initramfs, and thought it was exactly what I needed. However the build doesn't go far, because its dependency initramfs-live-install [1] only seems to support x86: COMPATIBLE_HOST = (i.86|x86_64).*-linux Is this the limitation of current OE? or am I just looking at the wrong corner? i recently had to build an initrd too, and notice that as well... so i am not sure exactly what that means. I am glad you asked... however if you want to test an initrd, you can simply build *any* image and make sure to build the 'cpio' from IMAGE_FSTYPES. you can then use the generated cpio archive as an initrd. -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] systemd networking.service masked?
I am really just trying to auto bringup eth0 on boot. Christopher, I don't have dhcpcd, so I enabled udhcpc@eth0. No dice. Is dhcpcd@eth0 how you guys bring up on boot? I've been using udhcpc for my wireless connections and I have no complain. Thank you, Adam On Mon, May 5, 2014 at 5:41 PM, Stephen Arnold stephen.arnol...@gmail.com wrote: Well, none of my rpi or bbb images use systemd/connman/networkmanager and I'm just fine with that as the baseline. Steve On Mon, May 5, 2014 at 5:37 PM, Christopher Larson clar...@kergoth.comwrote: On Mon, May 5, 2014 at 5:31 PM, Adam Lee adam.yh@gmail.com wrote: I noticed networking.service is masked by default - http://cgit.openembedded.org/cgit.cgi/openembedded-core/tree/meta/recipes-core/systemd/systemd-compat-units.bb?h=master . I guess I can use the Network Manager to bring up eth0 on boot, but I rather not. What's the harm in networking.service? Is it really needed? Does systemctl enable dhcpcd@eth0 not do the job, or am I missing something? -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] systemd networking.service masked?
ok scratch what I said an hour ago. I had dhclient along with udhcpc installed on my system. I took dhclient out and systemctl enable udhcpc@eth0 works. Adam On Tue, May 6, 2014 at 9:52 AM, Adam Lee adam.yh@gmail.com wrote: I am really just trying to auto bringup eth0 on boot. Christopher, I don't have dhcpcd, so I enabled udhcpc@eth0. No dice. Is dhcpcd@eth0 how you guys bring up on boot? I've been using udhcpc for my wireless connections and I have no complain. Thank you, Adam On Mon, May 5, 2014 at 5:41 PM, Stephen Arnold stephen.arnol...@gmail.com wrote: Well, none of my rpi or bbb images use systemd/connman/networkmanager and I'm just fine with that as the baseline. Steve On Mon, May 5, 2014 at 5:37 PM, Christopher Larson clar...@kergoth.comwrote: On Mon, May 5, 2014 at 5:31 PM, Adam Lee adam.yh@gmail.com wrote: I noticed networking.service is masked by default - http://cgit.openembedded.org/cgit.cgi/openembedded-core/tree/meta/recipes-core/systemd/systemd-compat-units.bb?h=master . I guess I can use the Network Manager to bring up eth0 on boot, but I rather not. What's the harm in networking.service? Is it really needed? Does systemctl enable dhcpcd@eth0 not do the job, or am I missing something? -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] systemd networking.service masked?
Hello everybody! I noticed networking.service is masked by default - http://cgit.openembedded.org/cgit.cgi/openembedded-core/tree/meta/recipes-core/systemd/systemd-compat-units.bb?h=master. I guess I can use the Network Manager to bring up eth0 on boot, but I rather not. What's the harm in networking.service? Thank you, Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] v4l-utils won't build
which branch are you on? I am on master-next for OE and on Daisy on Poky. Both opencv and v4l-utils build ok. Adam On Fri, Apr 25, 2014 at 5:30 PM, Richard Cagley rcag...@gmail.com wrote: On Fri, Apr 25, 2014 at 4:56 PM, Martin Jansa martin.ja...@gmail.com wrote: On Fri, Apr 25, 2014 at 12:56:26PM -0700, Richard Cagley wrote: After running bitbake core-image-minimal I'm trying to run bitbake opencv and I get the below. I've looking through the log files and the v4l-utils recipe. All I can see is that it's unhappy about something to do with the autotools configuration for the project. Any ideas? See http://git.openembedded.org/openembedded-core/commit/?id=baf5b230af919b6b0fd14ac5fc3e734bf7c464d5 and related discussion on ML sorry, i'm too new at this stuff to extract the needed information. Any chance you can give me a bit more guidance? I'm not even sure what to search for in the mailing lists. What's a good procedure to debug this sort of thing? -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] xfce4-dev-tools fails to build on master-next
It looks like autotools bbclass began doing out of tree build. Switching to Poky's 'daisy' branch, which contains a couple of autotools related commits, fixed this issue. On Mon, Apr 21, 2014 at 10:56 AM, Adam Lee adam.yh@gmail.com wrote: I noticed my XFCE image is blocked due to the following: DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common'] DEBUG: Executing shell function do_compile NOTE: make -j 4 Making all in m4macros make[1]: Entering directory `/media/Build/next/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/xfce4-dev-tools/4.11.0-r0/build/m4macros' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/media/Build/next/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/xfce4-dev-tools/4.11.0-r0/build/m4macros' Making all in scripts make[1]: Entering directory `/media/Build/next/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/xfce4-dev-tools/4.11.0-r0/build/scripts' make[1]: *** No rule to make target `/media/Build/next/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/xfce4-dev-tools/4.11.0-r0/xfce4-dev-tools-4.11.0/scripts/xdt-autogen.in', needed by `xdt-autogen'. Stop. make[1]: Leaving directory `/media/Build/next/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/xfce4-dev-tools/4.11.0-r0/build/scripts' make: *** [all-recursive] Error 1 ERROR: oe_runmake failed WARNING: exit code 1 from a shell command. ERROR: Function failed: do_compile (log file is located at /media/Build/next/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/xfce4-dev-tools/4.11.0-r0/temp/log.do_compile.22389) I can only see xdt-autogen.in.in (not xdt-autogen.in) in the scripts directory. This is the same with the previous version however. Has anyone else seen this? Thanks! Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] xfce4-dev-tools fails to build on master-next
I noticed my XFCE image is blocked due to the following: DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common'] DEBUG: Executing shell function do_compile NOTE: make -j 4 Making all in m4macros make[1]: Entering directory `/media/Build/next/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/xfce4-dev-tools/4.11.0-r0/build/m4macros' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/media/Build/next/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/xfce4-dev-tools/4.11.0-r0/build/m4macros' Making all in scripts make[1]: Entering directory `/media/Build/next/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/xfce4-dev-tools/4.11.0-r0/build/scripts' make[1]: *** No rule to make target `/media/Build/next/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/xfce4-dev-tools/4.11.0-r0/xfce4-dev-tools-4.11.0/scripts/xdt-autogen.in', needed by `xdt-autogen'. Stop. make[1]: Leaving directory `/media/Build/next/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/xfce4-dev-tools/4.11.0-r0/build/scripts' make: *** [all-recursive] Error 1 ERROR: oe_runmake failed WARNING: exit code 1 from a shell command. ERROR: Function failed: do_compile (log file is located at /media/Build/next/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/xfce4-dev-tools/4.11.0-r0/temp/log.do_compile.22389) I can only see xdt-autogen.in.in (not xdt-autogen.in) in the scripts directory. This is the same with the previous version however. Has anyone else seen this? Thanks! Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] LXDM failure on master-next
Hello everybody, my image has been booting into shell instead of LXDM ever since I switched to master-next from Dora. I believe LXDM is not compatible with the new systemd, but my knowledge is limited. Here is what I gathered so far: 1.5 Dora: root@overo:~$ cat log | grep -i lxdm Jan 01 00:02:38 overo systemd[1]: Looking at job lxdm.service/start conflicted_by=no Jan 01 00:02:38 overo systemd[1]: Looking at job lxdm.service/stop conflicted_by=no Jan 01 00:02:38 overo systemd[1]: Fixing conflicting jobs by deleting job lxdm.service/stop Jan 01 00:02:38 overo systemd[1]: Installed new job lxdm.service/start as 89 Jan 01 00:02:48 overo systemd[1]: About to execute: /usr/sbin/lxdm Jan 01 00:02:48 overo systemd[1]: Forked /usr/sbin/lxdm as 127 Jan 01 00:02:48 overo systemd[127]: Executing: /usr/sbin/lxdm Jan 01 00:02:53 overo kernel[114]: [4.286621] systemd[1]: Looking at job lxdm.service/start conflicted_by=no Jan 01 00:02:53 overo kernel[114]: [4.286651] systemd[1]: Looking at job lxdm.service/stop conflicted_by=no Jan 01 00:02:53 overo kernel[114]: [4.286682] systemd[1]: Fixing conflicting jobs by deleting job lxdm.service/stop Jan 01 00:02:53 overo kernel[114]: [4.289398] systemd[1]: Installed new job lxdm.service/start as 89 Jan 01 00:02:55 overo kernel[114]: [ 15.754699] systemd[1]: lxdm.service changed dead - running Jan 01 00:02:55 overo kernel[114]: [ 15.754852] systemd[1]: Job lxdm.service/start finished, result=done Jan 01 00:02:55 overo systemd[1]: lxdm.service changed dead - running Jan 01 00:02:55 overo systemd[1]: Job lxdm.service/start finished, result=done root@overo:~$ master-next: root@overo:~$ cat systemd_log | grep -i lxdm Jan 01 00:22:42 overo systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/lxdm_2eservice interface=org.freedesktop.DBus.Properties member=GetAll cookie=1 reply_cookie=0 error=n/a Jan 01 00:22:42 overo systemd[1]: Collecting lxdm.service Jan 01 00:22:42 overo systemd[1]: Failed to send unit change signal for lxdm.service: Transport endpoint is not connected Jan 01 00:22:42 overo systemd[1]: Failed to send unit remove signal for lxdm.service: Transport endpoint is not connected root@overo:~$ Manually starting the service works. Adding the lxdm service to multi-user target works also, however this feels like a hack. Any pointers will be appreciated! Thanks, Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] LXDM failure on master-next
Great! Exactly what I needed. Thanks Andreas, Adam On Thu, Apr 3, 2014 at 11:08 AM, Andreas Müller schnitzelt...@googlemail.com wrote: On Thu, Apr 3, 2014 at 7:52 PM, Adam Lee adam.yh@gmail.com wrote: Hello everybody, my image has been booting into shell instead of LXDM ever since I switched to master-next from Dora. I believe LXDM is not compatible with the new systemd, but my knowledge is limited. Here is what I gathered so far: 1.5 Dora: root@overo:~$ cat log | grep -i lxdm Jan 01 00:02:38 overo systemd[1]: Looking at job lxdm.service/start conflicted_by=no Jan 01 00:02:38 overo systemd[1]: Looking at job lxdm.service/stop conflicted_by=no Jan 01 00:02:38 overo systemd[1]: Fixing conflicting jobs by deleting job lxdm.service/stop Jan 01 00:02:38 overo systemd[1]: Installed new job lxdm.service/start as 89 Jan 01 00:02:48 overo systemd[1]: About to execute: /usr/sbin/lxdm Jan 01 00:02:48 overo systemd[1]: Forked /usr/sbin/lxdm as 127 Jan 01 00:02:48 overo systemd[127]: Executing: /usr/sbin/lxdm Jan 01 00:02:53 overo kernel[114]: [4.286621] systemd[1]: Looking at job lxdm.service/start conflicted_by=no Jan 01 00:02:53 overo kernel[114]: [4.286651] systemd[1]: Looking at job lxdm.service/stop conflicted_by=no Jan 01 00:02:53 overo kernel[114]: [4.286682] systemd[1]: Fixing conflicting jobs by deleting job lxdm.service/stop Jan 01 00:02:53 overo kernel[114]: [4.289398] systemd[1]: Installed new job lxdm.service/start as 89 Jan 01 00:02:55 overo kernel[114]: [ 15.754699] systemd[1]: lxdm.service changed dead - running Jan 01 00:02:55 overo kernel[114]: [ 15.754852] systemd[1]: Job lxdm.service/start finished, result=done Jan 01 00:02:55 overo systemd[1]: lxdm.service changed dead - running Jan 01 00:02:55 overo systemd[1]: Job lxdm.service/start finished, result=done root@overo:~$ master-next: root@overo:~$ cat systemd_log | grep -i lxdm Jan 01 00:22:42 overo systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/lxdm_2eservice interface=org.freedesktop.DBus.Properties member=GetAll cookie=1 reply_cookie=0 error=n/a Jan 01 00:22:42 overo systemd[1]: Collecting lxdm.service Jan 01 00:22:42 overo systemd[1]: Failed to send unit change signal for lxdm.service: Transport endpoint is not connected Jan 01 00:22:42 overo systemd[1]: Failed to send unit remove signal for lxdm.service: Transport endpoint is not connected root@overo:~$ Manually starting the service works. Adding the lxdm service to multi-user target works also, however this feels like a hack. Any pointers will be appreciated! Thanks, Adam See http://lists.openembedded.org/pipermail/openembedded-core/2014-April/091380.html -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [OE-core] State of bitbake world, Failed tasks 2014-03-29
I took a look into these three (in hopes of free beer): polkit-gnome: configure was passed unrecognised options: --disable-scrollkeeper --disable-man-pages gnome-bluetooth-2.32.0: gnome-bluetooth: configure was passed unrecognised options: --disable-schemas-install openobex-1.5: openobex: configure was passed unrecognised options: --with-usb --with-bluez And it looks like all three package recipes are more or less the same as the ones in Dora. So I am confused why they haven't come up before (say, in Dora). Are we doing more strict config flag checking anywhere that I am unaware of? Also, sound-theme-freedesktop has been blocking my build for a while. I see JaMa has a local commit, but I am not sure if that's the fix for the build failure we see in the report. Can someone provide tips on that nasty undefined macro? Thank you, Adam On Sat, Mar 29, 2014 at 5:28 PM, Martin Jansa martin.ja...@gmail.comwrote: On Sat, Mar 29, 2014 at 11:54:32PM +0100, Martin Jansa wrote: On Wed, Mar 26, 2014 at 06:11:36PM +0100, Martin Jansa wrote: On Sun, Mar 23, 2014 at 09:43:24PM +0100, Martin Jansa wrote: On Tue, Mar 18, 2014 at 07:50:08PM +0100, Martin Jansa wrote: On Sat, Mar 15, 2014 at 03:10:46PM +0100, Martin Jansa wrote: On Tue, Mar 11, 2014 at 02:50:14PM +0100, Martin Jansa wrote: On Tue, Mar 11, 2014 at 02:45:04PM +0100, Martin Jansa wrote: Biggest difference from last e-mail is aclocal changes which can possibly explain increased number of do_configure failures, I've asked Richard to delay merging B!=S change until we resolve or at least analyze these new failures, so any help with would be highly appreciated. http://www.openembedded.org/wiki/Bitbake_World_Status == Failed tasks 2014-03-29 == Be aware that I plan to run test-dependencies script for next few days, so changes to meta-oe will be delayed until it's finished and I can use jenkins again to test incoming changes. If you want to do something really useful and you're not confident with big changes, please scan qa.log files in URLs in report and send some small patches to resolve unrecognized configure options (check the configure script if the option was replaced by something or if there is typo or if it is applied by some bbclass which possibly shouldn't be used e.g. gnome/gnombase). I offer beer on ELC for everybody who sends 10 changes like this :). It won't show much, because a lot of recipes are still blocked by issues listed bellow, but because release is close it's better to run it now and fix at least found issues, before the release. I also have couple of local changes which I haven't sent yet, because they aren't properly tested: f2e1f65 libgnomecanvas: add intltool dependency cc3dac2 edbus: remove test-gui option eff6aaa zram: include whole sysconfdir in PN d308e37 atftp: include whole sysconfdir in PN cdfd489 metacity: inherit only gnomebase f415c1f gtksourceview2: inherit only gnomebase 85550a0 goffice: inherit only gnomebase 22a1a79 zenity: inherit only gnomebase 29c844e gnome-themes: inherit only gnomebase 561c24c gnome-backgrounds: inherit only gnomebase 49fb47b gcr: inherit only gnomebase b470935 modemmanager: inherit only gnomebase bdc4cd9 libbonobo: inherit only gnomebase 2b13d00 libgnome-keyring: inherit only gnomebase fb2406f gnome-disk-utility: inherit only gnomebase 58a1d87 libgdata: inherit only gnomebase 6141925 libgtop: inherit only gnomebase 8c021f1 gnome-bluetooth: inherit only gnomebase 8723ea9 dconf: inherit only gnomebase e63ca45 babl: inherit only gnomebase bea1f1d gnome-menus: inherit only gnomebase a33e667 wvstreams: fix QA warning 7aa1b5e elementary: remove --disable-web 6e3a7c8 libwnck*: inherit only gnomebase 7855b14 tracker: inherit only gnomebase, fix QA warn 3251a4e gnome-control-center: include datadir/mime in PN 0ee66bb freerdp: move to nonworking de68ce6 sound-theme-freedesktop: add glib-2.0 dependenecy 5fac747 libdc1394: add libsdl dependency 4609314 mplayer2: bump SRCREV to fix build issues with newer live555 e403bec gvfs-gdu-volume-monitor: Define build dependency on libgnome-keyring If you have some patches for issues bellow and you haven't sent them because you want to test them more, please send them with [WIP] in subject and I'll include them in master-next for test-depedencies build (better to test recipe which is possibly broken in runtime than not testing it and it's dependents at all) I'll probably start it on Wed and last time it took 11 days. === common (23) === * meta-openembedded/meta-gnome/recipes-gnome/devilspie/ devilspie2_0.24.bb, do_compile * meta-openembedded/meta-gnome/recipes-gnome/libgnome/ libgnomecanvas_2.30.3.bb, do_configure * meta-openembedded/meta-multimedia/recipes-mediacentre/xbmc/ xbmc_git.bb, do_compile * meta-openembedded/meta-multimedia/recipes-multimedia/libdc1394/ libdc1394_git.bb, do_configure *
[oe] Warnings during build
Hope I am not spamming the list with pesky questions. I am getting build warnings similar to below: WARNING: gtk-immodule-ipa-2.24.22 was registered as shlib provider for im-ipa.so, changing it to gtk3-immodule-ipa-3.10.7 because it was built later The full list of warnings can be found at - http://pastebin.com/quqwCPEq. I am not sure what these warnings are. They are definitely new in 1.6. I am trying to figure out if there is something I can do, or if this will be sorted out as we get closer to the 1.6 release date. Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Warnings during build
I see! I trust bitbake to link against the right one (newer one that is). Thanks for ur response JaMa. Adam On Wed, Mar 26, 2014 at 11:28 AM, Martin Jansa martin.ja...@gmail.comwrote: On Wed, Mar 26, 2014 at 11:12:28AM -0700, Adam Lee wrote: Hope I am not spamming the list with pesky questions. I am getting build warnings similar to below: WARNING: gtk-immodule-ipa-2.24.22 was registered as shlib provider for im-ipa.so, changing it to gtk3-immodule-ipa-3.10.7 because it was built later The full list of warnings can be found at - http://pastebin.com/quqwCPEq . I am not sure what these warnings are. They are definitely new in 1.6. I am trying to figure out if there is something I can do, or if this will be sorted out as we get closer to the 1.6 release date. See http://comments.gmane.org/gmane.comp.handhelds.openembedded/62213 as long as nothing tries to link against im-ipa.so it's safe and you should just list them in PRIVATE_LIBS. The warning means that if something links with im-ipa.so then it's not known if it will get runtime dependency on gtk-immodule-ipa-2.24.22 or gtk3-immodule-ipa-3.10.7 (it will always be the one built later in the same sysroot). -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] exo build fail on master and master-next
Hi Richard, thanks for the explanation. It helped me in understanding about the commit. intltool-native builds fine. This suggests me that I have the dependencies requirement for intltool-native. Also I apt-get installed intltool on my build server just in case. However, I still get exo-native build error. Just letting you know, the recipes involved are all under the OE layer (meta-xfce). I am building for Gumstix Overo, which is not the default build target, but this error is not platform dependent. I still get the same result on qemuarm. At any rate, I now know it's a dependency issue, so that's where I will start digging and report back. Thank you, Adam On Wed, Mar 26, 2014 at 1:07 AM, Richard Purdie richard.pur...@linuxfoundation.org wrote: On Tue, 2014-03-25 at 17:46 -0700, Adam Lee wrote: exo-native (one of xfce4-taskmanager deps) was the point of failure. More specifically, exo-native was failing during configuration time. I discovered that, on master-next, exo-native build finishes by reverting this commit in autoconf.bbclass. This commit was new this year in Yocto Project 1.6. I have no idea how this commit breaks exo-native build. So I can't discern if the commit has errors. This still could very be a configuration issue in my build machine. Can anyone take a look at the commit one more time? On Mon, Mar 24, 2014 at 2:29 PM, Adam Lee adam.yh@gmail.com wrote: The error is occurring on master-next (and master I presume) when building xfce4-taskmanager (as part of XFCE4 Extended package group). I confirmed it on both qemuarm and on Gumstix Overo as build targets. This tells me it's a bug, but there still might be something unique about my setup. Can anyone verify if xfce4-taskmanager can be built successfully? On Fri, Mar 21, 2014 at 2:08 PM, Adam Lee adam.yh@gmail.com wrote: Good day everyone, On both master and master-next, I get build fail on exo like below: configure.ac:112: error: possibly undefined macro: AC_PROG_INTLTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. That commit makes the system more strict about dependencies and they're probably incorrect in your recipe. The above error suggests you're missing a dependency on intltool-native. Cheers, Richard -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] exo build fail on master and master-next
Thanks Richard, that worked! I've submitted a patch for this. Adam On Wed, Mar 26, 2014 at 2:08 PM, Richard Purdie richard.pur...@linuxfoundation.org wrote: On Wed, 2014-03-26 at 14:00 -0700, Adam Lee wrote: Hi Richard, thanks for the explanation. It helped me in understanding about the commit. intltool-native builds fine. This suggests me that I have the dependencies requirement for intltool-native. Also I apt-get installed intltool on my build server just in case. However, I still get exo-native build error. Just letting you know, the recipes involved are all under the OE layer (meta-xfce). I am building for Gumstix Overo, which is not the default build target, but this error is not platform dependent. I still get the same result on qemuarm. At any rate, I now know it's a dependency issue, so that's where I will start digging and report back. Right, to be more specific, try adding DEPENDS += intltool-native to the recipe. Cheers, Richard -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH] exo: Add intltool-native as native dependency
Cool, thanks JaMA Adam On Wed, Mar 26, 2014 at 2:35 PM, Martin Jansa martin.ja...@gmail.comwrote: On Wed, Mar 26, 2014 at 02:27:34PM -0700, Adam YH Lee wrote: exo-native fails to build due to more strict dependency checking introduced in autotools.bbclass. intltool-native should be explicitly defined as a dependency. Signed-off-by: Adam YH Lee adam.yh@gmail.com --- meta-xfce/recipes-xfce/exo/exo_0.10.2.bb |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-xfce/recipes-xfce/exo/exo_0.10.2.bbb/meta-xfce/recipes-xfce/exo/ exo_0.10.2.bb index 09aacc3..3eb03bc 100644 --- a/meta-xfce/recipes-xfce/exo/exo_0.10.2.bb +++ b/meta-xfce/recipes-xfce/exo/exo_0.10.2.bb @@ -3,8 +3,8 @@ SECTION = x11 LICENSE = GPLv2 LIC_FILES_CHKSUM = file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 DEPENDS = gtk+ libxfce4util libxfce4ui virtual/libx11 liburi-perl-native cairo -DEPENDS_class-native = glib-2.0-native xfce4-dev-tools-native -PR = r4 +DEPENDS_class-native = glib-2.0-native xfce4-dev-tools-native intltool-native +PR = r5 We don't do PR bumps anymore, I'll remove that when cherry-picking to master-next. inherit xfce pythonnative perlnative -- 1.7.9.5 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] exo build fail on master and master-next
exo-native (one of xfce4-taskmanager deps) was the point of failure. More specifically, exo-native was failing during configuration time. I discovered that, on master-next, exo-native build finishes by reverting this commit in autoconf.bbclasshttps://github.com/openembedded/oe-core/commit/79ea036de331bde65a88fb777647dc099ef05acf. This commit was new this year in Yocto Project 1.6. I have no idea how this commit breaks exo-native build. So I can't discern if the commit has errors. This still could very be a configuration issue in my build machine. Can anyone take a look at the commit one more time? Thank you, Adam On Mon, Mar 24, 2014 at 2:29 PM, Adam Lee adam.yh@gmail.com wrote: The error is occurring on master-next (and master I presume) when building xfce4-taskmanager (as part of XFCE4 Extended package group). I confirmed it on both qemuarm and on Gumstix Overo as build targets. This tells me it's a bug, but there still might be something unique about my setup. Can anyone verify if xfce4-taskmanager can be built successfully? Thank you, Adam On Fri, Mar 21, 2014 at 2:08 PM, Adam Lee adam.yh@gmail.com wrote: Good day everyone, On both master and master-next, I get build fail on exo like below: configure.ac:112: error: possibly undefined macro: AC_PROG_INTLTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /media/Build/master-next/build/tmp/sysroots/x86_64-linux/usr/bin/autoconf failed with exit status: 1 Full log is here http://paste.ubuntu.com/7132707/ Thank you for your help, Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] exo build fail on master and master-next
The error is occurring on master-next (and master I presume) when building xfce4-taskmanager (as part of XFCE4 Extended package group). I confirmed it on both qemuarm and on Gumstix Overo as build targets. This tells me it's a bug, but there still might be something unique about my setup. Can anyone verify if xfce4-taskmanager can be built successfully? Thank you, Adam On Fri, Mar 21, 2014 at 2:08 PM, Adam Lee adam.yh@gmail.com wrote: Good day everyone, On both master and master-next, I get build fail on exo like below: configure.ac:112: error: possibly undefined macro: AC_PROG_INTLTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /media/Build/master-next/build/tmp/sysroots/x86_64-linux/usr/bin/autoconf failed with exit status: 1 Full log is here http://paste.ubuntu.com/7132707/ Thank you for your help, Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] exo build fail on master and master-next
Good day everyone, On both master and master-next, I get build fail on exo like below: configure.ac:112: error: possibly undefined macro: AC_PROG_INTLTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /media/Build/master-next/build/tmp/sysroots/x86_64-linux/usr/bin/autoconf failed with exit status: 1 Full log is here http://paste.ubuntu.com/7132707/ Thank you for your help, Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] libxfce4ui build fail on master branch
Hello everyone, I am building my dora bsp layers with OE/poky master to prepare for 1.6 release. My console image built just fine, but I am getting this error while building xfce image. NOTE: Executing intltoolize --copy --force --automake NOTE: Executing ACLOCAL=aclocal --system-acdir=/media/Build/Post-Dora/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libxfce4ui/4.10.0+gitAUTOINC+530b72f50f-r0/git/aclocal-copy/ autoreconf --verbose --install --force --exclude=autopoint autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --system-acdir=/media/Build/Post-Dora/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libxfce4ui/4.10.0+gitAUTOINC+530b72f50f-r0/git/aclocal-copy/ --force aclocal: error: couldn't open directory '/media/Build/Post-Dora/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libxfce4ui/4.10.0+gitAUTOINC+530b72f50f-r0/git/aclocal-copy/': No such file or directory autoreconf: aclocal failed with exit status: 1 ERROR: autoreconf execution failed. WARNING: exit code 1 from a shell command. ERROR: Function failed: do_configure (log file is located at /media/Build/Post-Dora/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libxfce4ui/4.10.0+gitAUTOINC+530b72f50f-r0/temp/log.do_configure.2388) This https://github.com/gumstix/Gumstix-YoctoProject-Repo/blob/dev/default.xmlis my manifest just in case. Thank you for your help! Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] libxfce4ui build fail on master branch
Weird, when I bitbaked the package individually, it built ok. Now my xfce image is also happily building. On Thu, Mar 20, 2014 at 2:11 PM, Adam Lee adam.yh@gmail.com wrote: Hello everyone, I am building my dora bsp layers with OE/poky master to prepare for 1.6 release. My console image built just fine, but I am getting this error while building xfce image. NOTE: Executing intltoolize --copy --force --automake NOTE: Executing ACLOCAL=aclocal --system-acdir=/media/Build/Post-Dora/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libxfce4ui/4.10.0+gitAUTOINC+530b72f50f-r0/git/aclocal-copy/ autoreconf --verbose --install --force --exclude=autopoint autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --system-acdir=/media/Build/Post-Dora/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libxfce4ui/4.10.0+gitAUTOINC+530b72f50f-r0/git/aclocal-copy/ --force aclocal: error: couldn't open directory '/media/Build/Post-Dora/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libxfce4ui/4.10.0+gitAUTOINC+530b72f50f-r0/git/aclocal-copy/': No such file or directory autoreconf: aclocal failed with exit status: 1 ERROR: autoreconf execution failed. WARNING: exit code 1 from a shell command. ERROR: Function failed: do_configure (log file is located at /media/Build/Post-Dora/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libxfce4ui/4.10.0+gitAUTOINC+530b72f50f-r0/temp/log.do_configure.2388) This https://github.com/gumstix/Gumstix-YoctoProject-Repo/blob/dev/default.xmlis my manifest just in case. Thank you for your help! Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] libxfce4ui build fail on master branch
Found Stephen's patch last week. Thanks! Adam On Thu, Mar 20, 2014 at 3:19 PM, Martin Jansa martin.ja...@gmail.comwrote: On Thu, Mar 20, 2014 at 02:11:04PM -0700, Adam Lee wrote: Hello everyone, I am building my dora bsp layers with OE/poky master to prepare for 1.6 release. My console image built just fine, but I am getting this error while building xfce image. NOTE: Executing intltoolize --copy --force --automake NOTE: Executing ACLOCAL=aclocal --system-acdir=/media/Build/Post-Dora/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libxfce4ui/4.10.0+gitAUTOINC+530b72f50f-r0/git/aclocal-copy/ autoreconf --verbose --install --force --exclude=autopoint autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --system-acdir=/media/Build/Post-Dora/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libxfce4ui/4.10.0+gitAUTOINC+530b72f50f-r0/git/aclocal-copy/ --force aclocal: error: couldn't open directory '/media/Build/Post-Dora/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libxfce4ui/4.10.0+gitAUTOINC+530b72f50f-r0/git/aclocal-copy/': No such file or directory autoreconf: aclocal failed with exit status: 1 ERROR: autoreconf execution failed. WARNING: exit code 1 from a shell command. ERROR: Function failed: do_configure (log file is located at /media/Build/Post-Dora/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/libxfce4ui/4.10.0+gitAUTOINC+530b72f50f-r0/temp/log.do_configure.2388) This https://github.com/gumstix/Gumstix-YoctoProject-Repo/blob/dev/default.xml is my manifest just in case. Thank you for your help! See patches on ML from last week -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] GDM alternative?
Thanks Stephen for your response :) I think I will give slim a spin this weekend on my desktop. Ultimately a lighter DM will be appreciated on my embedded boards. Adam On Thu, Feb 27, 2014 at 2:29 PM, Stephen Arnold stephen.arnol...@gmail.comwrote: It's a bit more subtle than just obvious advantage since the deps are different, config options are different, etc. Slim is probably lighter than lxdm, in both features and dependency bloat. The former pretty depends only on X11 libs and png (with optional pam and dbus/consolekit integration). OTOH, lxdm has about the same pam/consolekit features, but depends on gtk[2|3]. So, a bit fancier and a little more bloat. Which one do you think is easier to theme? ;) On Wed, Feb 26, 2014 at 3:28 PM, Adam Lee a...@gumstix.com wrote: Are there any obvious advantages over one another between LXDM and Slim? I love how LXDM doesn't require complicated authentication framework like GDM. Adam On Tue, Feb 25, 2014 at 7:49 PM, Stephen Arnold stephen.arnol...@gmail.comwrote: Is there any interest in reviving slim? I'm using it on gentoo-arm on several devices; works just like x86. Since I haven't tried it or otherwise looked at it in oe yet, I have no idea why it's in a non-working state. That said, it was on my todo list until I noticed lxdm, so I'll probably check it out at some point; never a bad idea to have another lightweight alternative... Steve On Thu, Feb 20, 2014 at 1:36 PM, Adam Lee adam.yh@gmail.com wrote: Andreas, LXDM from meta-oe works well with minimal configuration on my part :) I didn't have to add another layer to satisfy dependencies. Thanks :) Adam On Wed, Feb 19, 2014 at 11:36 PM, Andreas Müller schnitzelt...@googlemail.com wrote: On Wed, Feb 19, 2014 at 5:15 PM, Adam Lee adam.yh@gmail.com wrote: Thank you Koen and Andreas. That has been really helped in clearing up my confusion and setting the path forward. I think I will try LXDM in meta-misc in meta-oe. Is there any special configuration that I should be aware of (other then setting it as the graphical init manager)? meta-misc is my personal playground - it might have dependencies to other layers and some things might not work as expected... Andreas ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] GDM alternative?
Are there any obvious advantages over one another between LXDM and Slim? I love how LXDM doesn't require complicated authentication framework like GDM. Adam On Tue, Feb 25, 2014 at 7:49 PM, Stephen Arnold stephen.arnol...@gmail.comwrote: Is there any interest in reviving slim? I'm using it on gentoo-arm on several devices; works just like x86. Since I haven't tried it or otherwise looked at it in oe yet, I have no idea why it's in a non-working state. That said, it was on my todo list until I noticed lxdm, so I'll probably check it out at some point; never a bad idea to have another lightweight alternative... Steve On Thu, Feb 20, 2014 at 1:36 PM, Adam Lee adam.yh@gmail.com wrote: Andreas, LXDM from meta-oe works well with minimal configuration on my part :) I didn't have to add another layer to satisfy dependencies. Thanks :) Adam On Wed, Feb 19, 2014 at 11:36 PM, Andreas Müller schnitzelt...@googlemail.com wrote: On Wed, Feb 19, 2014 at 5:15 PM, Adam Lee adam.yh@gmail.com wrote: Thank you Koen and Andreas. That has been really helped in clearing up my confusion and setting the path forward. I think I will try LXDM in meta-misc in meta-oe. Is there any special configuration that I should be aware of (other then setting it as the graphical init manager)? meta-misc is my personal playground - it might have dependencies to other layers and some things might not work as expected... Andreas ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] NetworkManger's glib schemas are not getting compiled
Thanks Ross, but adding gsettings to network-manager-applet's recipe didn't work. I don't know how gsettings work, so I think I will take a look at it first. Will update soon. Thanks, Adam On Tue, Feb 25, 2014 at 3:35 PM, Burton, Ross ross.bur...@intel.com wrote: On 25 February 2014 23:08, Adam Lee adam.yh@gmail.com wrote: Hello everyone, I'm on 1.5.1 at the moment. My image includes XFCE and Gnome's Network Manager. The network manager applet cannot be accessed because the schema associated with it is not compiled. Try adding gsettings to the inherits list, that should handle the schema compilation. Ross ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] NetworkManger's glib schemas are not getting compiled
Hello everyone, I'm on 1.5.1 at the moment. My image includes XFCE and Gnome's Network Manager. The network manager applet cannot be accessed because the schema associated with it is not compiled. Error I get: (nm-applet: 891): settings schema 'org.gnome.nm-applet' is not installed It works as long as I run this: $ glib-compile-schemas /usr/share/glib-2.0/schemas However this should be part of post installation process. I am not sure what I am missing. Any guidance will be appreciated! Adam ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] GDM alternative?
Andreas, LXDM from meta-oe works well with minimal configuration on my part :) I didn't have to add another layer to satisfy dependencies. Thanks :) Adam On Wed, Feb 19, 2014 at 11:36 PM, Andreas Müller schnitzelt...@googlemail.com wrote: On Wed, Feb 19, 2014 at 5:15 PM, Adam Lee adam.yh@gmail.com wrote: Thank you Koen and Andreas. That has been really helped in clearing up my confusion and setting the path forward. I think I will try LXDM in meta-misc in meta-oe. Is there any special configuration that I should be aware of (other then setting it as the graphical init manager)? meta-misc is my personal playground - it might have dependencies to other layers and some things might not work as expected... Andreas ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] GDM alternative?
Thank you Koen and Andreas. That has been really helped in clearing up my confusion and setting the path forward. I think I will try LXDM in meta-misc in meta-oe. Is there any special configuration that I should be aware of (other then setting it as the graphical init manager)? Regards, Adam On Wed, Feb 19, 2014 at 2:18 AM, Andreas Müller schnitzelt...@googlemail.com wrote: On Tue, Feb 18, 2014 at 10:24 PM, Adam Lee adam.yh@gmail.com wrote: Hello everyone, I am sure this has been asked before but I haven't found a solution. I am currently integrating GDM to my XFCE image. I was hoping that it's as easy as adding GDM as the graphical init manager (in local.conf), but it looks like PolicyKit, Console Kit, PAM, gconf, gconf-sanity (as per meta-angstrom) all need to be correctly configured for GDM to work. This integration of multiple frameworks is not what I had in mind. So I am now searching for alternative - something more lightweight and with less dependency. meta-oe contains another login manager 'slim', except it's no longer maintained and has been moved to nonworking directory within the tree. I don't see any other. Thank you, Adam I am using lxdm for my XFCE-image. Andreas ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] pam_gnome_keyring.so not getting packaged into my rootfs
Great, it worked :)
Thanks Koen,
Adam
On Mon, Feb 17, 2014 at 11:47 PM, Koen Kooi k...@dominion.thruhere.netwrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam Lee schreef op 18-02-14 00:00:
Hello everyone, my gdm logs in /var/log/gdm is complaining about these
missing files:
- polkit-gnome-authentication-agent-1 - ck-get-x11-display-device -
pam_gnome_keyring.so
The first two files are found in paths GDM wasn't aware of, so all I had
to do was create symbolic links to
/usr/lib/gdm/{polkit-gnome-authentication-agent-1,
ck-get-x11-display-device}.
The last file, pam_gnome_keyring.so, is not in my rootfs. The file gets
generated and it's in my build directory however. I can create a
bbappend to install this shared object into the rootfs, but I wanted to
ask in the list to see if I missed something obvious.
Give http://patches.openembedded.org/patch/66793/ a try
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFTAw/5MkyGM64RGpERAkDGAKCyFB1qqElkH2gRAtSL/578jYFa5gCgl7hE
Z9hpU5nZuPs+VJcYxDpVKNU=
=2Bsi
-END PGP SIGNATURE-
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] GDM alternative?
Hello everyone, I am sure this has been asked before but I haven't found a solution. I am currently integrating GDM to my XFCE image. I was hoping that it's as easy as adding GDM as the graphical init manager (in local.conf), but it looks like PolicyKit, Console Kit, PAM, gconf, gconf-sanity (as per meta-angstrom) all need to be correctly configured for GDM to work. This integration of multiple frameworks is not what I had in mind. So I am now searching for alternative - something more lightweight and with less dependency. meta-oe contains another login manager 'slim', except it's no longer maintained and has been moved to nonworking directory within the tree. I don't see any other. Thank you, Adam ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] pam_gnome_keyring.so not getting packaged into my rootfs
Just learned ConsoleKit is no longer maintained and is replaced by
Systemd's Logind (http://www.freedesktop.org/wiki/Software/ConsoleKit/).
Judging by the fact that GDM still relies on ck (ck-get-x11-display-device
handle), I am inclined to say OE's gdm recipe is not up to date.
However I am not too familiar with the scene and I may have missed details.
Any clarification on this?
Adam
On Mon, Feb 17, 2014 at 3:00 PM, Adam Lee adam.yh@gmail.com wrote:
Hello everyone, my gdm logs in /var/log/gdm is complaining about these
missing files:
- polkit-gnome-authentication-agent-1
- ck-get-x11-display-device
- pam_gnome_keyring.so
The first two files are found in paths GDM wasn't aware of, so all I had
to do was create symbolic links to
/usr/lib/gdm/{polkit-gnome-authentication-agent-1,
ck-get-x11-display-device}.
The last file, pam_gnome_keyring.so, is not in my rootfs. The file gets
generated and it's in my build directory however. I can create a bbappend
to install this shared object into the rootfs, but I wanted to ask in the
list to see if I missed something obvious.
Thank you for your help!
Adam
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] dbus-daemon-proxy repository has disappeared
Good day y'all, I am tracking refs/heads/dora and this morning I got a fetch failure on dbus-daemon-proxy (git:// git.collabora.co.uk/git/user/alban/dbus-daemon-proxy). No available mirrors, so I am build blocked. Anyone figured this out? Thanks! Adam ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] dbus-daemon-proxy repository has disappeared
Cool thank you Ross! Regards, Adam On Fri, Feb 7, 2014 at 12:00 PM, Burton, Ross ross.bur...@intel.com wrote: Just contacted Collabora. They were having a spring clean, the repo will hopefully re-appear shortly. Ross On 7 February 2014 19:51, Burton, Ross ross.bur...@intel.com wrote: On 7 February 2014 18:59, Adam Lee adam.yh@gmail.com wrote: I am tracking refs/heads/dora and this morning I got a fetch failure on dbus-daemon-proxy (git:// git.collabora.co.uk/git/user/alban/dbus-daemon-proxy). No available mirrors, so I am build blocked. Have you tried emailing Alban at Collabora? Ross ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] libmpd-11.8.17 gets 404 Not Found
There is a pull request on this - https://github.com/openembedded/meta-oe/pull/15 On Thu, Nov 14, 2013 at 1:48 PM, Andreas Müller schnitzelt...@googlemail.com wrote: On Thu, Nov 14, 2013 at 8:41 PM, Adam Lee adam.yh@gmail.com wrote: Thanks Otavio. Quick question - is there a reason not to use the upstream? - http://www.musicpd.org/download/mpd/stable/ Thanks, Adam patches welcome - but please check for xfce4-mpc-plugin and xfmpc are still building with mpc. Andreas ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] libmpd-11.8.17 gets 404 Not Found
What should be my course of action? Add the new provider to the OE mirror, or patch the entire recipe? I can do either, but just not sure what the right thing to do. Trying not to pollute. Thanks. On Thursday, November 14, 2013, Andreas Müller wrote: On Thu, Nov 14, 2013 at 12:57 PM, Paul Eggleton paul.eggle...@linux.intel.com javascript:; wrote: On Tuesday 12 November 2013 19:14:22 Adam Lee wrote: Sorry, I shouldn't have mentioned anything about updating to Dora from Dylan. This 404 is happening in Dylan build. On Tue, Nov 12, 2013 at 7:07 PM, Adam Lee adam.yh@gmail.comjavascript:; wrote: Hello everyone, my first post here. Not sure if I am posting at the right place. I am updating my meta layer to Dora from Dylan. At the moment, libmpd-11.8.17 is getting 404 Not Found. It is here - http://downloads.sourceforge.net/musicpd/libmpd/11.8.17/libmpd-11.8.17.tar .gz . Not sure if it's a temporary issue. Anyone else ran into this? Looks like it's vanished upstream... :/ I'm not familiar with this particular project and I can't tell what's going on with this particular component, but I did find an alternative download location: http://download.sarine.nl/Programs/gmpc/11.8/libmpd-11.8.17.tar.gz Until we figure out what's happened upstream we can add this to the OE source mirror. Tom, could you please take care of that? Cheers, Paul I included (lib)mpd and am using it from time to time with XFCE environment. Somehow libmpd turned obsolete and libmpd's homepage is linked to mpd. Since I don't have time for it at the moment: Could somebody please fix download location? As soon as I have some spare cycles I will take care how to fix properly. Andreas ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org javascript:; http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] libmpd-11.8.17 gets 404 Not Found
Thanks Otavio. Quick question - is there a reason not to use the upstream? - http://www.musicpd.org/download/mpd/stable/ Thanks, Adam On Thu, Nov 14, 2013 at 9:57 AM, Otavio Salvador ota...@ossystems.com.brwrote: On Thu, Nov 14, 2013 at 3:16 PM, Adam Lee adam.yh@gmail.com wrote: What should be my course of action? Add the new provider to the OE mirror, or patch the entire recipe? I can do either, but just not sure what the right thing to do. Trying not to pollute. Thanks. I'd say both. People may be using an old snapshot of OE-Core/Poky and have the download problem so adding it to the mirror is good. Updating this is also good so we can check the new path/version/URL for new versions easily. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] libmpd-11.8.17 gets 404 Not Found
Hello everyone, my first post here. Not sure if I am posting at the right place. I am updating my meta layer to Dora from Dylan. At the moment, libmpd-11.8.17 is getting 404 Not Found. It is here - http://downloads.sourceforge.net/musicpd/libmpd/11.8.17/libmpd-11.8.17.tar.gz . Not sure if it's a temporary issue. Anyone else ran into this? Adam ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] libmpd-11.8.17 gets 404 Not Found
Sorry, I shouldn't have mentioned anything about updating to Dora from Dylan. This 404 is happening in Dylan build. On Tue, Nov 12, 2013 at 7:07 PM, Adam Lee adam.yh@gmail.com wrote: Hello everyone, my first post here. Not sure if I am posting at the right place. I am updating my meta layer to Dora from Dylan. At the moment, libmpd-11.8.17 is getting 404 Not Found. It is here - http://downloads.sourceforge.net/musicpd/libmpd/11.8.17/libmpd-11.8.17.tar.gz . Not sure if it's a temporary issue. Anyone else ran into this? Adam ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] ImageMagick recipe oudated - fetch failure
Hi there, I am getting no such file error when building Image Magick. The recipe points to ftp://ftp.nluug.nl/pub/ImageMagick/ImageMagick-6.7.5-6.tar.bz2, but it looks like the ftp server has updated file (ImageMagick-6.8.2-1.tar.bz2) instead. Please update the recipe :) Regards, Adam ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
