**** BEGIN LOGGING AT Fri Feb 26 02:59:58 2016 Feb 26 03:46:56 I'm hoping someone on here can help me with the following error message "Can't install no package provides libzmq.so.3()(64bit)" Feb 26 03:47:48 I am using an existing zeromq recipe and trying to build an image for intel-corei7-64. Feb 26 03:49:24 Prior to trying to add my package which requires zeromq, I verified zeromq is being built and included in the image, but it is clearly not the type (64 bit?) that is being expected. Feb 26 04:14:25 Hi , i'm building yocto fido branch with that i'm getting do_configure error for gcc https://paste.kde.org/pxdjjnezy, can anyone please help Feb 26 04:30:09 is giving for bitbake core-image-minimal Feb 26 04:30:23 *its Feb 26 04:44:48 tknccy: that looks really weird Feb 26 04:45:05 are you using fsl-community setup? Feb 26 04:46:41 yes Feb 26 04:47:06 I got this for dizzy too Feb 26 04:49:22 built for me on jethro with a patch for the snmp fail Feb 26 04:53:05 with a patch for the snmp fail? Feb 26 04:55:39 net-snmp needs a fix unless it's been pushed Feb 26 04:56:30 don't install it and core-image-minimal should build Feb 26 04:58:45 daisy did not gave me this error Feb 26 04:59:01 it built successfully Feb 26 05:00:12 any special features/packages? Feb 26 05:00:21 and which machine? Feb 26 05:02:51 no nothing, just built core-image-minimal, but the broblem with that image was the board stuck in while booting, and everyone suggested to try for newer branch, the logs https://paste.kde.org/phvslptom Feb 26 05:02:54 its sabresd Feb 26 05:03:15 8problem Feb 26 05:04:03 it didn't gave me prompt Feb 26 05:04:37 neo built fine for me on jethero, booted normally (mostly) Feb 26 05:04:47 *jethro even Feb 26 05:05:11 ok Feb 26 05:05:23 i can't test a sabresd image but we'll go ahead and build one Feb 26 05:06:16 ok let me try jethro too Feb 26 05:11:02 hmm, need to finish the migration stuff after the reboot Feb 26 05:15:48 ?? Feb 26 05:19:46 switching to pax xt flags on the build server Feb 26 06:19:00 nerdboy: weird , I restarted the computer and again gave a bitbake in fido branch the error went off Feb 26 06:19:36 but that isn't the logical reason though Feb 26 06:22:04 maybe some env variables were mangling Feb 26 10:46:48 Hello everyone Feb 26 10:48:28 I'm trying to build oe for beagleboard and im hitting an issue with meta ti: Feb 26 10:48:46 WARNING: Failed to fetch URL svn://gforge.ti.com/svn/dmai/;module=UNDEFINED_DMAIBRANCH;protocol=https;user=anonymous;pswd='' ... Feb 26 10:48:52 and longer list of issues Feb 26 10:49:30 it looks like beagleboard.conf and omap3.inc were not parsed Feb 26 10:50:09 here is the build config Feb 26 10:50:10 Build Configuration: BB_VERSION = "1.20.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-14.04" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "beagleboard" DISTRO = "poky" DISTRO_VERSION = "1.5.4" TUNE_FEATURES = "armv7a vfp neon" TARGET_FPU = "vfp-neon" meta meta-yocto meta-yocto-bsp = "dora:8e9e7e8def9b0b728937d34115f7165677c31bed" meta Feb 26 12:00:48 when will there be a point release for jethro, yocto-2.0.1? Feb 26 12:05:47 shortly Feb 26 14:15:59 rburton: shortly is a good answer :) Feb 26 16:11:31 hi, quick question: I want to release my yocto recipes to the customer, with the downloads directory Feb 26 16:11:54 this way the customer doesn't have to download from the internet, avoiding potential issues the day that some website is shut down Feb 26 16:12:10 the first thing I did was a git add downloads Feb 26 16:12:24 remove the git2/git.customer.org* files Feb 26 16:12:35 so they can continue developing their own stuff and rebuild it Feb 26 16:12:41 but it seems to be not working Feb 26 16:14:15 LocutusOfBorg: you probably forgot to enable BB_MIRROR_TARBALLS Feb 26 16:14:33 erm, BB_GENERATE_MIRROR_TARBALLS Feb 26 16:14:39 if you want to share a dldir, best to do that Feb 26 16:15:15 indeed. for what its worth, what you're trying to do is fairly common and should work fine if you do what rburton says Feb 26 16:15:34 we do that at mentor with our mel installers, ship downloads so BB_NO_NETWORK will work Feb 26 16:17:00 the problem is BB_NO_NETWORK is not feasible Feb 26 16:17:11 because I want the customer git services to be available from internet Feb 26 16:17:20 you know, they might continue developing the internal tools Feb 26 16:17:37 but indeed I can generate mirror tarballs and add them to the conf Feb 26 16:17:40 let me try that Feb 26 16:20:57 INHERIT += "own-mirrors" Feb 26 16:20:57 SOURCE_MIRROR_URL ?= "file://${TOPDIR}/../sources/" Feb 26 16:20:57 BB_GENERATE_MIRROR_TARBALLS = "1" Feb 26 16:21:01 let's try this Feb 26 16:22:30 LocutusOfBorg what version of YP? Feb 26 16:22:47 There are multiple settings to restrict network access, BB_NO_NETWORK is just one of them Feb 26 16:22:47 fido :( Feb 26 16:22:57 I use jethro for other projects, but this one is on fido Feb 26 16:23:32 look if you have the bitbake commit "c7263096ba31ba45daeeb9de90c1cb9ebef24a28" Feb 26 16:23:43 commit c7263096ba31ba45daeeb9de90c1cb9ebef24a28 Feb 26 16:23:43 Author: Liam R. Howlett Feb 26 16:23:43 Date: Thu Apr 16 13:23:18 2015 -0400 Feb 26 16:23:43 fetch2: Add BB_ALLOWED_NETWORKS support Feb 26 16:23:50 the commit msg has the usage instructions Feb 26 16:24:49 nope, I don't have it Feb 26 16:24:59 backport it then.. or you can't do what you want Feb 26 16:27:41 ack thanks Feb 26 16:28:07 git branch --contains 59ce7d02 Feb 26 16:28:08 jethro Feb 26 16:40:38 <_william_> hi all, i would need please some help to compile an image using debian packages (sdk 1.9). I am trying to build a simple fsl-full-image, but it fails with some missing packages (target is ppc64el built on an amd64). Il looks like it uses "local /etc/apt/sources.list" for repo definition, and not what is in the rootfs. Any know issues about this ? **** BEGIN LOGGING AT Fri Feb 26 17:11:54 2016 Feb 26 17:19:12 anybody have experience changing window managers on an image? I'm trying to set up metacity but having problems Feb 26 23:02:56 ok guys, back with a new problem... Feb 26 23:03:12 now I somehow advanced to package 3500 out of 5000 and so and Feb 26 23:03:20 it gives an error I cna't solve with good ol' google Feb 26 23:03:25 with "mraa" Feb 26 23:03:33 the log: Feb 26 23:03:34 https://ghostbin.com/paste/tuss6 Feb 26 23:03:40 the last lines I've copied from the terminal; Feb 26 23:03:47 [ 58%] Built target mraajs| make[1]: Leaving directory '/home/sixsmith/Desktop/galileo/build/tmp/work/i586-poky-linux/mraa/0.8.0-r0/build'| Makefile:126: recipe for target 'all' failed| make: *** [all] Error 2| ERROR: oe_runmake failed| WARNING: exit code 1 from a shell command.| ERROR: Function failed: do_compile (log file is located at /home/sixsmith/Desktop/galileo/build/tmp/work/i586-poky-linux/mraa/0.8.0-r0/temp/log.do_compile.2406)ERROR: Task 682 Feb 26 23:03:47 (/home/sixsmith/Desktop/galileo/meta-intel-iot-middleware/recipes-devtools/mraa/mraa_0.8.0.bb, do_compile) failed with exit code '1' Feb 26 23:04:04 in the log it says it can't find some header file (.h) Feb 26 23:04:25 I'm trying to build this for galileo Feb 26 23:04:34 but it's a real pain in the ass Feb 26 23:05:29 also why the heck do you need such crazy amounts of space? I made a 80 gb vdi now and at package ~3500/5000 I ahve about 14 gb left... this almost surely means I will run out of space once again and it really pisses me off Feb 26 23:05:44 the only thing I wanted is to put gphoto2 Feb 26 23:05:50 it fucking kills me Feb 26 23:09:58 is there a way to build a "minimal" image, based on only what I specifically want it to do? I hate it when I waste other people's time with stupidities like this, but process of making a yocto build for galileo is a real mess Feb 26 23:10:29 RP: another rpm5 failure :( Feb 26 23:11:22 fray: around? Feb 26 23:12:43 rburton: :( Feb 26 23:13:20 rburton: back it out and try again? do we want to risk meta-poky in the next one? Feb 26 23:16:24 huh Feb 26 23:16:32 Your gcc version is older than 4.5 or is not working properly. Please verify you can build and link something that uses atomic operations, such as: Feb 26 23:16:32 __sync_bool_compare_and_swap (&atomic, 2, 3); Feb 26 23:16:35 says the AB Feb 26 23:18:28 rburton: note the AB just gained some new builders Feb 26 23:19:16 yeah, suse 42.1 has gcc 4.8.5 Feb 26 23:19:29 trying to remember what can cause that to trip when its not gcc Feb 26 23:20:05 rburton: missing libs of some kind? Feb 26 23:21:37 hm appears to be working now Feb 26 23:21:48 halstead_: have you been fixing opensuse421? Feb 26 23:22:40 rburton, I just set it up. I'm testing it with a ross/gi build now. Feb 26 23:23:29 halstead: lots are failing with sanity test failure, gcc not working Feb 26 23:23:33 RP: http://errors.yoctoproject.org/Errors/Details/37943/ <— was this you? Feb 26 23:25:42 rburton, I'm looking at them. Still trying to orient. Feb 26 23:26:04 halstead: one concrete thing: fedora23 builder needs perl-bignum installed Feb 26 23:26:28 rburton, That's what I was currently doing. Feb 26 23:26:33 great Feb 26 23:26:46 the suse421 machine is always failing like https://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/674/steps/BuildImages/logs/stdio Feb 26 23:27:03 rburton, I wasn't positive if the was supposed to be in the host environment or built. Feb 26 23:27:22 halstead: its a rpm that generally doesn't get installed out of the box for some reason (its a standard perl module) Feb 26 23:27:36 RP: Still around? Feb 26 23:28:18 rburton, Should it be added to the Fedora setup in the Yocto Quickstart? Feb 26 23:28:29 halstead: it should be there Feb 26 23:29:43 rburton, Ah I was looking at the 2.0 quickstart Feb 26 23:29:45 halstead: have you fixed anything on the suse421 machine? i can't make a build that failed in the AB fail by hand if i ssh in. Feb 26 23:31:06 rburton, I added 54 new packages in the last half hour. Feb 26 23:31:35 that might be it :) Feb 26 23:32:28 halstead is a troublemaker Feb 26 23:32:47 hm debian83 didn't like doing any fetches Feb 26 23:32:50 rewitt_: yes Feb 26 23:33:05 it's a beard requirement... Feb 26 23:33:29 RP: re cleansstate, it looks like it's not deleting it because it only deletes what is in sstate-cache/*/* Feb 26 23:33:31 proportionally speaking Feb 26 23:33:31 rburton: yes, I suspect that was me Feb 26 23:33:37 RP: DEBUG: For url ['git', 'anonscm.debian.org', '/collab-maint/ncurses.git', '', '', {}] comparing ['npm', '.*', '/.*', '', '', {}] to ['file', '', '//srv/www/vhosts/autobuilder.yoctoproject.org/current_sources', '', '', {}] <— looks like your npm uri fix to me Feb 26 23:33:55 I try to limit troublemaking to just a few times a year at least. Feb 26 23:34:17 RP: http://pastebin.com/F1CRWpy0 Feb 26 23:34:28 rburton: I favour http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=a83ac4a6b4c1429d19fe99b32f8cb76b2f6366bc myself Feb 26 23:35:31 rewitt_: and why is that incorrect? Feb 26 23:35:56 gi has a few non-trivial fails Feb 26 23:36:01 lets just run mut tonight :) Feb 26 23:36:11 rburton: yes, we need a baseline now... Feb 26 23:36:26 RP: Because it isn't deleting the file sstate-cache/sstate:glibc:i586-poky-linux:2.23:r0:i586:3:7b9e20d645347583443a0385eebe8137_populate_sysroot.tgz Feb 26 23:36:47 rewitt_: a symlink? Feb 26 23:37:31 No, that's a real file 53MB, the one in sstate-cache/7b was the symlink Feb 26 23:37:43 rburton: I assume you'll let alex know about the fails? Feb 26 23:37:46 yes Feb 26 23:38:10 rewitt_: ok, what is happening is the fetcher downloads this from the mirror, its gets placed in the wrong location so the system symlinks it Feb 26 23:39:10 rewitt_: line 629 sstate.bbclass Feb 26 23:39:32 rewitt_: how about we make that move the file? Feb 26 23:40:48 RP: I think it's a safe assumption that won't be a move across a filesystem boundary, so I'm fine with that. I just noticed this problem because I'm trying to make the sstate automatically get removed after a setscene. Feb 26 23:41:11 rewitt_: agreed, this should be in the same filesystem Feb 26 23:41:33 RP: Ok, I'll make that change with the patchset I'm working on Feb 26 23:42:50 RP: should i revert those in mut? Feb 26 23:43:14 halstead: are you still fixing things, or can i re-kick a nightly? Feb 26 23:43:27 rburton: I have a fix for the path issue Feb 26 23:43:37 rburton: two mins and I'll update master-next Feb 26 23:43:43 rburton, I was just about to ask you if I could interrupt for a new test Feb 26 23:43:52 halstead: go for it Feb 26 23:44:12 rburton, Would you like to start it? Feb 26 23:44:17 All stopped now, Feb 26 23:44:40 i'll kick a nightly ross/mut once RP has updated master-next Feb 26 23:44:51 and then, go to bed and await the carnage in the morning :) Feb 26 23:45:24 rburton: -next updated/pushed Feb 26 23:45:44 rburton, If I need to kill a restart a few times tonight while testing is that a problem as long as I leave it building a ross/mut in the end? Feb 26 23:45:46 rburton: note meta-poky is in there so you may not want that bit Feb 26 23:46:04 halstead: absolutely fine! Feb 26 23:46:11 RP: erm yeah do you mind if i revert that Feb 26 23:46:34 rburton: or just rebase it out Feb 26 23:46:49 rburton: I'll test separately over the weekend Feb 26 23:46:55 i've started to like reverts for clarity to myself Feb 26 23:47:08 rburton: whichever... Feb 26 23:48:42 fired! Feb 26 23:48:49 now i'm running before i can see it break Feb 26 23:48:56 :) Feb 26 23:49:39 halstead: I did give you ross' mobile number for the SMS notifier on the AB right? Feb 26 23:49:58 gah, he left Feb 26 23:50:17 RP, Not yet. But I have a twillo account ready so we can set that up. Feb 26 23:50:31 Not sure what the UK cost per SMS is though. ;) Feb 26 23:51:12 well, his branch broke as he reverted half the change Feb 26 23:51:20 let me push a better fix... Feb 26 23:52:26 halstead: it would be tempting even just for a laugh :) Feb 26 23:53:33 RP, I imagine Beth's reaction would be memorable if we did it with her number. Feb 26 23:54:36 halstead: yes, this is sounding better and better :) Feb 27 00:00:21 halstead: we're ready for another try with ross/mut Feb 27 00:02:18 RP, Okay starting one presently. Feb 27 00:04:51 halstead: thanks Feb 27 00:08:35 Hi gurus! Feb 27 00:09:20 I am trying to use qemux86-64 and can't get past the following error during a bitbake of core-image-rt: Feb 27 00:09:38 ERROR: User requested feature sdl | configure was not able to find it. | Install SDL devel | | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_configure (log file is located at /home/dmikulin/dev/yocto/poky/build-q64/tmp/work/x86_64-linux/qemu-native/2.4.0-r1/temp/log.do_configure.13632) ERROR: Task 72 (virtual:native:/home/dmikulin/dev/yocto/poky/meta/recipes-devtools/qemu/qemu_2.4.0.bb, do_config Feb 27 00:10:34 dmikulin: do you have the sdl libraries installed? Feb 27 00:10:48 dmikulin: if you don't need qemu graphics, you could disable sdl (see local.conf) Feb 27 00:10:50 ERROR: User requested feature sdl Feb 27 00:11:00 configure was not able to find it. Feb 27 00:11:12 Install SDL devel Feb 27 00:11:26 halstead: this build looks better. the fsl-ppc issues are sad but not surprising with the udev change in that branch Feb 27 00:11:34 libsdl1.2-dev is installed as is libsdl2-dev Feb 27 00:12:00 dmikulin: sdl1.2 != sdl2 Feb 27 00:12:13 RP, I was just about to ask if those had to do with the build hosts or not. Feb 27 00:12:26 halstead: no, they're that branch for sure Feb 27 00:12:41 Okay, but libsdl1.2 is what is needed (I think) and it is definitely installed in my host. Feb 27 00:12:52 I don't need graphics. Feb 27 00:13:12 Are there other sdl libraries that I need installed? Feb 27 00:13:25 dmikulin: you need libsdl1.2-dev Feb 27 00:13:32 dmikulin: or remove PACKAGECONFIG_append_pn-qemu-native from local.conf Feb 27 00:13:39 (the append of sdl) Feb 27 00:14:03 sudo apt-get install libsdl1.2-dev [sudo] password for dmikulin: Reading package lists... Done Building dependency tree Reading state information... Done libsdl1.2-dev is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Feb 27 00:14:29 If libsdl1.2-dev is already installed, why am I getting this error message? Feb 27 00:14:38 dmikulin: which distro and which version of the project are you using? Feb 27 00:14:54 Ubuntu 15.10, Yocto Project 2.0 (jethro) Feb 27 00:15:46 dmikulin: can you share tmp/work/x86_64-linux/qemu-native/2.5.0-r1/build/config.log somewhere? Feb 27 00:16:12 dmikulin: I'm guessing there is an error in there which might better help show what is going on. I use ubuntu15.10 myself so it should work... Feb 27 00:16:33 dmikulin: oh, hang on. There is a problem with jethro Feb 27 00:17:12 hanging on... Feb 27 00:17:33 dmikulin: https://bugzilla.yoctoproject.org/show_bug.cgi?id=8553 Feb 27 00:17:34 Bug 8553: normal, Medium+, 2.1, ross.burton, VERIFIED FIXED, qemu-native to build on Ubuntu 15.10 Feb 27 00:17:54 dmikulin: workaround add BUILD_LDFLAGS_prepend_pn-qemu-native = "-Wl,-rpath-link,/lib/x86_64-linux-gnu " to local.conf Feb 27 00:18:10 dmikulin: its fixed in master but not in jethro yet :/ Feb 27 00:18:34 I will try that. Feb 27 00:20:32 halstead: looks like that build is working so I'm getting some sleep :) Feb 27 00:20:43 halstead: the updated set of distros looks good! Feb 27 00:20:56 RP, Alright. I'm around tomorrow if anything sticks. Feb 27 00:21:05 * halstead waves. Feb 27 00:21:34 RP: that seems to be working. I'm passed do_configure and onto do_compile Feb 27 00:21:41 Thanks! Feb 27 00:21:57 And thank you. Feb 27 00:24:35 BTW, I found a typo in one of the Yocto manuals with respect to using qemu for X86-64... it could trip others up. Trying to find it again. Feb 27 00:35:10 RP: Okay, it might not be a problem, but in section 6.2.2 "Using the runqemu command", it says that the QEMU machine architecture should be qemux86_64. For MACHINE, further down it says qemux86-64. Are these supposed to be different (one using underscore, the other using a dash)? Feb 27 00:35:37 RP: this is in the 2.0 version of the manual. **** ENDING LOGGING AT Sat Feb 27 02:59:58 2016