**** BEGIN LOGGING AT Wed May 16 03:00:01 2012 May 16 05:18:02 hello all May 16 05:19:00 while configuring "xerces-c-src_2_8_0" I m getting this error in oe .... getopt: unrecognized option '--sysroot=/mnt/sda3/OPENEMBEDDED/build/tmp/sysroots/armv4t-angstrom-linux-gnueabi' May 16 07:25:46 good morning May 16 07:49:51 good morning mckoan, all May 16 08:29:25 Hi everyone May 16 08:37:50 I was wondering, where to get the MACHINE and distro parameters when building a custom os ? May 16 08:54:37 mohtadi: local.conf May 16 09:04:24 mckoan: i've left the May 16 09:04:45 local.conf as it is changing only three parameters ( just to test for now) May 16 09:05:52 and compiling the helloworld gives me this http://pastebin.com/FS8H8dxk May 16 09:42:17 mckoan: what's the best way to begin with OpenEmbedded, i've been into ptxdist for a while, and it's completly different! May 16 09:42:42 i've followed the official wiki, but , i'm getting problems :D May 16 09:49:12 mohtadi: I also used in Ptxdist for years, then I quit and joined OE May 16 09:49:56 mohtadi: I usually suggest to use my distro KaeilOS http://www.kaeilos.com/download May 16 09:50:27 mohtadi: but you can follow OE documents of course: http://www.openembedded.org/wiki/Getting_started May 16 09:50:42 http://www.openembedded.org/wiki/Documentation May 16 09:51:35 mckoan: for KaeilOS , is compatible with a i586 target? May 16 09:52:27 AFAIK OE (and derivative) does not support well x86 targets May 16 09:53:04 BTW I tested it with 486/586 and a console-image (no graphics) and worked May 16 09:53:30 if you need graphics with x86 OE is the bad choice May 16 09:53:47 nobody supports it and cares about it May 16 09:54:27 :s May 16 09:54:50 mckoan: well... May 16 09:55:08 mckoan: depends... Intel does provide BSPs for some of our newer embedded platforms May 16 09:55:09 i'm scrwed then! May 16 09:55:39 bluelightning: are you talking about oe-core + yocto ? May 16 09:55:57 mckoan: yep, which is where new developers ought to be starting really May 16 09:56:29 mckoan: is there a way to start building and extending a customized system? not based on any distro???? May 16 09:56:46 bluelightning: unfortunately with yocto I see only console based stuff, no graphics May 16 09:56:56 here is my embedded target : http://www.diamondsystems.com/products/poseidon May 16 09:57:58 mckoan: we definitely have graphic drivers in the BSPs; OE-core contains X and a number of graphics-related libs May 16 09:58:00 mohtadi: again, if you need only console mode you can use what I said or the newer yocto http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html May 16 09:58:31 bluelightning: reading in yocto website it isn't so clear May 16 09:58:58 mckoan: I don't think we say anywhere that it's console-only do we? May 16 09:59:19 if that's the impression we're conveying maybe we need to change a few things on there May 16 09:59:51 bluelightning: http://www.yoctoproject.org/documentation/hardware-support for example is scaring May 16 10:00:13 what you should argue from this page? May 16 10:00:48 to me is to find another project :-) May 16 10:01:21 mckoan: the only thing missing from that page is a statement that other BSPs are available (as they are now) May 16 10:02:01 mckoan: the core project still supports the devices listed as hardware reference platforms May 16 10:02:41 unlike OE-classic we don't fold in all the BSPs into the core metadata; they are maintained separately May 16 10:03:42 bluelightning: a simple howto to build an Atom based system with fb0+xorg+WM would boost yocto though ;-) May 16 10:04:22 bluelightning: IMHO yocto is too fragmented and unclear to understand May 16 10:05:27 mckoan: fragmented in what way? May 16 10:07:01 mohtadi: I'm guessing it wouldn't be too hard to put together a very simple BSP for this device if you have the drivers already May 16 10:07:11 bluelightning: is not clear what to do to tie all the pieces (oe-core, metadata, and so on) May 16 10:07:17 mohtadi: in an ideal world the manufacturer would provide the BSP May 16 10:08:16 bluelightning: in the real world the manufacturer wants the BSP for free from the community, LOL May 16 10:08:52 mckoan: right, but the manufacturer holds all the cards; ultimately it's not that difficult to produce a BSP and it benefits them May 16 10:09:18 mckoan: from the OE side sure, the documentation is severely lacking May 16 10:09:34 mckoan: despite many complaints nobody seems to be able to find time to write better docs May 16 10:09:46 within the Yocto project we have quite good docs though May 16 10:17:45 bluelightning: Digita il testo o l'indirizzo di un sito web oppure traduci un documento. May 16 10:17:48 Annulla May 16 10:17:50 italiano May 16 10:17:53 tedesco May 16 10:17:55 inglese May 16 10:17:58 Alpha May 16 10:18:00 The perception from outside is that it has Yocto is a project run by large corporations and Linux Foudadtion therefore expected that they provide for the solution. May 16 10:18:03 With the old e-classic was a greater sense of community. May 16 10:18:07 These impressions were communicated to me by several people who attended the recent presentation to ELC / ELCE May 16 10:18:40 (sorry for the clumsy paste) May 16 10:40:35 mckoan: I think this is all about perception; reality is that from that standpoint I don't think much has changed May 16 10:40:51 mckoan: even in the old days a lot of work was done by people paid by companies May 16 10:53:42 mckoan: there are significant contributions from outside the Yocto Project to OE-Core, it's not just us working on it... so I'm not sure what more could be done to strengthen the community May 16 10:53:53 mckoan: we're more than happy to have suggestions though May 16 11:18:09 mckoan: not only large corporations ... (here we are ... 4 ;-) May 16 11:18:23 hi btw May 16 11:22:31 hi ericben May 16 11:28:23 hi bluelightning May 16 15:41:51 is someone working with mali opensource driver? May 16 15:58:33 hi. I would like to make a micro image rootfs manually, using ipks packages I can download from http://www.angstrom-distribution.org/feeds/core/ipk/eglibc/mips/base/ May 16 15:59:25 no sure if that is possible. I mean, I would like to download busybox, udev, sysvinit, etc ipk packages. And then May 16 15:59:35 to make manually a micro image to test in a little board May 16 15:59:41 Is that possible? May 16 16:01:08 I would like to try that at the same time I am trying to build the micro-image using OE directly of course. But because the building process is slow with my machine (and I have to fix from time to time SRC_URI or stuff like that) May 16 16:01:24 I would like to try to make a micro image using ipk packages already available. May 16 16:01:58 Jay7: do you think that I am clear? :) ( May 16 16:02:36 I am building a cloud9-gnome-image for beagleboard using oe. How can I choose between glibc and eglibc? May 16 16:27:09 sp00k: if this is with current Angstrom, you cannot; OE-core only supports eglibc (and uclibc) May 16 16:28:47 there is no reason to choose between "glibc" and "eglibc".. they are both binary compatible, unless you change the configuration of eglibc May 16 16:29:15 ok, that makes it easier if there is no choice ;) May 16 16:35:34 is someone working with mali opensource driver? May 16 16:35:45 soon we will switch back to glibc :) May 16 16:35:52 if you are not confused enought May 16 16:36:12 may be 2.17 time frame May 16 16:38:12 ah? really? May 16 16:38:18 why move back to glibc? May 16 16:39:32 otavio: due to change in glibc community practices its more open now May 16 16:39:48 hence lot of (almost all) eglibc changes will be merged into glibc May 16 16:39:51 eventually May 16 16:39:55 khem: so development is merging back effectively? May 16 16:40:00 yes May 16 16:40:03 but afaik, glibc is less embedded friendly, regarding configurability May 16 16:40:05 well, that's good :) May 16 16:40:25 (about merging back) May 16 16:40:28 otavio: it use to be since maintainership changed that perception has changed May 16 16:40:31 or should be changed now May 16 16:40:40 presumably that configurability will be made available in glibc as well May 16 16:40:45 good May 16 16:40:45 yes May 16 16:40:55 infact glibc will use kconfig May 16 16:41:01 nice! May 16 16:41:05 a step further than what we have May 16 16:41:08 in eglibc May 16 16:41:25 I already have patches accumulated but they need to be polished May 16 16:41:29 they dont work yet May 16 16:42:14 eglibc kind of forced the change in glibc structure May 16 16:42:24 khem: btw pls remember the poor orphan needing much care, klibc ;) May 16 16:42:36 ant_work: heh yes May 16 16:42:44 lol May 16 16:42:44 hpa is back and release 2.0 is imminent May 16 16:42:45 I looked at ur patches infact May 16 16:42:50 and they looked ok to me May 16 16:42:54 pheww May 16 16:43:11 but I did not test them myself May 16 16:45:07 I suspect there is some overpatching, which I just refreshed May 16 16:45:32 and the 'new' features we add with oe-patches are actually unused by curren images May 16 16:45:53 (wc, modprobe, ..) May 16 16:46:38 khem: I tried to compile kmod against klibc and well, ..first try was not encouraging May 16 16:46:51 lol May 16 16:46:52 ant_work: hmm May 16 16:47:02 I've seen I had to add the mtd headers, maybe we need more May 16 16:47:32 yes it uses lot of new syscalls May 16 16:47:34 otavio: too many warnings to be true, and finally on error May 16 16:47:52 ah May 16 17:25:52 zrafa: seems no because nobody answers :) May 16 18:05:09 Jay7: yes you can populate an image from ipk May 16 18:05:18 using ar to extract stuff from it May 16 18:05:40 khem: there may be some scripts iirc May 16 18:06:04 imho, in zrafa's case sstate should fit better May 16 18:06:26 then he may just run bitbake some-image May 16 18:06:55 but I'm unsure is antsgrom's sstate published or not May 16 18:12:41 khem: what about busybox? May 16 18:13:25 khem: if I extract busybox ipk package I get busybox binary.. but the symbolic links are not there May 16 18:13:39 khem: have you tried?.. Could you give me some tips? May 16 18:13:52 I thought you were absolutely clear on what your image should consist of ? May 16 18:14:02 since you want to do it manually May 16 18:14:12 and not use image generation through OE May 16 18:14:21 khem: well, I do not know how to get an image. I know how to extract files from ipk May 16 18:14:27 khem: but I am not sure if that is enough May 16 18:14:32 angstrom sstate is published yes May 16 18:14:44 khem: and I do not know if there is some howto or tutorial to know which packages to use May 16 18:14:51 but it could mean downloading gigagbytes of data at first May 16 18:14:53 khem: (for a micro or minimal image) May 16 18:15:15 zrafa: I dont think so. May 16 18:15:29 I have booted systems with just kernel+uclibc+busybox May 16 18:16:01 or kernel+eglibc+busybox May 16 18:17:57 khem: I do not know which packages to use to get the same May 16 18:19:15 Jay7: what is angtrom sstate? May 16 18:19:27 khem: ^ May 16 18:20:21 zrafa: sstate is kind of cache May 16 18:21:04 i.e. some directories with packages May 16 18:21:20 oe-core can use it to re-create building environment May 16 18:21:34 w/o recompiling every package May 16 18:29:23 ah May 16 18:29:26 sounds interesting May 16 18:29:35 do you know where to get more info? May 16 18:38:17 zrafa: ask some angstrom developer :) May 16 18:38:23 may be in angsrom-devel ML May 16 18:38:47 or check angstrom building scripts May 16 19:12:46 khem, hi May 16 20:18:19 GNUtoo-desktop: hi May 16 20:18:30 GNUtoo-desktop: so the gold patch did not really help May 16 20:19:02 I can't tell May 16 20:19:11 it created another problem before May 16 20:19:24 like it segfault during startup May 16 20:19:29 no --help May 16 20:19:30 etc... May 16 20:19:43 so no way to see if it fixed the illegal instruction that is *after* May 16 20:19:49 s/is/comes/ May 16 20:20:26 that segfault I see is in libc May 16 20:20:34 are you able to run it in gdb May 16 20:20:37 and see the stack trace May 16 20:23:06 I dd yesterday May 16 20:23:08 let me retry May 16 20:32:57 khem, http://www.pastie.org/private/7rk2ifqhg7zls2nvlfrteg May 16 20:37:19 GNUtoo: ok that seems to be early enough May 16 20:37:40 GNUtoo: can you set breakpoint at strtok and rerun May 16 20:37:48 and show stack when it stop May 16 20:57:55 ok I will do it later May 16 21:17:32 khem, ok will do it now May 16 21:19:50 khem, http://www.pastie.org/private/pmo2rloe0ak1aia9qifgyq is that ok? May 16 22:14:18 does someone has a clue about /usr/local/oecore-i686/sysroots/armv7a-vfp-neon-oe-linux-gnueabi/usr/lib/arm-oe-linux-gnueabi/4.6.4/libgcc.a(bpabi.o):(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr1' May 16 22:14:23 ? May 16 22:29:51 otavio, it's uboot? May 16 22:33:15 GNUtoo-desktop: yep May 16 22:35:20 what if you define it? May 16 22:35:56 how? May 16 22:40:23 I don't remember the exact semantics but try adding the function in uboot May 16 22:43:49 otavio, do you have the full log? May 16 22:46:04 I can have May 16 22:46:11 hold May 16 22:46:26 for instance I suspect that it's because it divides by zero May 16 22:46:29 but uboot has: May 16 22:46:36 arch/arm/lib/div0.c May 16 22:46:49 GNUtoo-desktop: it is amlogic hacked uboot code May 16 22:46:55 so it might be their fault May 16 22:47:32 probably yes May 16 22:47:37 but you have to fix it anyway May 16 22:48:15 a -j1 log is easier for you, right? May 16 22:48:49 whatever I need the last part May 16 22:50:59 GNUtoo-desktop: http://paste.debian.net/169179/ May 16 22:52:44 basically I already saw this error May 16 22:52:47 and I solved it May 16 22:52:51 but I don't remember where May 16 22:52:54 maybe in nuttx May 16 22:54:22 heheh May 16 22:55:52 hi May 16 22:56:05 hi May 16 22:56:20 zrafa, are you the one doing the nanonote layer? May 16 22:56:35 hi, I get this : Unable to fetch URL svn://svn.o-hand.com/repos/misc/trunk;module=psplash;proto=http from any source. May 16 22:56:39 what can I do? May 16 22:56:49 I do not find another svn to replace the SRC_URI May 16 22:57:16 otavio, not sure if it's the right fix but try defining that in uboot somewhere: May 16 22:57:17 void __aeabi_unwind_cpp_pr1(){} May 16 22:57:24 GNUtoo-desktop: nanonote: no. I tried to work a bit a couple of years ago :) May 16 22:57:28 GNUtoo-desktop: with that. May 16 22:57:42 zrafa, weren't you the main jlime developper? May 16 22:58:17 GNUtoo-desktop: yes, but I do not have many OE skills. I just built a repository and few images with hacking stuff inside. (that was 2 years ago) May 16 22:58:18 zrafa, for your error why do you need that specific psplash? May 16 22:58:27 ok May 16 22:58:38 nanote seem nice May 16 22:58:44 GNUtoo-desktop: I am trying to "bitbake minimal-image-with-mtd-utils" May 16 22:58:50 ok May 16 22:58:55 oe-classic I guess May 16 22:58:58 GNUtoo-desktop: and It seems that minimal image wants that psplash May 16 22:59:02 GNUtoo-desktop: yes May 16 22:59:13 that's why you have this error: May 16 22:59:27 basically open-hand was bought by intel May 16 22:59:51 so when they were bought they stopped developing the stuff they developped May 16 23:00:06 and the address was not updated because oe-classic is not developed anymore May 16 23:00:18 GNUtoo-desktop: ah, I see. Is some easy way to go further? May 16 23:00:26 some of the stuff has moved to a new server May 16 23:00:35 now intel is behind yocto and stuff has changed in good May 16 23:00:39 ok May 16 23:00:44 zrafa, what is your machine? May 16 23:00:50 nanonote? May 16 23:01:01 i.e. splash screen http://git.yoctoproject.org/cgit/cgit.cgi/psplash May 16 23:01:05 GNUtoo-desktop: I mean.. I do not catch the differences between oe flawors.. If I follow the wiki instructions it seems that I use oe-classic by default May 16 23:01:26 oe-classic is for existing projects.. and is no longer seeing new development.. May 16 23:01:41 oe-core is the base for many distributions poky, angstrom, etc... May 16 23:01:44 zrafa, the main difference is that oe-classic is dead and no longer developed actively....and oe-core is actively developped May 16 23:01:48 oe-core is what you want to move to May 16 23:02:13 there even was a layer for the nanonote May 16 23:02:18 not official tough May 16 23:02:24 because not totally ready May 16 23:02:28 GNUtoo-desktop: it is a tp-link tl mr3020 May 16 23:02:33 GNUtoo-desktop: mips machine, no mipsel May 16 23:02:37 GNUtoo-desktop: 32MB of ram May 16 23:02:42 ok May 16 23:02:49 GNUtoo-desktop: I have some minimal rootfs with kernel and uboot from openwrt May 16 23:02:52 was it supported by oe classic? May 16 23:03:00 GNUtoo-desktop: I wanted to build a minimal or micro image from OE for mips May 16 23:03:14 GNUtoo-desktop: I set qemumips as machine and mips as arc May 16 23:03:15 h May 16 23:03:27 hmmm May 16 23:03:28 GNUtoo-desktop: I do not think so May 16 23:03:34 then do a layer May 16 23:03:37 GNUtoo-desktop: I just choosed mips and qemumips May 16 23:03:38 it's really easy May 16 23:04:06 basically you need at minimum some config files May 16 23:04:11 + a machine config May 16 23:04:16 and some README etc... May 16 23:04:20 a LICENSE May 16 23:04:28 and then you add stuff May 16 23:04:31 like a kernel May 16 23:04:48 because you'll have a big problem if you don't add support for your machine May 16 23:05:03 GNUtoo-desktop: how can I use another oe, and no oe-classic? I just used the instructions from oe wiki and it seems that it uses oe-classic by default? May 16 23:05:20 beside CPU incompatibility I think you want the kernel modules to go in the rootfs May 16 23:05:33 zrafa, hmmm let me look May 16 23:05:38 many of the manuals on the wiki are centered around classic.. they've not been updated.. May 16 23:05:48 indeed that's a big problem May 16 23:05:50 let me look May 16 23:05:51 GNUtoo-desktop: yes, but I just have some kernel from openwrt.. I just would like to have a minimal OE rootfs . I still does not know how to build a kernel for that machine via kernel.org sources May 16 23:06:07 the Yocto Project manuals (for the most part) cover many oe-core tasks.. check out yoctoproject.org and go to the docs.. they are well written IMHO.. May 16 23:06:45 http://www.openembedded.org/wiki/OpenEmbedded-Core ? May 16 23:07:06 fray: that is for me?.. NO sure if I understand. I want to build a minimal rootfs by mips (without kernel maybe). Is that too complex nowadays? May 16 23:07:22 it's actually very easy May 16 23:07:25 zrafa, qemumips is supported by oe core May 16 23:07:32 I was pointing you at documentation that is relevant to oe-core May 16 23:07:37 fray: okey. Then I would like to know how :) May 16 23:07:43 but it's really easy to add a machine config May 16 23:07:49 and a kernel recipe May 16 23:07:52 fray: (to build a minimal rootfs for mips) May 16 23:08:22 GNUtoo-desktop: I will try to do my best, but first I will try to build something . I am a little frustated these days ! :) May 16 23:08:34 ok May 16 23:08:38 http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html#super-user May 16 23:08:44 start there.. May 16 23:09:00 The only thing different w/ oe core is the clone.. May 16 23:09:22 git clone git://git.openembedded.org/openembedded-core May 16 23:09:29 cd openembedded-core May 16 23:09:34 git clone git://git.openembedded.org/bitbake May 16 23:09:41 the rest of hte instructions are applicable May 16 23:10:21 once it's cloned.. you need to source oe-init-buildenv May 16 23:10:26 then setup your conf/local.conf May 16 23:10:29 then run bitbake May 16 23:10:33 core-image-minimal is a good place to start May 16 23:11:00 fray: great.. let me try May 16 23:11:14 GNUtoo-desktop: fray : great for the links pointed.. reading.. May 16 23:20:38 did i miss a gentoo person? May 16 23:20:45 * mr_science waves May 16 23:20:56 fray: which is the relation between yocto project and OE? I am reading : May 16 23:20:58 - http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html#super-user May 16 23:21:02 and May 16 23:21:04 - https://wiki.yoctoproject.org/wiki/OpenEmbedded-Core May 16 23:21:21 yocto project uses oe-core, and heavily contributes to it's development May 16 23:21:38 fray: I will try to follow the instructions from https://wiki.yoctoproject.org/wiki/OpenEmbedded-Core May 16 23:21:52 but no completely sure if to build a minimal image I need to follow that or http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html#super-user May 16 23:22:23 the steps are showing you how to configure and build an image May 16 23:22:49 source, configure, bitbake core-image-minimal May 16 23:24:56 fray: yes, but both links use different git links.. Are them mirrors from the same thing? May 16 23:25:09 look above, I wrote out the git links for oe-core.. May 16 23:25:13 fray: sorry if the questions are too newbie, first time with this stfuff May 16 23:25:18 the ones in the quick start guide for the yocto project are for yocto May 16 23:25:25 git clone git://git.openembedded.org/openembedded-core May 16 23:25:29 cd openembedded-core May 16 23:25:34 git clone git://git.openembedded.org/bitbake May 16 23:25:56 that is the same as the git clone git://git.yoctoproject.org/poky in the quickstart guide May 17 00:49:47 fray: GNUtoo : building minimal rootfs with oe-core.. thanks May 17 01:14:00 hiho **** ENDING LOGGING AT Thu May 17 02:59:59 2012