**** BEGIN LOGGING AT Tue Dec 17 03:00:00 2013 Dec 17 10:06:02 Hello, good morning. Dec 17 10:06:54 * LetoThe2nd agrees on the "morning" part Dec 17 10:09:17 morning all Dec 17 10:24:09 <__ccube> Please use a umask which allows a+rx and u+rwx Dec 17 10:24:22 <__ccube> what exactly is here wrong? Dec 17 10:25:34 <__ccube> check_sanity_eventhandler outputs this when trying to build with buildbot Dec 17 10:27:51 __ccube: the yocto autobuilder which is based on buildbot set umask to 022 Dec 17 10:28:00 __ccube: so maybe buildbot changes the umask Dec 17 10:28:26 __ccube: i do recommend you try yocto-autobuilder, it's based on buildbot and pretty neat for yocto builds Dec 17 10:29:17 <__ccube> is it kind a fork of buildbot? Dec 17 10:29:40 no, it uses buildbot Dec 17 10:29:53 <__ccube> k Dec 17 10:29:54 there are a few patches to buildbot in the repo iirc Dec 17 10:30:00 buildbot is a framework etc etc Dec 17 10:30:02 <__ccube> ill have a a look at it. :) Dec 17 10:31:00 <__ccube> thx Dec 17 10:32:04 <__ccube> seems to work when settind umask 022 in build script. Dec 17 11:02:39 rp: have you had a chance to look at my proposed git fetcher changes? Dec 17 11:07:06 zibri: not enough to write a detailed enough reply :( Dec 17 11:07:28 zibri: I think some of the patches are ok but some also make me nervous Dec 17 11:07:30 right. would you prefer it if i break out the "real" changes from the unittest changes? Dec 17 11:11:18 zibri: there probably is a bit much going on in that specific commit, yes Dec 17 11:11:55 rp: which commit are you refering to? Dec 17 11:14:40 zibri: I don't know Dec 17 11:14:57 zibri: let me go and look at the patches :/ Dec 17 11:14:59 (because i don't see that. but the patch series does contain two distinct changes, the reason for this being that i tried to do my change "tdd-ish") Dec 17 11:19:13 zibri: the trouble with these patches is you're both splitting things up into smaller functions for testing purposes and changing the behaviour Dec 17 11:20:08 zibri: it makes it harder to see what is going on, at least to the way I visualise things. There isn't anything wrong with the patches as such, it just isn't easy for me to parse Dec 17 11:20:30 zibri: every time I touch the fetcher, I end up with several weeks of bug fixing as we break corner cases :( Dec 17 11:21:24 zibri: I will try and merge some of the patches and then look closer at the remaining ones Dec 17 11:22:01 * RP has now lost track of the sstate business I was trying to look at Dec 17 11:23:48 rp: sure. but i did try to avoid changing behavior for the test changes at least. the exception is the changes to _contains_ref, but afaict it's only used within the git fetcher. Dec 17 11:47:40 dany: ping Dec 17 11:58:09 Hi all, What is the procedure to have two image builds? I have got one for my regular use and I want to create another test image with just some recipes on it. How can I have two build directories? Dec 17 11:59:10 Zaif: for building two images you don't need separate build dirs Dec 17 11:59:16 Zaif: just separate image recipes Dec 17 11:59:24 unless I'm misunderstanding the question Dec 17 12:00:06 If I run bitbake test-console-image, does it swipe my old rootfs files in build directory and replace it with new rootfs? Dec 17 12:00:25 bluelightning ^ Dec 17 12:00:58 Zaif: for test-console-image yes, but if you have a test-console2-image or some other recipe name, that's a completely separate image Dec 17 12:02:09 bluelightning ok got it. Dec 17 12:05:49 bluelightning Why is yocto build showing Currently 1 running tasks (5057 of 5059): , eventhough I have just 10 small recipes in my test-console-image.bb recipe? Dec 17 12:06:06 Is it building again all those recipes? Dec 17 12:07:24 Zaif: it's not building them all again, if it's at 5057 of 5059 it's probably just doing do_rootfs for the image Dec 17 12:08:16 bluelightning ok. got it. Thank you Dec 17 12:10:41 Hi everyone. "PREMIRRORS_prepend = "\ git://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ ..." in local.conf (as described in http://www.yoctoproject.org/docs/1.0/poky-ref-manual/poky-ref-manual.html ) doesn't seem to work for me. I get "Fetcher failure for URL: 'git://git.yoctoproject.org/prelink-cross.git'. Unable to fetch URL from any source". Any pointers? Dec 17 12:13:41 Dennis__: that's a really old version of the manual - which version of the build system are you using? Dec 17 12:14:21 Using 1.4 dylan i think Dec 17 12:14:45 ok, in which case the current manual is at: http://www.yoctoproject.org/docs/1.4/ref-manual/ref-manual.html Dec 17 12:14:53 (for 1.4) Dec 17 12:15:49 Dennis__: we do already set those mirrors up though Dec 17 12:16:14 Dennis__: if you're trying to set up your own internal mirror I'd recommend using own-mirrors though, it's a lot easier to use Dec 17 12:17:20 Dennis__: https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_create_my_own_source_download_mirror_.3F Dec 17 12:17:33 (assuming that's what you're trying to do) Dec 17 12:20:38 yes we already have that for some images, but now im trying to build sdk and it seems the system wants some additional sources, that are not yet on our internal mirror. that works fine as long as there are http mirrors available but it doesn't work for packages with only git: available Dec 17 12:24:58 It's not able to pull git sources of the form 1.0+gitAUTOINC+6822ec76aa-r0 Dec 17 12:29:15 I'm using poky so the premirrors are already correctly defined in meta-yocto/conf/distro/poky.conf but it still isn't able to receive prelink-cross 1.0+gitAUTOINC+6822ec76aa-r0 Dec 17 12:42:47 bluelightning it works when i change the SRC_URI in the prelink_git.bb to "git://git.yoctoproject.org/git/prelink-cross.git;protocol=http" Dec 17 12:45:55 the problem is that some recipes use custom git tags and those don't seem to be available via http://downloads.yoctoproject.org/mirror/sources/ Dec 17 13:27:32 Dennis__: perhaps git is being blocked by your firewall/proxy? Dec 17 13:54:41 bluelightning: yes that's exactly why i need to have working premirrors, sadly this isn't the case for packages that use SRCREV in their recipes (they all seem to have a name *_git.bb). Dec 17 13:55:44 im now using local.conf to define custom mirrors for those packages, because in the end the repositories are mostly available over http, Dec 17 13:56:05 MIRRORS =+ "\ git://git.yoctoproject.org/prelink-cross.git git://git.yoctoproject.org/git/prelink-cross;protocol=http \n " Dec 17 14:39:26 How Do I install pam_faildelay package Dec 17 14:39:40 is there any recipe exist for the same? Dec 17 14:54:13 Any suggestion for installing pam_faildelay package Dec 17 14:57:26 ramose: is that part of pam or some third-party add-on? Dec 17 14:58:27 bluelightning: I think its part of PAM module Dec 17 15:03:31 ramose: each pam plugin is in a separate package - I think you just need to install pam-plugin-faildelay Dec 17 15:06:43 bluelightning: would you tell me ,how should I intsall this pam-plugin-faildelay package Dec 17 15:06:59 I never install any packge earlier Dec 17 15:07:10 ramose: you just need to add it to your image Dec 17 15:07:11 ramose: http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Dec 17 15:10:02 bluelightning: but I have to define a recipe for that,right? Dec 17 15:14:12 ramose: well, probably you should have your own image recipe Dec 17 15:14:37 yes i have my own image recipe Dec 17 15:14:50 ramose: ok, then you should just add to IMAGE_INSTALL within that Dec 17 15:15:37 bluelightning: Thanks ,I guess its compiling through bitbake Dec 17 15:15:58 just for understanding wanted to know where its souce is ? Dec 17 15:16:37 i mean there must be some recipe file where pam tarball will be fetched and compiled ,right? Dec 17 15:17:18 ramose: sure, the pam recipe can be found in meta/recipes-extended/pam/ Dec 17 15:18:25 bluelightning: ok ,let me check the poky source. Dec 17 15:19:00 bluelightning: also one more small point wanted to check with you Dec 17 15:20:32 ramose: sure Dec 17 15:21:04 currently my sshd authentication is going through /etc/passwd file but can I still use pam-plugin-faildelay to do task like delaying ssh login time? Dec 17 15:24:15 ramose: as far as I know, if the system is configured to use PAM then it should be using that for authentication Dec 17 15:24:24 ramose: are you using OpenSSH or dropbear? Dec 17 15:24:31 openssh Dec 17 15:24:45 do you have pam in DISTRO_FEATURES? Dec 17 15:26:55 bluelightning:Do I have to check local.conf for that? Dec 17 15:28:29 ramose: if you haven't set it yourself, the answer will be no Dec 17 15:28:58 ramose: if you want to use PAM, you do need to add it though if you haven't done so Dec 17 15:29:15 i.e. DISTRO_FEATURES_append = " pam" Dec 17 15:29:31 and yes you would need to do that in local.conf or your custom distro config Dec 17 15:29:52 http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#creating-your-own-distribution Dec 17 15:30:40 ok fine bluelightning :but would it make any conflict with sshd authentication happening through /etc/passwd? Dec 17 15:32:57 ramose: with PAM enabled, it would simply do that via PAM Dec 17 15:46:56 bluelightning: It means it would override the earlier authentication way,right? Dec 17 15:47:30 ramose: if you enable PAM, yes, I suspect it will Dec 17 15:47:43 I'm not much of an expert on PAM though Dec 17 15:51:29 ok no prob @bluelightning,Thanks for your time:) Dec 17 15:53:47 ramose: no problem :) Dec 17 15:58:17 The Yocto Project Tech Meeting Con-Call will be starting at the top of the hour Dec 17 15:58:17 Dial-in number: 1.972.995.7777 / Participant passcode: 42001078 Dec 17 15:58:17 This call is open to all and the channel remains open to discuss any topic Dec 17 15:59:33 YPTM: Saul is on Dec 17 16:00:01 YPTM: Matthew is on Dec 17 16:01:03 YPTM: Scott Rifenbark joined the call. Dec 17 16:01:29 alex d in the room Dec 17 16:01:41 YPTM: polk is on Dec 17 16:02:02 YPTM: Björn joined the call Dec 17 16:02:03 YPTM: beth is on Dec 17 16:02:04 YPTM: Bruce is on Dec 17 16:02:10 YPTM: Mark is on the call Dec 17 16:02:14 YPTM: Welcome to the technical team meeting. Please let me know who's on the line. Thanks! Dec 17 16:02:17 YPTM: belen is on the call Dec 17 16:02:19 YPTM: Paul Eggleton is on Dec 17 16:02:23 YPTM: Tom Z on Dec 17 16:02:33 YPTM: jzhang on the call Dec 17 16:02:33 YPTM: also Beth & AlexD are in the same room Dec 17 16:02:45 * halstead present in YPTM Dec 17 16:03:10 YPTM: Any opens? Dec 17 16:06:08 YPTM: I'm no longer on the call, and can't dial back in for some reason. Dec 17 16:06:16 YPTM: Darren has joined Dec 17 16:06:48 is there a present for holiday bug fixing. like an extra present in our stocking. Dec 17 16:07:05 Cookies for bugs ? Dec 17 16:07:17 doughnuts Dec 17 16:07:57 pidge: skinny dougnuts? Dec 17 16:08:04 YPTM: I'm back Dec 17 16:09:20 YPTM: Denys is on, sorry I'm late Dec 17 16:10:01 no cookie for you denix Dec 17 16:10:05 denix: np. We just got started. talking about 1.5.1. the QA report will be out this Friday Dec 17 16:10:21 Song_Liu: thanks Dec 17 16:10:54 pidge: drats, that would ruin my holidays :) Dec 17 16:12:19 hi there Dec 17 16:12:47 hi Xz Dec 17 16:12:47 is there any other way to send a patch to openembedded-core than git send-email or sending patch as email content? Dec 17 16:13:21 Xz: you can send a pull request, it's almost the same thing but there is a git branch attached Dec 17 16:13:40 Xz: see scripts/create-pull-request and send-pull-request Dec 17 16:13:48 sgw_1 louder please Dec 17 16:14:04 turn up your volume! Dec 17 16:14:51 sgw_: you were fine after Beth asked the first time, then you went back to the earlier volume Dec 17 16:15:36 /msg sgw_ Amy's sister was nominated for a local radio content "Christmas Wish"... http://www.youtube.com/watch?v=y8zBogtExbo Dec 17 16:15:46 oops Dec 17 16:16:19 bluelightning: what's the difference between git request-pull and git push? Dec 17 16:16:36 (link goes to video scrapbook I put together) :P Dec 17 16:17:03 * fray blames the cat that just jumped on the table for the errant 'space' :P Dec 17 16:17:53 Xz: "git push" pushes a branch to a remote; I'm not sure about "git request-pull" but our pull request scripts take care of generating and sending the emails after you've pushed the branch somewhere Dec 17 16:18:55 trying to create a recipe for the library libpqxx, the configure scripts call a script called pg_config --libdir to know where is the libpq library. When I compile natively, I have to put pg_config in path, but how to manage the path in yocto ? And is it possible to browse the image ? Dec 17 16:20:00 weebet: pg_config is something produced by postgresql I assume Dec 17 16:20:41 bluelightining yes, you are right. the recipe postgresql_9.2.4 is in one of my meta Dec 17 16:21:27 weebet: is the recipe installing that into an appropriate place such that it ends up in PATH? Dec 17 16:21:38 weebet: and is it returning the right answer? Dec 17 16:21:56 i.e. it needs to be reporting the appropriate path from the sysroot Dec 17 16:24:20 bluelightning : I think it will end up in /usr/bin but I did not yet created the image. I bet I cannot only bitbake postgresql then libpqxx. I will have to put them in an image first ? Dec 17 16:25:00 weebet: if libpqxx needs pg_config then you need to have postgresql in the libpqxx recipe's DEPENDS value Dec 17 16:25:23 YPTM: thank you all for joining the meeting. Happy holidays! Dec 17 16:25:44 bluelightning : good clue. I will try it now. Thank you Dec 17 16:25:45 pidge, sgw_ I'll swap ab06 out for fedora20. might as well start with an easy one. :) Dec 17 16:26:09 halstead: have you done any builds on F20? Dec 17 16:26:23 it's still Beta right? Dec 17 16:26:31 sgw_, I've only tested core-image-sato for x86. Dec 17 16:26:37 sgw_, Released this morning. Dec 17 16:27:26 Ok can you try x86-64 and arm first core-image-sato-sdk, yes it will take a few hours Dec 17 16:29:03 sgw_, I'll test those before adding back to the pool. Does that sound good? Dec 17 16:29:18 thanks Dec 17 16:32:09 bluelightning : adding the depend does not help, I will try to add them to my image. I'm not sure, but would it be possible that since pg_config from the recipe postgresql is built for arm and yocto is built from a x86 so it cannot load pg_config to see where is the library path... no ? probably there is a LDFLAGS to tell the script where to look for the library Dec 17 16:32:59 weebet: this is a similar situation we've dealt with for other recipes... e.g. apr Dec 17 16:33:30 bluelighning : thank you I will look at it Dec 17 16:33:36 weebet: this isn't really about image, this is about what goes into the sysroot on the build side Dec 17 16:33:49 about the image, that is Dec 17 16:34:24 bluelightning : I am a newb with yocto and it is a very big black box. It is very difficult to understand what is going on inside Dec 17 16:35:02 weebet: have you had a look at the new "Closer Look" section? http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#closer-look Dec 17 16:35:17 it should help explain a lot of how the build system operates Dec 17 16:35:52 Quick question, how can I know the quantity of packages Yocto has? And where can I see a list of them? Dec 17 16:36:45 vicenteolivert: well, there's a couple of different answers to that question - there's what we provide in the poky repository (i.e. OE-Core) and there's what's available out there in the community Dec 17 16:36:47 blielightning : thank you for the link. Dec 17 16:37:03 YPTM: by the way, let me know if anyone could come up with a holiday bug fixing present. I'll see if we have budget for it. It also depends on how much we can bring the WDD down during the time. Dec 17 16:37:14 vicenteolivert: there is an index of layers here: http://layers.openembedded.org Dec 17 16:37:33 vicenteolivert: if you look under "openembedded-core" you can see what we provide out of the box Dec 17 16:37:54 bluelightning: I mean the ones I can put in IMAGE_INSTALL_append. Dec 17 16:38:54 vicenteolivert: most recipes produce a package of the same name as the recipe Dec 17 16:39:04 vicenteolivert: but some produce additional packages, e.g. for optional modules Dec 17 16:39:11 vicenteolivert: there isn't really a central list of these Dec 17 16:39:31 vicenteolivert: are you looking for something specific? Dec 17 16:40:00 vincenteolivert : i guess you mean you want to know what is available on your repo with the layers installed on your computer ? I guess bitbake -s is what you are looking for. Dec 17 16:40:05 bluelightning: no, just wondering how many packages were available on Yocto. Dec 17 16:40:57 weebet: bitbake -s kind of works, but that's really a list of build targets i.e. it includes native and cross stuff Dec 17 16:41:36 Ok, maybe I haven't explained myself very well... I mean, for instance, if you install Gentoo, you have all the packages in the portage tree available. If you install Debian, you have all the packages in debian repositories (base, contrib, non-free) available. Dec 17 16:41:40 patch I have is for poky master branch, I'm trying to send it to 'openembedded-core@lists.openembedded.org' Dec 17 16:41:43 am I doing something wrong? Dec 17 16:42:03 Xz: ideally it should be applied on top of the openembedded-core repository rather than poky Dec 17 16:42:30 bluelightning: so when I do 'git send-email' I should rather execute it form openembedded-core repo? Dec 17 16:42:39 Xz: right Dec 17 16:42:43 bluelightning: so far I tried doing it from poky/ repo Dec 17 16:43:10 Xz: usually I just do "git format-patch" from my poky repo and then "git am" those on top of an openembedded-core tree Dec 17 16:43:48 bluelightning: git://git.openembedded.org/openembedded-core Dec 17 16:43:50 bluelightning: this one? Dec 17 16:43:53 Xz: yes Dec 17 16:44:10 vicenteolivert: we make a distinction between recipes and packages - a recipe may (and usually does) produce more than one package Dec 17 16:45:09 bluelightning: yes, I know. Package is what you get installed and recipe is the scrip that generate that/those installed packages. Dec 17 16:45:18 *generates Dec 17 16:49:07 vicenteolivert: indeed Dec 17 16:50:04 bluelightning: tried 'git send-email' now directly from openembedded-core and the same result - 'The mailinglist requires people to subscribe before posting' Dec 17 16:50:20 bluelightning: In my commit I include commit message and signed off Dec 17 16:50:26 bluelightning: have no idea what could be wrong Dec 17 16:50:27 Xz: yep, whatever from email you have set must be subscribed to that list Dec 17 16:51:17 bluelightning: when I try to submit using that email - I'm being sent an email saying 'Mailman privacy alert: An attempt was made to subscribe your address to the mailing list xyz.org. You are already subscribed to this mailing list.' Dec 17 16:51:33 bluelightning: so I'd say I'm already subscribed :) Dec 17 16:51:51 Xz: I suspect the email address it's using when you use git-send-email is not what you think it is... it should be printing it though Dec 17 17:03:22 <__ccube> hi, I am trying to get my yocto autobuilder working. The job fails at Running Preamble with a /bin/sh: ./oe-init-build-env: No such file or directory error. Any hints how to investigate? Dec 17 17:05:07 __ccube: sounds like maybe you are running that from the wrong directory? Dec 17 17:05:40 although in theory I guess that should be working out of the box Dec 17 17:06:01 Beth isn't around at the moment but she should be back here in a short while Dec 17 17:08:56 <__ccube> autobuilder itself is running fine, but just my builds are failing. i can see that the git command is working in the build dir of yocto-slave. after finishing the git clone, the files are disappearing Dec 17 17:09:11 <__ccube> are they moved to another working idr or sth? Dec 17 17:09:28 I'm not too sure, this is definitely a question for Beth Dec 17 17:09:39 unless rburton knows what might be going on Dec 17 17:11:24 <__ccube> k, so ill wait for beth Dec 17 17:11:30 <__ccube> thx Dec 17 17:16:06 __ccube: autobuilder from git? grab the "dora" tag, not master. Dec 17 17:16:19 <__ccube> hm Dec 17 17:16:33 __ccube: master got "improved" which "broke" it :) Dec 17 17:16:45 <__ccube> ok, so I hit a known bug? Dec 17 17:17:02 <__ccube> will my whole config work with dora roight now? Dec 17 17:28:03 <__ccube> rburton, Dec 17 17:35:00 <__ccube> looks like, switched to dora, building now. lets see if the error is gone. Dec 17 17:51:19 what should be the variable to point to the /usr/lib ? I tried ${WORKDIR}/usr/bin but no luck ... yes I know, I am trying absolutely anything Dec 17 17:52:09 what exactly are you doing? Dec 17 17:52:18 ${WORKDIR}/usr/bin doesn't make any sense Dec 17 17:53:45 <__ccube> looks better, but now.... 'our version of bblayers.conf has the wrong LCONF_VERSION (has 6, expecting 5). Dec 17 17:56:33 kergoth : I am trying to port the library libpqxx but needs the lpq from postgresql. So I have to tell the ./configure script where is the lpq library. as bluelighning told me, I added a DEPENDS = "postgresql" and using EXTRA_OECONF = "POSTGRES_LIB = ${variable}/usr/lib" (postgresql place his library in /usr/lib as seen in postgresql image directory. Dec 17 17:59:22 POSTGRES_LIB="${STAGING_LIBDIR}" Dec 17 17:59:48 when recipes use one anothers files, they look in the sysroots. STAGING_LIBDIR is a convenience variable pointing to the libdir in the current host sysroot Dec 17 18:01:19 thank you a lot kergoth Dec 17 18:04:03 np Dec 17 18:05:21 <__ccube> GetDistroVersion failes. what exactly does it? Dec 17 18:07:16 __ccube: hi, what can I help you with? Dec 17 18:07:29 <--- autobuilder maintainer Dec 17 18:07:36 <__ccube> are you beth? Dec 17 18:08:01 __ccube: yes Dec 17 18:08:06 <__ccube> :) Dec 17 18:08:08 <__ccube> well, i try to get my autobuilder to work Dec 17 18:08:21 __ccube: what revision are you on? Dec 17 18:08:27 <__ccube> i was told to use dora branch Dec 17 18:08:33 kergoth : is there any other staging variable to point to /usr/bin ? Dec 17 18:08:50 and where did you learn the existence of this variable ? Dec 17 18:09:04 <__ccube> pidge, or what do you mean with revision? Dec 17 18:09:46 weebet: see meta/conf/bitbake.conf for most of these Dec 17 18:09:49 __ccube: yes, dora branch is fine, so what seems to be the issue? Dec 17 18:10:24 bluelightning: Thank you I found some interesting info there : http://docs.openembedded.ru/directories_staging.html Dec 17 18:10:58 <__ccube> everything goes green until GetDistroVersion. This failes. But I do not get any oputput there. Then I am getting 'your version of bblayers.conf has the wrong LCONF_VERSION (has 6, expecting 5).' error in build step Dec 17 18:11:30 weebet: that manual is very old, I'd suggest using the yocto project manuals instead Dec 17 18:13:49 __ccube: how very odd. can you please pastebin (or other appropriate site) your build-config for that build? Also, in the root of your yocto-autobuilder directory the output of git rev-parse HEAD Dec 17 18:14:37 <__ccube> ok, I got another problem right now. Ill do so in few minutes Dec 17 18:14:38 __ccube: my guess is something is going wrong with how you're doing CreateBBLayers.conf Dec 17 18:14:52 er CreateBBLayersConf Dec 17 18:15:36 <__ccube> {'CreateBBLayersConf': {'buildprovider' : 'yocto', 'layerdirs': ['meta-allwinner','meta-java','meta-openembedded/meta-oe','meta-oracle-java']}}, Dec 17 18:17:23 __ccube: 'buildprovider' : 'oe' See: nightly-oecore Dec 17 18:18:15 __ccube: also, you should have this: {'GetDistroVersion' : {'distro': 'oecore'}}, Dec 17 18:18:38 <__ccube> ok Dec 17 18:18:40 <__ccube> ill try Dec 17 18:21:39 __ccube: email me or ping me here if it doesn't. Dec 17 18:21:51 <__ccube> pidge, :) thank you Dec 17 18:22:01 __ccube: no problem Dec 17 18:31:16 * mr_science making his laptop whine Dec 17 18:42:35 <__ccube> pidge, why exectly do i have to set 'buildprovider' : 'oe instead of poky? Dec 17 18:42:52 <__ccube> s/poky/yocto/g Dec 17 18:45:05 __ccube: if you're using this as an oecore build (checking out oe-core and bitbake type build) build provider gives you an easy way to produce a distroless build/set up the bblayers for oecore type builds. If you're not doing it like that and are actually checking out poky, then yes, buildprovider should be yocto. Sorry if I made a bad assumption Dec 17 18:46:12 <__ccube> ah ok. Dec 17 18:46:23 __ccube: if I can see the conf you're trying to build I could probably figure this out in a few moments. Dec 17 18:47:02 <__ccube> I defined my own distro in one of my custom layers. So should I use that in GetDistroVersion? Dec 17 18:47:13 <__ccube> ok, Ill post you my configs Dec 17 18:47:23 __ccube: thanks Dec 17 18:48:05 <__ccube> can I send you a mail with them attached? Dec 17 18:52:19 ccube: sure elizabeth.flanagan at intel.com Dec 17 18:52:28 again with my libpqxx port, the recipe depends on postgresql-9.4.2. In sysroots, I cannot find the postgres executable, only header and library. In the postgresql image directory (in work directory) I can see them in image/usr/bin is there something I does not understand ? Dec 17 18:54:39 yes, how exactly are yo ugoing to run a binary from a different architecture? Dec 17 18:54:58 we're crosscompiling, bin files from a target recipe would make no sense Dec 17 18:56:38 kergoth : I don't know ! There is a lot of black hole I does not understand. Dec 17 18:57:36 libpqxx want to use the software pg_config to find the include dir and lib dir. Dec 17 19:06:30 and even if I add extra_oeconf with parameter to specify where are the directories, it will look in my path for pg_config Dec 17 19:07:35 pidge, sent Dec 17 19:09:05 weebet: sounds like you want to call the $staging_bindir_native/pg-config Dec 17 19:09:35 is there a postgresql in your native sysroot? Dec 17 19:10:14 mr_science thank you, hummm... I feel really bad asking that, but ... what is the native sysroot ? Dec 17 19:10:58 look under tmp/sysroots/x86_64 or i686/ for postgres Dec 17 19:11:25 you should have a native sysroot under sysroots/ Dec 17 19:11:44 ccube: ok. I'll look at it in a moment. Dec 17 19:13:44 :) Dec 17 19:14:01 pidge, just tell me if you need more config/logs Dec 17 19:14:07 mr_science : in sysroots I have x86_64 Dec 17 19:14:16 but no sign of postgres Dec 17 19:15:01 no pg-config? Dec 17 19:15:37 mr_science nothing for postgresql, no lib, no header, no pg_config no postgres no psql ... Dec 17 19:17:44 what happens if you try "bitbake postgresql-native" ? Dec 17 19:18:43 nothing. I copied the postgresql_9.2.4.bb from openembedded repo. I will see if it is available Dec 17 19:19:00 waht do you mean "nothing"? Dec 17 19:19:02 elaborate Dec 17 19:19:26 sorry, nothing provides 'postgresql-native' Dec 17 19:20:43 the recipe postgresql-native is not available in the openembedded repo Dec 17 19:21:00 ccube: Ah, ok, two issues. You may want to do 'GetDistroVersion' : {'distro': 'poky'}} I know, that seems silly, but, we use it as a way to determine how to set up auto.conf. As for the LCON_VERSION issue, that's a bit puzzling. I'd need to see the output from CreateBBLayersConf. Dec 17 19:21:21 ccube: if you email this to me I can look at it in the morning. heading out. Dec 17 19:21:52 pidge, I already tried distro poky, but Ill set it again. Output coming soon :) Dec 17 19:22:24 cool. thanks! Dec 17 19:25:38 weebet: shouldn't be too difficult to add a native recipe Dec 17 19:26:00 but i'm kinda stuck in oe-classic all day... Dec 17 19:27:43 mr_science : I am sure it is not needed. I can't believe I will not find a way to tell configure script where are the directory instead on relying on pg_config script. this is a non-sense Dec 17 19:28:30 not a bad idea to have native tools available during the build Dec 17 19:29:00 tho i'm oretty sure there's more than one way to do it... Dec 17 19:29:10 *pretty sure even Dec 17 19:38:58 I guess I will have to patch the configure script Dec 17 19:41:20 weebet: pgsql-native would probably be easier and support more packages Dec 17 19:43:21 thank you, I'm looking to find it :-) Dec 17 19:45:21 for some recipes, all it takes is the bbclass extend native thing Dec 17 19:45:35 i'd try that first Dec 17 19:46:06 ok, I will do that now Dec 17 19:48:55 mr_science were you involved in the creation of the lighttpd recipe ? Dec 17 19:49:29 nope, i only have a couple of minor/indirect contributions to meta Dec 17 19:50:08 just the nginx one, plus some rpi/erlang stuff Dec 17 19:50:27 ok, TY. I will have to understand how to insert lighttpd module in an image Dec 17 19:50:58 shouldn't be hard... Dec 17 19:51:51 it is easy to copy the package, but how to insert it during my image creation... it is a mystery Dec 17 19:54:34 you can try rdepending on it, or add it to your image recipe Dec 17 20:01:44 my problem is that I cannot find how to call the module. I can add lighttpd on my image but when I try to add ie: lighttpd_mod_fastgi it does not work. Dec 17 20:03:03 the package name is probably lighttpd-module-fastcgi Dec 17 20:03:25 ok, thank you. I will try this :-) Dec 17 20:10:30 mr_science : thank you for the advice of postgresql-native it only needs few changes to make it work **** ENDING LOGGING AT Wed Dec 18 02:59:59 2013