**** BEGIN LOGGING AT Thu Dec 18 02:59:58 2014 Dec 18 04:55:26 I am trying to compile Yocto Galileo image. I ran the command 'bitbake image-full-galileo' and encountered error. Here is the error message http://pastebin.com/TyVPvPbU Dec 18 04:56:22 Hi. Is anyone around? This channel appears silent Dec 18 05:00:40 teachme: it says why it failed. the only site to retrieve OpenCV-2.4.3.tar.bz2 from is no longer valid as the download doesn't exist anymore. Dec 18 05:03:17 TypoNAM: Thanks for the reply! Would you know where I should put OpenCV-2.4.3.tar.bz2 after it has been downloaded? Dec 18 05:04:57 there should be a downloads/ directory in the parent directory of your build/, put it into that Dec 18 05:05:18 so if you're in build/ right now, then it should go into ../downloads/ Dec 18 05:09:51 TypoNAM: Thanks! besides putting into downloads, do I need to do anything else? Like mark some file to indicate to BitBake that file has been successfully downloaded? Dec 18 05:11:43 nope, just rerun the bitbake command you just tried and it should see the package as already downloaded and proceeds onwards Dec 18 06:29:50 teachme: ping Dec 18 06:34:36 still here Dec 18 06:35:10 Help provided by TypoNAM works. Now, waiting for new error to appear while compiling Dec 18 07:30:24 Has anybody used yocto to build minimal base images for docker? Dec 18 07:46:05 tomprince: you mean this docker? https://www.docker.com/ Dec 18 08:29:13 good morning Dec 18 09:01:46 I am trying to compile Galileo yocto image. There are some errors with patching opencv. http://pastebin.com/Ng7PtAuX Dec 18 09:03:31 I downloaded opencv-2.4.3.2.tar.gz manually. Convert it to OpenCV-2.4.3.tar.bz2. Then, copy it to downloads folder. Run bitbake again and encountered the error Dec 18 09:03:40 Hi. Is anyone around? Dec 18 09:04:00 teachme: sorry to be captain obvious but it seems like you have issue with the patch not finding the file Dec 18 09:04:17 did you try to poke around the working directories to see what's missing? Dec 18 09:04:54 teachme: and, manually recreating archive files will most likely also not work. better check the recipes what going wrong Dec 18 09:05:33 Are the working directories in this location meta-clanton_v1.0.1/yocto_build/tmp/work/i586-poky-linux-uclibc/opencv ? Dec 18 09:05:38 teachme: sorry to bother u with unrelated topic but since you are trying to compile opencv, I assume u got llvm+clang to work? Dec 18 09:06:11 teachme: you can get the working directory by doing bitbake -e | grep ^WORKDIR= Dec 18 09:06:12 pardon my ignorance. I don't know what is llm+clang Dec 18 09:06:28 teachme: excuse my typo, i mean llvm Dec 18 09:09:54 chankit: In the working directories, I only see patches. I do not see opencv.tar.bz2 being unzipped. Maybe that is why file was not found Dec 18 09:11:11 LetoThe2nd: The original problem was that while doing bitbake, opencv cannot be fetched from sourceforge website. So, I downloaded the opencv package manually. I cannot find another website to download the opencv package. How do I go about modifying the recipe in this case? Dec 18 09:12:38 teachme: point the recipe to the available archive (seems to be tar.gz in your case), and replace the checksum with the new, correct one. Dec 18 09:12:53 teachme: if there is no version change involved, this should suffice Dec 18 09:13:23 teachme: randomly replacing with other versions will certainly go *boom* Dec 18 09:13:47 LetoThe2nd: pardon my ignorance. How do I find the new checksum? Dec 18 09:14:24 teachme: look at the md5sum, sha256sum tools Dec 18 09:15:01 teachme: http://www.yoctoproject.org/docs/1.7/dev-manual/dev-manual.html#new-recipe-writing-a-new-recipe Dec 18 09:15:08 So, I have to install md5sum, sha256sum? do a 'sudo apt-get install md5sum'? Dec 18 09:15:21 teachme: this has basically all the necessary information Dec 18 09:15:39 teachme: instead of random shooting apt-commands, maybe check your system first? Dec 18 09:35:20 Hi there Dec 18 09:36:07 I want to use my own kernel, I have sources locally, and I want to use a yocto recipe and append my own recipe with the uri to the local sources using externalsources Dec 18 09:36:21 what is the best yocto recipe I can use (I am building a 3.18 linux kernel) Dec 18 09:41:31 jmleo: you can look at https://github.com/linux4sam/meta-atmel/tree/master/recipes-kernel/linux for example Dec 18 09:41:57 jmleo: the linux-yocto-custom recipes there are not super pretty, but basically self-contained. Dec 18 09:42:01 morning all Dec 18 09:42:55 LetoThe2nd: ok, I'll have a look Dec 18 09:43:49 but this is not using externalsrc Dec 18 09:44:12 It seems that this problem was solved by unzipping the opencv package and copying the unzipped contents to the working directory. Then, the patch is able to find the file to patch. Thanks. But I think modifying the recipe would be the best solution. Unfortunately, it is beyond me at this moment Dec 18 09:45:23 jmleo: i'd look at it as two steps. first, make your own recipe work. then, beat it into shape to additionally accept external source. Dec 18 09:45:58 LetoThe2nd: I already have a custom recipe, but based on a freescale one Dec 18 09:46:06 so I want to clean things up Dec 18 09:46:28 jmleo: so whats the problem then after all? Dec 18 09:47:29 Here is the current recipe Dec 18 09:47:30 http://pastebin.com/dVuUXmDR Dec 18 10:00:45 so, basically, I think it would be good to have this recipe rewritten, as the reference, and a bbappend, which compiles it locally, overwriting SRC_URI and using externalsrc Dec 18 10:02:30 jmleo: sounds like a concept that should work Dec 18 10:05:49 LetoThe2nd: what is the "nocheckout" in the SRC_URI exactly ? Dec 18 10:06:32 jmleo: see http://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#git-fetcher Dec 18 10:09:58 jmleo: i'm not totally sure why its needed or what its good for, its more like "worksforme" Dec 18 10:14:51 LetoThe2nd: ok, here is the failure I saw : http://pastebin.com/Q4j5bT6E Dec 18 10:17:05 jmleo: sorry, i'm no specialist there. we just did base of the recipes i gave you, and it "worked". not much more i can helpfully tell you at the moment, unfortunately Dec 18 10:27:18 Maybe somebody else has an idea... bluelightning perhaps ;) ? Here is a more informations, recipes, and a list of files in the build directory : Dec 18 10:27:19 http://pastebin.com/wW3Qpbv8 Dec 18 10:28:44 jmleo: at this point linux-yocto derived kernel recipes simply do not support building with externalsrc properly I'm afraid Dec 18 10:28:58 there are patches in review to fix that at the moment Dec 18 10:31:50 Adding this in my bbappend, make me able to configure : KERNEL_CONFIG_COMMAND = "oe_runmake_call -C ${S} O=${B} oldnoconfig || yes '' | oe_runmake -C ${S} O=${B} oldconfig" Dec 18 10:32:44 but it seems to not beeing taking the defconfig into account Dec 18 10:52:16 is there a way to avoid configuration step ? Dec 18 10:52:34 I want to have fetch->unpack->compile Dec 18 10:52:37 no configure Dec 18 10:54:09 jmleo: you can set do_configure[noexec] = "1" Dec 18 10:57:56 hi there...anyone done any llvm builing before (regardless of any linux distro) Dec 18 10:58:16 *building Dec 18 11:08:53 Hello! Is anybody successfully using the Sabrelite and the 3.10.31 boundary kernel, with working LCD? On my board, the update seems to have broken LVDS output... Dec 18 11:09:05 Just hoping I'm doing something wrong... Dec 18 11:27:41 mrschmitz: did you get any errors? Dec 18 11:30:51 chankit1: The error I can't seem to get past (assuming this is the issue, still) is: "mxc_sdc_fb fb.30: NO mxc display driver found!", but there is a patch for it, supposedly, but it isn't fixing the issue. LCD was working fine with 3.10.17... Dec 18 11:31:28 chankit1: I have made sure the patch is applied. Dec 18 11:31:57 chankit1: and I am building on the master-next branch Dec 18 11:41:16 Hello! I'm trying to compile an image for raspberrypi with yocto and it's currently stuck at 'bcm2835-bootfiles-20140817-r3 do_fetch' for about 1 hour now. Either this file is too big or it failed to fetch the URL. Can you advise, please? Dec 18 11:41:27 newyoctobie: the repo is big Dec 18 11:41:52 newyoctobie: or rather it's history is large, as a lot of binaries were kept there before Dec 18 11:42:56 bboozzoo: do you know where i can find the log file for this task? Dec 18 11:45:14 newyoctobie: this should be ${TMPDIR}/work/raspberrypi-poky-linux-gnueabi/bcm2835-bootfiles/20140817-r3/temp Dec 18 11:45:49 look for log.do_fetch Dec 18 11:47:54 bboozzoo: yeah, it failed trying to fetch the url Dec 18 11:47:56 DEBUG: Mirror fetch failure for url http://downloads.yoctoproject.org/mirror/sources/git2_github.com.raspberrypi.firmware.git.tar.gz Dec 18 11:49:21 newyoctobie: iirc the fetch task will try a number of mirrors anyway Dec 18 11:53:19 newyoctobie: just checked, the git mirror of github repo is ~3.1GB large Dec 18 11:53:47 bboozzoo: yeah, it's currently cloning firmware.git.. Dec 18 11:54:37 IIRC they used to keep a whole rootfs there, but did a clean up but forgot to remove these large commits Dec 18 11:54:59 and git clone will try to get the complete history for you Dec 18 11:56:41 mrschmitz: I'm sorry I'm afraid I have no expertise on your issue :-( Best of luck Dec 18 11:57:02 chankit1: thank you anyway! Dec 18 11:57:19 bboozzoo: I see, but how can I see the status of the clone command? like how much it's already completed Dec 18 11:59:56 newyoctobie: git clone output is redirected to a something that is not a tty, thus the progress is not visible Dec 18 12:02:08 bboozzoo: OK, thank you very much for the help. Hope it won't take forever :) Dec 18 12:23:45 bluelightning: FYI, I can do a compile using the following steps : http://pastebin.com/Ms70bwGj Dec 18 12:24:11 but this is of course not using bitbake Dec 18 12:24:22 now, I need to change my recipe in order to get the same Dec 18 12:24:45 but the source directory needs to be clean, and the .config needs to be present in the outpout dir Dec 18 12:52:51 any idea why argparse from python stdlib is not built as part of python but as an external package? Dec 18 12:58:08 only python 2.7 and 3.3 are avaialble in master, since argparse is already in python stdlib, separate recipe for python-argparse is redundant Dec 18 13:10:24 bboozzoo: good point... we should probably remove it (and possibly add RPROVIDES / RCONFLICTS / RREPLACES to the python 2.7 recipe) Dec 18 13:25:17 bluelightning: ok, I've removed python-argparse_1.2.1.bb, updated generate-manifest-2.7.py, got a new python-2.7-manifest.inc, so far so good Dec 18 13:26:08 bluelightning: not sure about RCONFLICTS/RREPLACES, the package will also be named python-argparse but the version will be 2.7, will that work as a clean update path? Dec 18 13:26:27 Hi all, is there anyone here who has tried a Beaglebone black with the WL18xx wireless cape on together with an Yocto build? I'm having some problems with the eMMCreset pin getting set to low directly when Linux boots from U-boot Dec 18 13:34:46 bboozzoo: ah right, if the package is the same name there shouldn't be anything extra required there Dec 18 14:54:48 bluelightning: I've sent some patches for python-argparse, it'd be great if you could take a look: http://thread.gmane.org/gmane.comp.handhelds.openembedded.core/58769 Dec 18 16:34:24 chankit: yes. Dec 18 19:52:57 Hi, I'm running a yocto beaglebord build on my beagleboard, I'm having a problem with the eMMCrst gpio pin being set as an input sometime during boot. Does anybody know how I can find out by who it is done? Have checked the board config and it isn't there I think Dec 18 19:59:30 sounds like something you'll need to talk to beagleboard developers about. They should know more about beagle's bootup process and what their BSP is doing. Dec 18 20:09:48 TypoNAM: I have had a discussion on the channel beagle, do you know who makes the beaglebone bsp in yocto? Dec 18 20:10:20 I really don't know. Where are you getting it from? Dec 18 20:19:08 TypeNAM: Sorry, I don't understand the question Dec 18 20:19:17 Getting what? Dec 18 20:19:38 how did you acquire yocto for beagleboard Dec 18 20:20:13 There should be a README file in the layer containing the BSP which should hopefully explain where it is from Dec 18 20:20:29 Hello guys! I am trying to install matchbox-keyboard on CentOS and I'm having some problems. Can you guys lend me a hand? Dec 18 20:21:11 lulzury: shouldn't you be asking that in #centos ? Dec 18 20:21:19 I did, but they couldn't help me. Dec 18 20:21:40 Basically when installing matchbox-keyboard, I get the following error: "configure: error: *** You need to install libfakekey from MB SVN ***" Dec 18 20:22:04 Matchbox is part of the Yocto Project so it would be relevant here, I've not seen it used outside OpenEmbedded though Dec 18 20:22:33 however I already installed libfakeky in /usr/local/lib and updated my /etc/ld.conf Dec 18 20:23:14 Hi Paul, I've used it without problems on ubuntu. I just run apt-get install matchbox-keyboard and it works off the box. However, I've yet to find an RPM for centos that contains this nice app. Dec 18 20:23:29 I tried to build it from source, but to no avail :( Dec 18 20:24:01 have you set PKG_CONFIG_PATH? Dec 18 20:24:49 as in PKG_CONFIG_PATH="-L/usr/local/lib" ? Dec 18 20:25:07 I don't think you need '-L' there Dec 18 20:25:38 and it should be the path to the directory where the .pc file for libfakekey is Dec 18 20:25:56 as it looks like pkg-config is used to search for the library Dec 18 20:28:01 hi paul, when I downloaded fakekeylib from yocto, it only put files on /usr/local/lib, but I see no .pc files there Dec 18 20:28:40 It should have installed libfakekey.pc somewhere Dec 18 20:29:22 It's not software I really use so I'm just making guesses, but there is a libfakekey.pc.in file in the libfakekey repo Dec 18 20:29:35 I assume that should be processed and installed Dec 18 20:30:18 yes, I do see it too. Dec 18 20:30:26 Is the install location somewhere on the make file? Dec 18 20:31:49 pkgconfigdir=$(libdir)/pkgconfig Dec 18 20:32:01 okay Dec 18 20:32:03 let me try that Dec 18 20:32:17 and I assume $(libdir) is /usr/local/lib if you've set prefix to /usr/local Dec 18 20:32:52 yes it looks like that .pc is in there Dec 18 20:33:20 In which case export PKG_CONFIG_PATH="/usr/local/lib/pkgconfig" Dec 18 20:34:41 YAY! alright I got past that error. Thank you for your help paul. Now to find what expat library it needs... Dec 18 20:34:54 Is there a simple way to force bitbake to re-generate a recipe's RPM package (e.g. the package deployed in the rpm folder)? Dec 18 20:40:02 I can do this with ipkg's by doing a "bitbake -f -c package_write_ipk" This, however, doesn't update the RPM (I am using the default RPM package management). Dec 18 20:40:11 Paul!!! Confirmed working with CentOS! Thank you sir! Dec 18 20:40:28 glenn: Try package_write_rpm instead og package_write_ipk Dec 18 20:41:00 There's also package_write_deb for using dpkg if I remember rightly Dec 18 20:42:09 package_write_rpm wasn't listed when I did a "bitbake -c listtasks Dec 18 20:43:39 It (package_write_rpm) fails - target doesn't exist. Just confirmed that. Dec 18 20:45:49 glenn: Is rpm listed in PACKAGE_CLASSES? Dec 18 20:47:20 TypoNam: I just got Yocto, the latest, and builded the beaglebone board, it is supported and it boots fine noproblem Dec 18 20:48:02 That must've been it. Toggling between two yocto projects with different package managers. Seems to have done the trick. Thanks Paul! Dec 18 20:49:02 Now if only my build could finish... I clearly need a better build machine! Dec 18 20:49:44 Rybok: I did some searching and it looks like TI wrote all the BSPs for Beagle boards. I think TI has a community support forum on their website. I wonder if they have an IRC channel on this network. Dec 18 20:50:40 TypeNam: That is great info, thanks alot for that!! I will check that out! Dec 18 20:51:47 paulbarker: mine took ~5 hours to build a fresh yocto image for a i.MX6D board on an AMD Athlon II X2 250 w/ 8GB RAM :P Dec 18 20:51:52 Paul: FYI - by default Yocto says it uses RPM. So I didn't explicitly state 'PACKAGE_CLASSES ?= "package_rpm"' in my local.conf file. Without it being explicitly set, listtasks only offers the ipkg options. You have to explicitly set PACKAGE_CLASSES to package_rpm or listtasks only shows the IPKG tasks. That's what confused me. Dec 18 20:52:56 glenn: Ah ok, I always use ipk (dogfooding) so I've never tried using rpm or deb Dec 18 20:54:05 I usually use IPKG as well. Wanted to try something new . . . maybe I learned a lesson ;-) Dec 18 20:54:21 TypoNAM: I've got an Athlon II X4 so it's marginally better Dec 18 20:55:23 I was using a very shiny rented i7-3770 with 16GB RAM and 1Gbps symmetric internet connection, but I can't justify the cost of that any longer Dec 18 20:55:56 39EUR/month was fine when I was running builds every day Dec 18 20:59:34 yeah Dec 18 23:32:42 * nerdboy 's quick 'n dirty test beaglebone kernel was successful Dec 18 23:33:38 perferred_version=3.17, hardcoded uEnv file and boot console looks better than 3.14 Dec 18 23:34:47 denix says ping zeddii ^^ Dec 18 23:37:06 nerdboy: uEnv should be fixed shortly with the new u-boot-2014.x Dec 18 23:37:28 yeah, i didn't bump u-boot Dec 18 23:37:46 nerdboy: but bump to 3.17 is in zeddii hands Dec 18 23:38:24 still U-Boot 2013.04-dirty (Jul 10 2013 - 14:02:53) Dec 18 23:39:16 nerdboy: so, you'd need a similar bbappend for 3.17 - http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_3.14.bbappend Dec 18 23:39:37 yup Dec 18 23:40:18 nerdboy: and dtb is expected from /boot of rootfs, not FAT partition, hence you need that uEnv for non-standard setup Dec 18 23:40:18 i just kept hearing "fully mainlined" so i made a somewhat brutal test... Dec 19 02:43:15 Hi, If I want to put static libraries to image ( ex, core-image-minimal), can I use IMAGE_FEATURES_append = "staticdev-pkgs"? Dec 19 02:45:00 Perhaps, can I use staticdev-pkgs with SDK () only? **** ENDING LOGGING AT Fri Dec 19 02:59:59 2014