**** BEGIN LOGGING AT Sun Aug 24 02:59:59 2014 Aug 24 06:02:28 hi, how can add & install new packages in a built image? is it possible or not? (I do't want to build new image.) Aug 24 06:17:31 sm_: you should be able to provided your image includes some online package manager like opkg or rpm Aug 24 06:23:57 khem: thanks. I didn't work with opkg or rpm before... Is there any guideline or tutorial teaching these package manager? Aug 24 08:57:18 JaMa: gah. Its part of the previous commit, just had issues applying it :/ Aug 24 08:59:19 RP, JaMa, is this about the "fixup" commit ? Aug 24 08:59:57 kroon: yes Aug 24 09:00:08 ok Aug 24 12:38:31 Hi! Aug 24 12:38:44 I'm getting an error message when I run bitbake with SPDX. Aug 24 12:38:59 Here's my command; bitbake -c spdx foo Aug 24 12:39:03 and here's the error; Aug 24 12:40:34 ERROR: Task do_spdx does not exist for target Aug 24 12:40:47 Google gives me only three hits when I google for it. Aug 24 16:32:10 have people see my patch to add newer Debian releases as tested distros? Aug 24 16:33:30 I've seen something like that Aug 24 21:23:32 hi keh Aug 24 21:23:36 argh Aug 24 21:23:41 hi khem Aug 24 21:24:00 hi ant__ Aug 24 21:24:23 khem, the v4bx strikes again, klibc armv4 binaries are broken Aug 24 21:24:47 http://pastebin.com/eXR2Cbt1 Aug 24 21:24:49 hmm Aug 24 21:25:39 what options are used to compile kexecboot Aug 24 21:25:47 and ld options Aug 24 21:25:50 klibc carries the patch since v2.02 Aug 24 21:27:20 http://pastebin.com/eXR2Cbt1 Aug 24 21:27:29 sry Aug 24 21:27:31 arm-oe-linux-gnueabi-klcc -march=armv4 -mthumb-interwork -Wall -o kexecboot util.o cfgparser.o devicescan.o evdevs.o fb.o gui.o menu.o xpm.o rgb.o tui.o kexecboot.o fstype/fstype.o machine/zaurus.o Aug 24 21:28:01 it lacks the part in the 'if CONFIG_EABI ' Aug 24 21:28:42 ifeq ($(CONFIG_AEABI),y) Aug 24 21:28:42 KLIBCREQFLAGS += -mabi=aapcs-linux -mno-thumb-interwork Aug 24 21:28:42 +KLIBCLDFLAGS += $(FIX_ARMV4_EABI_BX) Aug 24 21:30:02 the fun is, the previous applied patch does Aug 24 21:30:04 -# CONFIG_AEABI is not set Aug 24 21:30:04 +CONFIG_AEABI=y Aug 24 21:31:08 (you fixed that long ago :) Aug 24 21:35:28 somehow '--fix-v4bx' is not passed Aug 24 21:36:48 and instead we get '-mthumb-interwork' Aug 24 21:39:47 I dont's see any particular change in klibc so I suspect gcc or gold Aug 24 21:39:57 or binutils? Aug 24 21:58:42 wrt klcc, looking at the produced klibc.config I see indeed LDFLAGS= --fix-v4bx Aug 24 22:01:30 and that goes in *arm-oe-linux-gnueabi-klcc Aug 25 02:33:40 I am working on my first autotools based recipe Aug 25 02:34:13 why does yocto try to run the binary that is compile with a -c during the install phase? Aug 25 02:36:44 it isn't "yocto" doing that, it's the buildsystem of the project you're building Aug 25 02:37:26 http://pastebin.com/jsy0RCkS Aug 25 02:39:31 yes Aug 25 02:39:45 it's quite common for projects to build tools that are then run later on as part of the build process Aug 25 02:40:22 this is one case of that. there are multuiple options, but the easiest is to figure out how to get that binary built with BUILD_CC/BUILD_CFLAGS/BUILD_LDFLAGS instead of CC/CFLAGS/LDFLAGS, so it's built for the host you're running on rather than the target Aug 25 02:40:38 you should be able to grep around for recipes which reference BUILD_CC to see examples Aug 25 02:40:59 but it's tough to say why it's running it without reading hte makefiles Aug 25 02:41:03 ok Aug 25 02:41:09 here is my recipe that I created Aug 25 02:41:10 http://pastebin.com/H3M55jMu Aug 25 02:41:12 i'd recommend doing that ifrst and foremost to see why moon-buggy runs itself at install time Aug 25 02:41:55 seems questionable, maybe you can patch that behavior out of its makefile entirely Aug 25 02:43:35 I am looking at the make file and yes it's as you said. Trys to run itself while installing. I will patch it. Thanks for the help! Aug 25 02:48:10 np **** ENDING LOGGING AT Mon Aug 25 02:59:58 2014