**** BEGIN LOGGING AT Wed Jul 03 02:59:58 2013 Jul 03 09:04:39 Hello. Can anyone explain me how the runtime pkg names are generated? For example the libxau package generates libxau6 rpm. Jul 03 09:05:20 where is that piece of code which does this? Jul 03 09:25:22 agherzan: see debian.bbclass Jul 03 09:25:34 agherzan: it renames packages that contain libraries so they match the library name Jul 03 09:25:48 based on soname right? Jul 03 09:26:02 yes Jul 03 09:27:01 Thanks Jul 03 09:46:16 morning all Jul 03 09:52:37 morning Jul 03 14:01:33 /query ixs Jul 03 14:01:41 er hello nice humans Jul 03 14:02:41 /msg nickserv identify passw0rd Jul 03 14:02:44 ops :/ Jul 03 14:04:39 eren: you may want to change that now :) Jul 03 14:05:19 :P Jul 03 14:05:22 :P Jul 03 14:07:06 JaMa: looks like Qt 5.1 released =) Jul 03 14:08:23 Net147: right, they were faster then me updating _git recipes to use latest SRCREVs with 5.1 :) Jul 03 14:08:24 hi, does yocto support the pacman packaging system (i.e. Archlinux)? Jul 03 14:08:44 lpapp: for the target device? Jul 03 14:09:10 Net147: yep Jul 03 14:09:36 lpapp: rpm, ipkg, deb if I remember correctly. does not support Arch Linux packaging Jul 03 14:10:28 yes, those three are written in the FAQ. Was just wondering because archlinux is pretty common nowadays and pacman is relatively stable and old project. Jul 03 14:10:37 lpapp: patches are welcome =) Jul 03 14:10:45 and pacman got adopted by other distributions as well. Jul 03 14:10:47 new and exciting wrappers for tar! Jul 03 14:10:57 morning Jul 03 14:11:12 Net147: I will welcome them, too. :-) Jul 03 14:11:22 Net147: pity that they haven't released qtwayland 5.1 yet Jul 03 14:11:25 deb, ipk, rpm, and tar are supported Jul 03 14:11:51 (see: poky/meta/classes/package_*.bbclass) Jul 03 14:12:33 JaMa: it is not mature yet. Jul 03 14:12:44 not sure if it can make it for 5.2 Jul 03 14:14:31 eren: i think it's best not to tell people about tar, as you can't build images with tar packages Jul 03 14:15:16 tar's mostly useful together with another package type, when debugging, as they're easier to extract, but even that's questionable value :) Jul 03 14:15:20 lpapp: we're using it already :) Jul 03 14:15:20 * kergoth yawns Jul 03 14:15:40 JaMa: that does not make it mature. ;-) Jul 03 14:16:03 lpapp: the problem is that it's quite picky about versions of other qt5 libs, so I would need to maintain multiple git recipes or support only one qt5 version in meta-qt5 Jul 03 14:17:51 kergoth, how do you use your python deps stuff Jul 03 14:18:01 iinherit the class? Jul 03 14:19:27 and add AUTO_DEPEND_TYPES = "python" Jul 03 14:19:29 JaMa: you're using qtwayland in production? =O Jul 03 14:19:31 is what I tried Jul 03 14:24:21 how about clang support? Jul 03 14:26:50 Crofton: yeah, afaik that should do it. actually, python will go into auto depend types by default right now, just add it to the inheirted package classes, but it has to be after package.bbclass, so it's best off beinga dded to the package classes variable Jul 03 14:27:46 Crofton: to see if it's doing anything at all, you should be able to inspect pkgdata, there should be a new directory in there holding the information after running do_package for a python recipe Jul 03 14:27:58 you can also inspect the info it puts in workdir Jul 03 14:28:03 lpapp: none at the moment Jul 03 14:28:24 be warned, it might eat your babies, i'm the only one that's tested it, and even i've never successfully completed an image build with it enabled yet ;) Jul 03 14:28:28 but it does seem to be working Jul 03 14:31:48 do I need to do it in local.con or the specifc recipe? Jul 03 14:32:37 it sounds like it needs to be applied globally Jul 03 14:32:54 local.conf. I did this in local.conf: PACKAGE_CLASSES = "package_ipk package-auto-deps" Jul 03 14:33:09 tha makes sense Jul 03 14:33:18 I put it in the recipe and the buld diead :) Jul 03 14:33:29 Net147: right. Jul 03 14:34:12 Crofton: the intent was that this generic mechanism would replace the current shlibs bits in package.bbclass, but the individual extra types could be opt-in, if no one objects to that approach Jul 03 14:34:17 Crofton: let me know how it goes Jul 03 14:35:54 will do Jul 03 16:01:35 halstead: ping Jul 03 16:01:48 sgw_, Good morning. Jul 03 16:06:09 I'm trying to get a poky build working for a beaglebone black - i've set my machine to beaglebone, brought in meta-ti and meta-oe but I'm getting an error Jul 03 16:06:12 ERROR: ParseError at /media/scratch/latest/layers/meta-oe/recipes-support/udisks/udisks_1.0.4.bb:20: Could not inherit file classes/systemd.bbclass Jul 03 16:06:56 have I missed something as I'm sure this method used to work https://gist.github.com/17twenty/2712354 Jul 03 16:10:21 exosyst: you're using wrong branch Jul 03 16:10:46 for which part..? meta-ti, meta-oe or poky itself? Jul 03 16:10:59 select one which is compatible Jul 03 16:11:11 exosyst: that depends on what release you want to use Jul 03 16:11:41 exosyst: but you need to use the same release (the same as branch name) for all involved layers Jul 03 16:12:18 e.g. use "dylan" or "master" for everything but don't mix them together Jul 03 16:14:32 JaMa, ok, thanks. I've set them all to dylan and gonna give a core-image-minimal a go. Jul 03 20:39:36 I've set INITSCRIPT_NAME to "snortd" and I've set INITSCRIPT_PARAMS to "start" and snortd is being placed in /etc/init.d and my .bb file explicitly inherits from update-rc.d. So, I would expect that the snortd daemon would get started when my image boots. But my evidence that it is not is that it is not in the output of ps and also that I don't see any message about it in /var/log/messages. Now, I can start the daemon by hand (and then Jul 03 20:39:37 fails and the record of the failure shows up in /var/log/messages). How can I investigate the problem that it doesn't seem to be being started at all? Jul 03 22:38:15 mulhern: did you resolve your /var/volatile issue? Jul 03 22:38:45 mr_science: Yes, thanks! Jul 03 22:39:30 the ro-rootfs patches add volatile config options for recipes Jul 03 22:39:54 mr_science: ro-rootfs? Jul 03 22:40:08 currently you have to make your own config file for /etc/default/volatiles Jul 03 22:40:17 per-recipe Jul 03 22:40:41 yeah, poky-contrib has some read-only root patches Jul 03 22:41:41 as i said, your recipe can add the volatle config so the right dirs/links/files are created at boot time Jul 03 22:44:45 mr_science: Yes, I see the example for dbus. Jul 03 22:46:23 it's pretty straightforward... i made one for mpd in my yocto pi image Jul 03 22:46:52 so ether that, or change your recipe to use a non-volatile path Jul 03 22:48:05 the mpd example would be on github if you want to see it... Jul 03 22:55:50 most of the recipes i've looked at lately just echo "volatile stuff" > 99_foo and install it Jul 03 23:36:04 sgw_: V2 submitted for the Qt 4.8.5 update Jul 03 23:38:48 Net147: thanks! Did you see paul's patch Jul 04 00:52:54 Hi! Jul 04 00:53:15 Does Yocto run on Little Endian-devices? Jul 04 00:57:46 I have a TV that I want to make some more changes to other than just using a wrapping-script. I have bootloader-access. Jul 04 00:57:52 it should Jul 04 00:58:03 mstar Jul 04 00:58:43 CPU-name is Titania. Jul 04 00:59:24 Yes, I know it's a long-shot, but I'm intreeegued to test something else that makes the TV better........ Jul 04 00:59:54 For instance........... in the original EEPROM it's quite difficult to add new drivers. Jul 04 01:01:13 I'm talking about adding the driver for my external USB sound-card so that I can listen to my movies (at night) through my headset/phones. Jul 04 01:01:33 Crofton|work: Where do I start? Jul 04 01:02:06 I know I have to do some reading, but reading is not the strongest part of me. I like to follow guides instead. **** ENDING LOGGING AT Thu Jul 04 02:59:59 2013