[yocto] telnetd is not running with "core-image-basic"

2013-10-25 Thread Amit Kumar
Hi, I tried to run the telnetd with "core-image-basic". I follow up the following step to enable the telnetd support in my layer. I have build the latest inetutils recipe with my layer, the latest version of inteutils is "intetutils_1.9.1". I have build the packages successful. But the telne

Re: [yocto] Custom defconfig is not used

2013-10-25 Thread Mike Lewis
Bruce: yep, fixed my issue. Sorry for the bother! Diego: thanks for the solution! - Mike On 10/25/2013 11:44 AM, Bruce Ashfield wrote: On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro wrote: Bruce, Regarding the defconfig not used, I've found this thread on Angstrom devel ML: http://www.mail-a

[yocto] 3.10 Kernel module loading

2013-10-25 Thread Michael Gloff
I am having an issue getting a custom touchscreen kernel driver to load. It's a pixcir touchscreen and I've modified the driver found below to work with this particular display: http://lii-enac.fr/cgi-bin/gitweb.cgi?p=linux-input/drivers.git;a=shortlog;h=refs/heads/pixcir The driver works perfect

Re: [yocto] [PATCH] perf: mips64: Convert __u64 to unsigned long long

2013-10-25 Thread Yang Shi
On 10/25/2013 1:14 PM, Billie Alsup wrote: I guess for that example, you have to add % yourself "%s/event-%d-%" PRIu64 "-%d" but for all the WRITE_ASS examples, simply replace "llu" with PRIu64 Thanks for the suggestion. I had a try, but it failed to build for x86_64. | tests/attr.c:74:4: er

Re: [yocto] [PATCH] perf: mips64: Convert __u64 to unsigned long long

2013-10-25 Thread Billie Alsup
I guess for that example, you have to add % yourself "%s/event-%d-%" PRIu64 "-%d" but for all the WRITE_ASS examples, simply replace "llu" with PRIu64 On 10/25/13 1:11 PM, "Billie Alsup" wrote: >Wouldn't it be better to change "%llu" to PRIu64 (from inttypes.h)? >Notice that PRIu32 is already

Re: [yocto] [PATCH] perf: mips64: Convert __u64 to unsigned long long

2013-10-25 Thread Billie Alsup
Wouldn't it be better to change "%llu" to PRIu64 (from inttypes.h)? Notice that PRIu32 is already used in places. You can use string catenation where necessary, e.g. "%s/event-%d-" PRIu64 "-%d" On 10/25/13 12:17 PM, "Yang Shi" wrote: >On MIPS64, "__u64" is "unsigned long" type, so the "%llu" s

[yocto] [PATCH] perf: mips64: Convert __u64 to unsigned long long

2013-10-25 Thread Yang Shi
On MIPS64, "__u64" is "unsigned long" type, so the "%llu" specifier will cause build error on MIPS64. Convert __u64 to unsigned long long in those sprintf calls to avoid the build error. Signed-off-by: Yang Shi --- tools/perf/tests/attr.c | 20 ++-- tools/perf/te

Re: [yocto] Custom defconfig is not used

2013-10-25 Thread Bruce Ashfield
On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro wrote: > Bruce, > > Regarding the defconfig not used, I've found this thread on Angstrom devel > ML: > http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html > > I've replaced "FILESEXTRAPATHS_prepend" with "FILESPATH_prepend" an

Re: [yocto] problems with yocto eclipse ADT and beaglebone

2013-10-25 Thread Larry Weaver
I have managed to answer one of my questions. The tcf-agent from the beagleboard build is apparently not complete. I set up a toolchain on the beaglebone and compiled the tcf-agent from the git. The previous tcf-agent didn’t have terminal or shell capability. The new one does. . So now i

Re: [yocto] BAD_RECOMMENDATIONS / BAD_RECOMMENDS not working

2013-10-25 Thread Diego Sueiro
2013/10/25 Martin Jansa > BAD_RECOMMENDATIONS work only for packages which are installed because > something has them in RRECOMMENDS, if your custom image has qt-demo-init in > IMAGE_INSTALL or pulled by RDEPENDS in some variable, than it won't be > removed (and shouldn't be). > Thanks Martin,

Re: [yocto] problems with yocto eclipse ADT and beaglebone

2013-10-25 Thread Larry Weaver
The system is the kepler release with the Yocto kepler 1.5 plugin (the Yocto manual says to use 1.6, but that doesn’t seem to exist). I’m setting things up totally from the manual and it says to use the tcf-agent with the Yocto plugin for eclipse kepler (also has some juno information, but say

Re: [yocto] BAD_RECOMMENDATIONS / BAD_RECOMMENDS not working

2013-10-25 Thread Martin Jansa
BAD_RECOMMENDATIONS work only for packages which are installed because something has them in RRECOMMENDS, if your custom image has qt-demo-init in IMAGE_INSTALL or pulled by RDEPENDS in some variable, than it won't be removed (and shouldn't be). Use bitbake -g to see why and how it's pulled to you

[yocto] BAD_RECOMMENDATIONS / BAD_RECOMMENDS not working

2013-10-25 Thread Diego Sueiro
Folks, I'm using dylan branch and package management is ipk. I'm trying to remove qt-demo-init package from my custom image with both BAD_RECOMMENDATIONS and BAD_RECOMMENDS variables but it is still being installed on rootfs. I've already did a cleansstate on my image recipe but no success. I c

[yocto] yocto-dora problems building python

2013-10-25 Thread João Henrique Freitas
Hello, I got this QA error when build python: ERROR: QA Issue: python: The compile log indicates that host include and/or library paths were used. Any hint? Build Configuration: BB_VERSION= "1.20.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-13.04" TARGET_SYS

Re: [yocto] Remote debugging with Yocto

2013-10-25 Thread Houkes, Bart
Hi Yocto, Thanks for all the support. I'm just working 2 weeks on Yocto and still no expert. Adding extra features is working great when I want to do remote-debug: EXTRA_IMAGE_FEATURES = "debug-tweaks tools-debug eclipse-debug" Next problem I have is related to the 5150 evaluation board from TI.

Re: [yocto] Custom defconfig is not used

2013-10-25 Thread Diego Sueiro
Bruce, Regarding the defconfig not used, I've found this thread on Angstrom devel ML: http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html I've replaced "FILESEXTRAPATHS_prepend" with "FILESPATH_prepend" and removed the custom "do_configure_prepend" function and bitbake i

[yocto] Problem with staging dir in Makefile.am

2013-10-25 Thread Hans Beckérus
Hi. I have a package that tries to point to a staged/installed source file (shared) in the list of files to be compiled. But how should the Makefile.am properly pick-up the current staging dir for my target? Currently it is simply using /usr/share/foo/foo.c, but obviously that will not work when cr