*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC | 00:02 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 00:03 | |
*** ant_home <ant_home!~andrea@host88-64-dynamic.8-87-r.retail.telecomitalia.it> has quit IRC | 00:16 | |
-YoctoAutoBuilder- build #237 of nightly-mips-lsb is complete: Failure [failed Building Images Building Images_1] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-mips-lsb/builds/237 | 00:17 | |
*** frank <frank!~frank@1.202.252.122> has quit IRC | 00:45 | |
*** _julian <_julian!~quassel@x2f00e69.dyn.telefonica.de> has joined #yocto | 00:56 | |
*** _julian_ <_julian_!~quassel@x2f14f06.dyn.telefonica.de> has quit IRC | 00:57 | |
*** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has quit IRC | 00:59 | |
-YoctoAutoBuilder- build #226 of build-appliance is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/build-appliance/builds/226 | 01:01 | |
wmat | seebs: I thought CodeSOurcery toolchains required 32 bit libs? | 01:02 |
---|---|---|
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has quit IRC | 01:04 | |
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has joined #yocto | 01:05 | |
-YoctoAutoBuilder- build #203 of nightly-oecore is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-oecore/builds/203 | 01:15 | |
*** mitz <mitz!~mitz@KHP222227247006.ppp-bb.dion.ne.jp> has quit IRC | 01:21 | |
-YoctoAutoBuilder- build #228 of nightly-arm-lsb is complete: Failure [failed Building Images Building Images_1] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-arm-lsb/builds/228 | 01:21 | |
lpapp | sgw_: now, yes | 01:21 |
seebs | wmat: They do, yes. | 01:22 |
seebs | One of the problems we appear to have is that even if you set NO32LIBS to 0, we still don't actually *try* to build 32-bit libpseudo unless the host environment has a particular 32-bit header file, which is probably a poor choice. | 01:22 |
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has joined #yocto | 01:22 | |
seebs | Originally, we tried to build 32-bit libpseudo on 64-bit machines if they had that file. Then the NO32LIBS stuff got added, but the check for the file wasn't changed, so there's no way to indicate "we actually require 32-bit libpseudo and if you can't build it that is a serious problem that should be reported". | 01:23 |
wmat | seebs: ah | 01:25 |
sgw_ | lpapp: We are making progress, I posted a patch thanks to you and kergoth for the sourcery toolchain in core, and as seebs points out we found my problem with not having a 32bit libpseudo built (different than your problem). | 01:25 |
sgw_ | lpapp: what we are trying to understand now is bug 4919 which is why your native build of a 32bit libpseudo is not finding the appropriate 32bit libraries from /usr/lib32 | 01:26 |
yocti | Bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=4919 normal, Medium, 1.5, peter.seebach, NEW , Failure when trying to build on Archlinux 64 bit host with 32 external toolchain | 01:26 |
wmat | does it break when using meta-sourcery too? | 01:26 |
wmat | on a 64bit machine | 01:27 |
sgw_ | wmat: Yes, I beleive it failed on my machine also, but I would have to go back and check, but now that I have the gnu/stubs-32.h it will succeed. | 01:28 |
wmat | hmmm, i'm surprised Mentor didn't encounter this | 01:28 |
lpapp | wmat: they do not use a sane distro. | 01:29 |
lpapp | where lib is the 64 bit. :) | 01:30 |
lpapp | i.e. the default is the system you are on. | 01:30 |
lpapp | sgw_: do you have an arch machine? | 01:30 |
lpapp | sgw_: if not, can you get one into chroot? | 01:31 |
sgw_ | lpapp, I am trying to build an Arch system, can you send me (by email ) a full package list that you have installed, so I don't have to go through the tap-dance of installing packages | 01:31 |
sgw_ | or a list that I can put on the pacstrap command line initially | 01:31 |
sgw_ | lpapp: I am building a VirtualBox image now | 01:32 |
lpapp | sgw_: sorry, I have no any clue. | 01:33 |
lpapp | sgw_: you can check what the requirement is for other distributions. | 01:33 |
sgw_ | lpapp: can you give me a list of what's installed on your system, that will go a long way to help. | 01:34 |
lpapp | lpapp: well, it would be useless for you. | 01:34 |
*** mitz <mitz!~mitz@KHP222227247006.ppp-bb.dion.ne.jp> has joined #yocto | 01:34 | |
lpapp | and would hold you up for quite a while. | 01:35 |
lpapp | as I have tons of packages installed | 01:35 |
lpapp | you probably do not need 90% of it. | 01:35 |
sgw_ | Not having would equally hold me up | 01:35 |
sgw_ | because every false start will require me to install another thing | 01:35 |
lpapp | sgw_: just check the requirements | 01:35 |
lpapp | and use pacman -Ss for them | 01:35 |
-YoctoAutoBuilder- build #228 of nightly-x86-lsb is complete: Failure [failed Building Images Building Images_1] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-lsb/builds/228 | 01:36 | |
lpapp | that is what I would do. | 01:36 |
seebs | A casual check confirms that about half of the 64-bit hosts I use have x86_64 in /usr/lib, and x86 in /usr/lib32. It doesn't matter at all. | 01:38 |
lpapp | seebs: well, why does it look in the wrong directory then? | 01:40 |
lpapp | it should look into /usr/lib32 | 01:40 |
lpapp | but it looks into /usr/lib | 01:40 |
seebs | Well, that's a really vague and open-ended question. Why does "it" look in the wrong directory? Which "it"? | 01:41 |
lpapp | 02:40 < lpapp> it should look into /usr/lib32 | 01:41 |
lpapp | 02:40 < lpapp> but it looks into /usr/lib | 01:41 |
seebs | The pseudo build specifies a -L for sqlite3 when compiling the pseudo executable which is wrong on some systems, but generally harmless if you are using the host system's sqlite, so it doesn't matter. | 01:41 |
seebs | So we have tons of successful builds where there's an extra -L which has nothing to do with anything. | 01:42 |
seebs | See, here's the thing. | 01:43 |
seebs | You said something. In that thing, you used the pronoun "it". I did not know what you were using that pronoun to refer to. | 01:44 |
seebs | So I asked you what "it" was. | 01:44 |
seebs | And you… *repasted the same two lines as though I had not just seen them*. | 01:44 |
seebs | You did not indicate whether you were talking about gcc, or whether you were talking about -L arguments or about some other compiler diagnostic, or whether you were talking about the runtime linker, or anything else. Instead, you insultingly repeated what you'd just said as though if I'd just read that I would have known what you were talking about. | 01:45 |
lpapp | see the bugreport for details please. | 01:45 |
seebs | But that's not the case at all. Nothing in there tells me what "it" is. Nothing tells me where in the process you are observing a failure, or what the failure is. | 01:45 |
lpapp | it is all pasted there, really. | 01:45 |
lpapp | I thought you have gone through that already... | 01:45 |
seebs | See, the thing is. Without the insulting re-paste of exactly the opposite of an answer to my question, I might well. | 01:45 |
seebs | But as is, I'm going back to ignoring you because you are rude and entitled and uncooperative, and it is *not useful* to spend time trying to derive valuable information from this. | 01:46 |
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC | 01:46 | |
lpapp | there is no any insult in trying to help you. | 01:46 |
*** joshc <joshc!~joshc@rhlug/joshc> has quit IRC | 01:46 | |
-YoctoAutoBuilder- build #64 of minnow-lsb is complete: Failure [failed Building Images] Build details are at http://autobuilder.yoctoproject.org:8011/builders/minnow-lsb/builds/64 | 01:47 | |
lpapp | thanks you so much for stop helping with unblocking me! | 01:47 |
lpapp | thank you* | 01:47 |
lpapp | hack, then I cannot really say this Yocto thingie "supported". | 01:48 |
seebs | I found the repasting of the exact text I'd asked for clarification of to be insulting, because it was the opposite of an answer. | 01:48 |
seebs | Even just responding with "there's more details in the bug report" would be less obnoxious. | 01:48 |
lpapp | I am tired of having issues with every setup possible. | 01:48 |
lpapp | repasting is exactly repeating "it". | 01:48 |
lpapp | I honestly do not know how to tell more. That is all very clear to me. | 01:49 |
lpapp | Besides, the bugreport was filed relatively long ago. | 01:49 |
seebs | "it should look into /usr/lib32" <-- this sentence here. | 01:49 |
lpapp | it is not an unreal expectation to read an already existing report before asking? | 01:49 |
seebs | I asked what "it" was. As in, *WHAT* should look into /usr/lib32? | 01:49 |
sgw_ | lpapp: I spent a good part of my day looking into this with seebs, I am working into my evening to setup a currently unsupported OS to try and test a situation that should work (lib32) | 01:49 |
seebs | gcc? | 01:49 |
seebs | sqlite? | 01:49 |
seebs | pseudo? | 01:49 |
seebs | The shell? | 01:49 |
seebs | ld.so? | 01:49 |
seebs | We have no idea. "it" should. | 01:49 |
lpapp | sgw_: yeah, I appreciate that. | 01:49 |
sgw_ | lpapp: If you keep this up we will just punt | 01:50 |
lpapp | now, that annoys me. | 01:50 |
seebs | Anyway, looking at your bug report, you're ignoring a very clear error message from the compiler and focusing on the distracting but ultimately irrelevant warnings. | 01:50 |
lpapp | I am trying to help *after* my work gours | 01:50 |
lpapp | hours | 01:50 |
lpapp | in my leisure time | 01:50 |
lpapp | see, it is 02:50 am | 01:50 |
lpapp | and normal people sleep rather than collaborating here. | 01:50 |
seebs | Quick test. Run "gcc -m32 -o hello hello.c" with a normal hello world. | 01:50 |
lpapp | I rather go back to sleep, I do not need this stress. | 01:50 |
lpapp | everything is in the bugreport, bye | 01:51 |
seebs | If that works, and "gcc -L/usr/lib -m32 -o hello hello.c" doesn't, then you have an issue. | 01:51 |
sgw_ | I know it's later there, you can help by trying things, but your not willing to help that way. | 01:51 |
*** swex <swex!~swex@178.17.201.225> has quit IRC | 01:51 | |
seebs | Eh, the bug report comes down to "lots of irrelevant errors, also key 32-bit libraries aren't installed". | 01:51 |
seebs | The compiler will search /usr/lib32 by default on a 32-bit host. The warnings about the incompatible libraries it's skipping are irrelevant. | 01:52 |
lpapp | sgw_: what things, really? | 01:52 |
lpapp | sgw_: information is all provided I can. | 01:52 |
seebs | What's important is that it isn't finding -lgcc and -lpthread, and if it's not finding those, that's because they're not installed. | 01:52 |
*** swex <swex!~swex@178.17.201.225> has joined #yocto | 01:52 | |
lpapp | sgw_: I am trying to collaborate at *02:30* am for the fuck sake | 01:52 |
lpapp | will you be here at 02:30 am, hello? | 01:52 |
lpapp | Honestly, I do not feel appreciated even though I came here at fucking 02:30 | 01:53 |
seebs | I frequently am. :) | 01:53 |
lpapp | so good night guys | 01:53 |
seebs | And anyway, I told you what's wrong. | 01:53 |
seebs | You can fix it or not. | 01:53 |
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has quit IRC | 01:54 | |
lpapp | seebs: sorry, but you do not make any sense | 01:54 |
lpapp | -L/usr/lib is unnecessary first of all | 01:54 |
lpapp | secondly, I said gazillion times 32 bit stuff is in /usr/lib32 | 01:54 |
seebs | Yes, we know. | 01:54 |
seebs | echo "int main(void) { return 0; }" > hello.c | 01:55 |
seebs | gcc -L/usr/lib32 -m64 -o h hello.c | 01:55 |
lpapp | I am tired, good night. | 01:55 |
lpapp | see you tomorrow | 01:55 |
seebs | => A couple of "/usr/bin/ld: skipping incompatible /usr/lib32/libc.so when searching for -lc" messages. | 01:55 |
seebs | And it links successfully anyway. | 01:55 |
seebs | Because those messages are not errors, they are just warnings. | 01:55 |
seebs | The actual problem is that your compiler isn't finding the libraries it needs, and those diagnostics are irrelevant, because they aren't what's wrong with the compiler. Either the compiler's busted or you don't have *the right* 32-bit libraries in /usr/lib32. | 01:56 |
seebs | The most common problem with this setup is that you have runtime libraries but not development libraries for the 32-bit environment. | 01:56 |
sgw_ | I giess I am back to trying the arch linux. | 01:57 |
wmat | seebs: is there any tests I can run to help? I'm on a 64-bit Ubuntu host with a dylan source tree and old codesourcery toolchain (same as lpapp's). | 02:00 |
sgw_ | wmat: we really need an Arch Linux, I have an Ubuntu system (12.10) and it's fine | 02:00 |
wmat | ah, ok | 02:00 |
seebs | It's pretty easy to get the same error out of others, I believe. | 02:01 |
*** joshc <joshc!~joshc@rhlug/joshc> has joined #yocto | 02:01 | |
*** mario-goulart <mario-goulart!~user@email.parenteses.org> has joined #yocto | 02:01 | |
seebs | Pretty sure this is exactly the behavior you'd get if you had runtimes but not the -dev packages for your 32-bit stuff. | 02:01 |
seebs | And that's a really common configuration, since most systems won't install the development stuff for 32-bit if they're 64-bit native, they just install enough runtime to run the executables. | 02:02 |
sgw_ | seebs, but would it have the header files for 32-bit (like the stubs-32.h) without the development libs? | 02:02 |
seebs | Maybe! | 02:02 |
seebs | It's certainly possible to get some systems into that state. You could, say, have the libc-dev-32 package (whatever they call it), but omit the pthread-dev-32 and libgcc-dev-32. | 02:03 |
sgw_ | ah, well I am working on the arch install (both syslinux and grub failed to install, so I am kind of stuck right now) | 02:04 |
seebs | The "skipping incompatible <foo>" messages are a red herring, you can get those easily by specifying extra -L and they don't do any harm. | 02:04 |
*** sakoman <sakoman!~steve@static-74-41-60-154.dsl1.pco.ca.frontiernet.net> has quit IRC | 02:05 | |
sgw_ | seebs: without his package list, we can't actually determine for sure if what you suggest above is correct and he was unwilling to give that list to me. | 02:06 |
sgw_ | I could easily install the "right things" and have it work. | 02:06 |
seebs | That's my guess. The lib/lib32 thing is a red herring, although it might not be a bad thing to fix it just to reduce the flood of irrelevant diagnostics. | 02:07 |
wmat | don't remove those warnings, just open a ticket to document this use case in the official documentation | 02:08 |
wmat | if it turns out to be valid, that is | 02:09 |
seebs | It might not be a bad idea to, when specifying the exact path for the sqlite library, just drop the -L. | 02:10 |
*** silviof2 <silviof2!~silviof@ppp-188-174-41-83.dynamic.mnet-online.de> has joined #yocto | 02:12 | |
*** silviof1 <silviof1!~silviof@ppp-88-217-75-129.dynamic.mnet-online.de> has quit IRC | 02:15 | |
-YoctoAutoBuilder- build #222 of nightly-x86-64 is complete: Failure [failed Running Sanity Tests Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-64/builds/222 | 02:31 | |
*** __frank_ <__frank_!~frank@1.202.252.122> has joined #yocto | 02:38 | |
*** sakoman <sakoman!~steve@static-74-41-60-154.dsl1.pco.ca.frontiernet.net> has joined #yocto | 02:39 | |
*** mitz <mitz!~mitz@KHP222227247006.ppp-bb.dion.ne.jp> has quit IRC | 02:39 | |
*** mitz <mitz!~mitz@KHP222227247006.ppp-bb.dion.ne.jp> has joined #yocto | 02:41 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 02:53 | |
*** sakoman <sakoman!~steve@static-74-41-60-154.dsl1.pco.ca.frontiernet.net> has quit IRC | 02:53 | |
*** sakoman <sakoman!~steve@static-74-41-60-154.dsl1.pco.ca.frontiernet.net> has joined #yocto | 03:07 | |
*** sakoman <sakoman!~steve@static-74-41-60-154.dsl1.pco.ca.frontiernet.net> has quit IRC | 03:12 | |
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has quit IRC | 03:16 | |
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has joined #yocto | 03:32 | |
-YoctoAutoBuilder- build #196 of nightly-fsl-arm-lsb is complete: Failure [failed Building Images Building Images_1 Building Images_2] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm-lsb/builds/196 | 03:46 | |
*** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 03:54 | |
*** behanw <behanw!~behanw@216-58-123-51.cpe.distributel.net> has quit IRC | 03:55 | |
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 03:58 | |
-YoctoAutoBuilder- build #228 of nightly-x86 is complete: Failure [failed Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86/builds/228 | 03:59 | |
*** agust <agust!~agust@p4FC461E3.dip0.t-ipconnect.de> has joined #yocto | 04:20 | |
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC | 04:24 | |
-YoctoAutoBuilder- build #225 of nightly-ppc-lsb is complete: Failure [failed Building Images Building Images_1] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-ppc-lsb/builds/225 | 04:34 | |
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has quit IRC | 04:48 | |
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has joined #yocto | 05:01 | |
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has quit IRC | 05:04 | |
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has joined #yocto | 05:05 | |
*** lpapp <lpapp!~lpapp@cpc11-cmbg15-2-0-cust30.5-4.cable.virginmedia.com> has joined #yocto | 05:07 | |
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto | 05:07 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 05:13 | |
*** tor <tor!~tor@c-ef66e655.125-1-64736c10.cust.bredbandsbolaget.se> has joined #yocto | 05:45 | |
*** mthalmei_away is now known as mthalmei | 06:11 | |
melonipoika | morning all | 06:13 |
melonipoika | basic question, does anyone know the name of the package that provides xvfb in yocto? | 06:13 |
-YoctoAutoBuilder- build #197 of nightly-fsl-arm is complete: Failure [failed Building Images_1] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm/builds/197 | 06:13 | |
*** mthalmei is now known as mthalmei_away | 06:15 | |
lpapp | melonipoika: which version? | 06:23 |
lpapp | melonipoika: have you checked the graphics recipes? | 06:24 |
lpapp | melonipoika: check xserver-xorg.inc | 06:24 |
melonipoika | i am using ti mcsdk, let me check what version of yocto it is absed | 06:25 |
lpapp | ${PN}-xvfb | 06:25 |
lpapp | so it is xserver-xorg-xvfb | 06:26 |
lpapp | at leat with oe-core | 06:26 |
lpapp | least* | 06:26 |
melonipoika | yeah, i tried adding xserver-xorg-xvfb to my local.conf | 06:26 |
lpapp | adding in what sense? | 06:26 |
lpapp | it should build by default, no? | 06:27 |
melonipoika | | * opkg_install_cmd: Cannot install package xserver-xorg-xvfb. | 06:27 |
melonipoika | that is the error i got | 06:27 |
melonipoika | i don't think so, the original image didn't ahve any x related stuff... | 06:28 |
lpapp | what image are you building? | 06:28 |
lpapp | is it custom or some-premade? | 06:28 |
melonipoika | the image is tidsk-server-rootfs-image.bb | 06:29 |
lpapp | sorry, I am afk for 20 minutes | 06:29 |
melonipoika | should i paste here the content? (17 lines) | 06:29 |
lpapp | ok, that I do not know | 06:29 |
lpapp | but if I use the default images | 06:29 |
lpapp | they work ok. | 06:29 |
lpapp | compare with the default ones | 06:29 |
melonipoika | ifik this is the only image that is supported in keystone II hw... | 06:29 |
melonipoika | ok, thanks | 06:30 |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 06:31 | |
*** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto | 06:51 | |
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC | 07:01 | |
*** volker <volker!~volker@host-80-81-19-29.customer.m-online.net> has quit IRC | 07:10 | |
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC | 07:13 | |
*** TuTizz <TuTizz!~TuTizz@46.18.96.158> has joined #yocto | 07:18 | |
*** tbn <tbn!~tbn@84.55.160.118> has joined #yocto | 07:21 | |
*** tbn is now known as Guest67693 | 07:21 | |
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto | 07:24 | |
lpapp | rburton: the cache stuff is calling for troubles | 07:26 |
lpapp | I was just debugging an issue because of that for hours. | 07:26 |
lpapp | once cache removed, it works. | 07:27 |
lpapp | rburton: was getting this continuously: http://paste.kde.org/~lpapp/p0bec71e5/ | 07:27 |
lpapp | by cache, I mean everything except the conf folder. | 07:28 |
*** sameo <sameo!~samuel@192.55.54.40> has joined #yocto | 07:33 | |
*** slaine <slaine!~slaine@84.203.137.218> has joined #yocto | 07:33 | |
lpapp | kergoth: hey? | 07:36 |
lpapp | http://paste.kde.org/~lpapp/p67427bfb/ | 07:39 |
lpapp | another libexec arch bug? | 07:39 |
lpapp | find /usr/local/arm-2009q1/ -name libexec | 07:40 |
lpapp | /usr/local/arm-2009q1/libexec | 07:40 |
lpapp | it is looking into the wrong directory again. | 07:40 |
*** ant_work <ant_work!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has joined #yocto | 07:50 | |
lpapp | rburton: oh, and we debugged that python stuff last time as well with -e for hours | 07:50 |
lpapp | that is exactly the reason why I prefer to clean cache. | 07:50 |
lpapp | there are no such issues then. | 07:50 |
*** bluelightning <bluelightning!~paul@83.217.123.106> has joined #yocto | 07:53 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 07:53 | |
lpapp | rburton: https://bugzilla.yoctoproject.org/show_bug.cgi?id=4922 | 07:54 |
yocti | Bug 4922: normal, Undecided, ---, richard.purdie, NEW , There is no clean option for bitbake or a separate util | 07:54 |
lpapp | kergoth: sgw_:https://bugzilla.yoctoproject.org/show_bug.cgi?id=4922 | 07:59 |
yocti | Bug 4922: normal, Undecided, ---, richard.purdie, NEW , There is no clean option for bitbake or a separate util | 07:59 |
lpapp | kergoth: sgw_:https://bugzilla.yoctoproject.org/show_bug.cgi?id=4923 * | 07:59 |
yocti | Bug 4923: normal, Undecided, ---, bogdan.a.marinescu, NEW , Cross-compilation issue with libexec when building for 32 bit host on arch 64. | 07:59 |
bluelightning | morning all | 08:00 |
lpapp | hi | 08:01 |
*** GunsNRose <GunsNRose!~GunsNRose@182.148.69.223> has joined #yocto | 08:02 | |
*** sakoman <sakoman!~steve@static-74-41-60-154.dsl1.pco.ca.frontiernet.net> has joined #yocto | 08:02 | |
*** tsjsieb <tsjsieb!~tsjsieb@5469C560.cm-12-2d.dynamic.ziggo.nl> has joined #yocto | 08:03 | |
lpapp | what is prefix usually in a bb recipe? | 08:08 |
lpapp | I mean where is it set? | 08:08 |
lpapp | I see it used in a meta-sourcery bb file, but it is not set right in there. | 08:09 |
lpapp | and I do not find it set anywhere inside meta-sourcery. | 08:09 |
*** mckoan|away is now known as mckoan | 08:11 | |
mckoan | good morning | 08:12 |
*** mihai <mihai!~mihai@80.97.15.150> has joined #yocto | 08:15 | |
*** GunsNRose_ <GunsNRose_!~GunsNRose@118.114.150.132> has joined #yocto | 08:17 | |
rburton | lpapp: default prefix is set in bitbake.conf, or your distro can override that | 08:18 |
lpapp | it is set to /usr | 08:18 |
lpapp | not sure that is correct for the cross-toolchain, really. | 08:18 |
lpapp | perhaps I am missing the sysroot | 08:18 |
lpapp | distro = layer, I believe | 08:20 |
lpapp | as it is probably not specific to a distro | 08:20 |
lpapp | as layers are not specific to distros | 08:20 |
*** GunsNRose <GunsNRose!~GunsNRose@182.148.69.223> has quit IRC | 08:21 | |
*** dzoe_ <dzoe_!joe@joe.cz> has quit IRC | 08:22 | |
*** dzoe_ <dzoe_!joe@pdpc/supporter/active/dzoe> has joined #yocto | 08:22 | |
*** dzoe_ is now known as dzoe | 08:22 | |
lpapp | rburton: shouldn't the meta-sourcery layer set the prefix to the cross-toolchain? | 08:26 |
lpapp | rburton: or is that the prefix for the installation? | 08:26 |
lpapp | I am slightly confused now. | 08:26 |
*** honschu_ <honschu_!~honschu@p549EAE8D.dip0.t-ipconnect.de> has joined #yocto | 08:27 | |
*** honschu_ <honschu_!~honschu@shackspace/j4fun> has joined #yocto | 08:27 | |
*** GunsNRose_ <GunsNRose_!~GunsNRose@118.114.150.132> has quit IRC | 08:30 | |
*** mihai <mihai!~mihai@80.97.15.150> has quit IRC | 08:30 | |
*** GunsNRose <GunsNRose!~GunsNRose@118.114.150.132> has joined #yocto | 08:30 | |
*** conditionzero <conditionzero!~Unknown@2001:6f8:12d9:13:1e4b:d6ff:fedb:207c> has joined #yocto | 08:30 | |
*** honschu <honschu!~honschu@shackspace/j4fun> has quit IRC | 08:31 | |
*** zeeblex <zeeblex!~apalalax@134.134.137.71> has joined #yocto | 08:32 | |
*** belen <belen!Adium@nat/intel/x-hkoebosgyhryaidf> has joined #yocto | 08:37 | |
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC | 08:38 | |
* lpapp is considering to open a bugreport about making shm optional | 08:46 | |
lpapp | it has been causing so much issues for several hours now. | 08:46 |
lpapp | and it is very hard to get it right. | 08:46 |
bluelightning | er, we can't do that | 08:46 |
bluelightning | python multiprocessing requires it | 08:46 |
lpapp | bluelightning: then you should not use such python instructions. | 08:46 |
lpapp | if any instruction needs that, that sucks huge balls. | 08:46 |
lpapp | that means, the language is fundamentally broken. | 08:47 |
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto | 08:47 | |
lpapp | because it gives no choice for IPC to you. | 08:47 |
lpapp | but I am fairly certain it is not the case. | 08:47 |
bluelightning | python multiprocessing is a well-accepted and widely used concurrency tool | 08:47 |
lpapp | which does not work apparently right ... | 08:48 |
lpapp | and got no help for several hours on #archlinux, #debian, #yocto | 08:48 |
lpapp | how to get it fed properly. | 08:48 |
lpapp | I tried everything now I had ideas. | 08:48 |
lpapp | so if it is this hassle, and so hard to get help, I would not consider it acceptable for everyone. | 08:48 |
lpapp | which brings back to optional. | 08:48 |
lpapp | pretty much no programs need that in my debian wheezy. | 08:49 |
lpapp | otherwise they would be broken. | 08:49 |
lpapp | bitbake is the first one. | 08:49 |
lpapp | so life can work without it. | 08:49 |
bluelightning | well, we cannot, sorry | 08:49 |
lpapp | yes, you can. | 08:49 |
bluelightning | I don't see why it should be so hard to ensure /dev/shm exists and has the correct permissions | 08:49 |
lpapp | it only means a different backend. | 08:49 |
lpapp | bluelightning: then why have you not spoken up for about a day? | 08:50 |
lpapp | the issue has been discussed here several times. | 08:50 |
lpapp | anyway, I am filing a bugreport. | 08:50 |
bluelightning | we have had several different concurrency mechanisms in bitbake over the years, and this one is the one that functions most efficiently and effectively | 08:50 |
lpapp | for _you_ | 08:50 |
lpapp | but not for many others users | 08:50 |
bluelightning | for the majority of users | 08:50 |
lpapp | so please do not demand non-functional stuff for users. | 08:50 |
lpapp | yeah, whatever. | 08:51 |
lpapp | bugtracker does not only exist for your top priority bugs | 08:51 |
bluelightning | you assume that your experience is mirrored by a large number of others; I can assure you that in my experience helping users it is not | 08:51 |
*** mihai <mihai!~mihai@80.97.15.150> has joined #yocto | 08:51 | |
lpapp | oh, so your perception is right? | 08:51 |
lpapp | but others' are not | 08:51 |
lpapp | nice joke. | 08:52 |
lpapp | many users who tried to help me (pro users, that is), could not help. | 08:52 |
rburton | lpapp: all you need is a tmpfs in the right place. | 08:52 |
bluelightning | my perception is based upon years of experience helping users to use the system | 08:52 |
lpapp | yeah, so let us get the next users with the very same issues who are forced for silly debian chroot to suck. | 08:52 |
lpapp | and go away from the project because it is not working. | 08:52 |
lpapp | that will be so beneficial for Yocto | 08:53 |
RP | lpapp: You are the first person who has ever complained that bitbake should not be using shm (and as a bitbake maintainer, I'd likely have seen such complaints) | 08:54 |
rburton | lpapp: if SHM is broken in your chroot, you'll have great trouble running a lot of software. fix your chroot and bitbake will work. | 08:54 |
lpapp | RP: you are free to help me to fix it. | 08:56 |
*** belen <belen!Adium@nat/intel/x-hkoebosgyhryaidf> has quit IRC | 08:56 | |
lpapp | I just do not have yet another day trying to fix it, honestly. | 08:56 |
lpapp | and I am very close to stepping away because pretty much there is no existing Yocto setup which actually works | 08:56 |
lpapp | I have been trying to make it work for a week in full time. | 08:56 |
rburton | lpapp: you've tried 1) an unsupported distro and 2) a broken chroot | 08:56 |
rburton | lpapp: *everyone else* in here is clearly using it fine | 08:57 |
lpapp | RP: and what you have seen does not mean there are no more. | 08:57 |
lpapp | https://bugzilla.yoctoproject.org/show_bug.cgi?id=4925 | 08:57 |
yocti | Bug 4925: normal, Undecided, ---, richard.purdie, NEW , Add an alternative backend for IPC communication | 08:57 |
rburton | lpapp: as you're running arch, try systemd-nspawn | 08:57 |
lpapp | it is totally irrelevant to systemd-nspawan | 08:57 |
lpapp | nspawn* | 08:57 |
lpapp | rburton: no software is broken in my chroot just as I wrote. | 08:58 |
rburton | lpapp: anything that uses SHM will be broken | 08:58 |
lpapp | the ones I actually use | 08:58 |
lpapp | rburton: please do not come with theoretical issues | 08:58 |
lpapp | we live in a practical world. | 08:58 |
lpapp | where we need to solve problems. | 08:58 |
rburton | lpapp: listen for a minute. your problem is that the chroot isn't correctly configured - specifically your /dev/shm is broken. systemd-nspawn will effectivly boot the guest and in that process, init /dev/shm | 08:58 |
rburton | that's the point, the joy, and reason for systemd-nspawn to live | 08:59 |
*** belen <belen!~Adium@134.134.139.70> has joined #yocto | 08:59 | |
rburton | chroots are *known* to have all sorts of fun problems as they don't actually boot | 08:59 |
lpapp | I am not sure how to put it clearly, | 08:59 |
lpapp | chroot *should* just work with proper bind mounts which I think I kinda have. | 09:00 |
lpapp | nspawn *would* probably have another issues on its own | 09:00 |
rburton | you clearly don't have the right mounts if the permissions are wrong | 09:00 |
lpapp | not to mention, I have a *lot* more experience with chroot. | 09:00 |
lpapp | it is "fun" to see how people argue against solution proposals, but they do not provide anything better. | 09:01 |
bluelightning | lpapp: you asked for help, we're giving you advice, if you ignore it then you're on your own | 09:02 |
rburton | i've proposed 1) let us help you fix your mounts or 2) try systemd-nspawn | 09:02 |
rburton | but now i'm going to have a run | 09:02 |
lpapp | rburton: 1) sorry, where? | 09:02 |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has left #yocto | 09:02 | |
lpapp | 2) Dropping what you have instead of fixing it is *not* a proposal. | 09:03 |
lpapp | it is a totally valid use case to use chroot for such things. | 09:03 |
*** belen <belen!~Adium@134.134.139.70> has quit IRC | 09:03 | |
lpapp | so, if you cannot help fixing the chroot stuff, please just implement an alternative backend when you get there. | 09:04 |
*** laur1 <laur1!~lau@192.198.151.43> has joined #yocto | 09:04 | |
*** romain_ <romain_!d96c30f9@gateway/web/freenode/ip.217.108.48.249> has joined #yocto | 09:04 | |
*** simon_b <simon_b!c06dbe58@gateway/web/freenode/ip.192.109.190.88> has joined #yocto | 09:14 | |
lpapp | bluelightning: what advice have you provided for fixing the shm mount? | 09:18 |
lpapp | and its writability. | 09:18 |
lpapp | I just went through the log, but I have not found anything. | 09:18 |
*** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has joined #yocto | 09:19 | |
bluelightning | lpapp: make sure it's mounted and you have write permissions there? | 09:20 |
lpapp | bluelightning: oh, really? | 09:23 |
ndec | lpapp: how did you mount it? | 09:23 |
lpapp | I would not have thought that. | 09:23 |
lpapp | bluelightning: the question is _how_. | 09:23 |
lpapp | we all know what the end result should be. | 09:23 |
lpapp | ndec: check the bugreport. | 09:23 |
bluelightning | lpapp: it's not really up to us how you set up your chroot environment | 09:25 |
ndec | lpapp: ok... can you tell me again which #BUG it is? | 09:25 |
ndec | it's lost in the huge irc backlog ;-) | 09:25 |
lpapp | ndec: 09:55 < yocti> Bug 4925: normal, Undecided, ---, richard.purdie, NEW , Add an alternative backend for IPC communication | 09:26 |
yocti | Bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=4925 normal, Undecided, ---, richard.purdie, NEW , Add an alternative backend for IPC communication | 09:26 |
lpapp | bluelightning: oh, it is not really up to make users' life easier? | 09:26 |
lpapp | to you* | 09:26 |
lpapp | that is a very disappointing mission statement. | 09:26 |
ndec | lpapp: you don't seem to mount /run/shm... | 09:27 |
*** shoragan <shoragan!~jlu@debian/developer/shoragan> has joined #yocto | 09:27 | |
ndec | or the bug report is wrong. | 09:27 |
lpapp | ndec: /run is mounted. | 09:27 |
bluelightning | lpapp: /run is not /run/shm | 09:28 |
ndec | what's not what i said . | 09:28 |
lpapp | it is | 09:28 |
lpapp | but even then, I tried this: mount --bind /dev/shm /media/wheezy/run/shm | 09:28 |
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC | 09:28 | |
lpapp | there is no point in mounting recursively, really. | 09:28 |
ndec | none on /run/shm type tmpfs (rw,nosuid,nodev) | 09:28 |
bluelightning | lpapp: I'm afraid there is | 09:28 |
ndec | and to be monone on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) | 09:28 |
ndec | none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) | 09:28 |
ndec | none on /run/shm type tmpfs (rw,nosuid,nodev) | 09:28 |
ndec | re complete | 09:28 |
ndec | oops.. to be more 'complete' that was. | 09:28 |
lpapp | why that will not work is simply because it is not bind mount. | 09:29 |
lpapp | see my command above please. | 09:29 |
ndec | that's from a working LXC container, where I can build OE. | 09:29 |
lpapp | the bugreport is not meant to be a chroot manual though | 09:29 |
lpapp | it is meant to be a feature extension for a better future for people having such issues | 09:30 |
lpapp | so I would not like to hijack it into chroot bugfixing. | 09:30 |
lpapp | that is why I did not provide all the details in there, just one of those. | 09:30 |
lpapp | added this information though | 09:31 |
lpapp | ndec: and it is 755 after that bind mount | 09:32 |
ndec | even if someone one day will accept to implement a new IPC .. which i doubt, that won't happen today. so you need to fix your chroot issue, should you want to make a build at some point. | 09:32 |
lpapp | and I cannot change that | 09:32 |
lpapp | I would not be so sure about that. | 09:32 |
ndec | so, i would agree 'more' on asking yocto to provide a 'manual' to setup a chroot. that seems more reasonnable to me. | 09:33 |
lpapp | but yes, obviously, it is a long term plan. | 09:33 |
lpapp | you cannot provide manual for each chroot/spawn host / guest combination ... | 09:33 |
lpapp | you would go haywire ... | 09:33 |
lpapp | so to me, that seems less reasonable. :) | 09:34 |
lpapp | bbiab | 09:35 |
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC | 09:36 | |
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto | 09:37 | |
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto | 09:37 | |
lpapp | not even Ubuntu 12.10 is supported. :( | 09:43 |
lpapp | WARNING: Host distribution "Ubuntu 12.10" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. | 09:43 |
bluelightning | lpapp: with which version now? | 09:43 |
lpapp | Request account | 09:45 |
lpapp | Your account request has successfully been sent and is now pending review. A confirmation email has been sent to your e-mail address. | 09:45 |
lpapp | I thought I could help with the wiki | 09:45 |
ndec | even danny seems to have 12.10 support, at least from git. | 09:48 |
lpapp | apparently, it is not simply a fire and help us | 09:59 |
lpapp | ndec: as dany a | 09:59 |
lpapp | as danny and dylan are fully broken for cross compilation | 09:59 |
lpapp | our best bet is denzil | 09:59 |
lpapp | which was not fully broken | 09:59 |
lpapp | the regression was not yet introduced in there. | 10:00 |
lpapp | and since we do not have shm alternative | 10:00 |
lpapp | and since I do not know how to make chroot work | 10:00 |
lpapp | I got an access to an ubuntu machine over ssh. | 10:00 |
bluelightning | lpapp: sorry but it's completely incorrect to say "danny and dylan are fully broken for cross compilation" | 10:00 |
lpapp | oh, really, so I am not having any issues with it then? | 10:01 |
lpapp | I just imagine them? | 10:01 |
bluelightning | no, you imply that it is not capable of cross-compilation; the fact of the matter is many, people use those versions daily to cross-compile | 10:01 |
lpapp | alongsidfe other people who can reproduce those issues? | 10:01 |
lpapp | I am not referring to the "many people doing cross-compilation" | 10:01 |
bluelightning | you've had problems specifically with external toolchains, that doesn't mean you can't cross-compile | 10:02 |
lpapp | let us not play word games. | 10:02 |
lpapp | I am clearly referring for my scenario. | 10:02 |
lpapp | to* | 10:02 |
lpapp | yes, it means | 10:02 |
lpapp | I also had problems with internal toolchains | 10:02 |
lpapp | I even wrote them here. | 10:02 |
lpapp | for me, there is no any setup where Yocto would work so far. | 10:02 |
lpapp | with cross-compilation. | 10:02 |
lpapp | sorry for putting it this way, but Yocto is immature for me at this point. | 10:04 |
lpapp | and for those who can reproduce the issues. | 10:04 |
lpapp | hopefully, this will improve over time. | 10:04 |
bluelightning | I'll make it clear as I have done so before, you make things harder for yourself by using host setups that aren't well-tested | 10:05 |
bluelightning | before you say anything I know you have had other problems | 10:05 |
bluelightning | but at least half of the major problems you have had have been due to the host environment you have chosen | 10:06 |
lpapp | huh, not? | 10:06 |
lpapp | actually, there has not been any arch specific issue so far that I can recall. | 10:06 |
lpapp | not in master HEAD that is. | 10:06 |
*** volker <volker!~quassel@host-80-81-19-29.customer.m-online.net> has joined #yocto | 10:07 | |
lpapp | but feel free to back your statement about this as it is unclear for me, the arch user.s | 10:07 |
lpapp | user.* | 10:07 |
lpapp | could you please show me _any_ issue that was arch specific? | 10:08 |
bluelightning | how about the issue you had with host gcc 4.8? I'm still unclear on how you got that given that the patch is already in dylan for that one | 10:08 |
lpapp | I did not have any of that? | 10:09 |
lpapp | since I am not using 4.8? | 10:09 |
lpapp | we are using gcc 4.3.3 ? | 10:09 |
lpapp | what CS ships ? | 10:09 |
ndec | you are confused between host and target gcc | 10:10 |
lpapp | perhaps you are confusing me with net147? | 10:10 |
lpapp | ndec: no, not at all | 10:10 |
ndec | yes. you are. | 10:10 |
lpapp | ndec: host toolchain for building for the target *is* from code sourcery | 10:10 |
lpapp | it would work even if there was no any toolchain installed on my arch for native x86 builds. | 10:10 |
ndec | bluelightning told you about host gcc 4.8, and you answer you use gcc 4.3.3, which is the target gcc. | 10:10 |
lpapp | no | 10:10 |
bluelightning | lpapp: I'm referring to when you switched to the internal toolchain | 10:10 |
lpapp | that is where you are wrong. | 10:10 |
lpapp | 4.3.3 is *explicitly* not the target gcc | 10:10 |
lpapp | it is the x86 ELF 32 binary for the *host*. | 10:11 |
bluelightning | lpapp: and no matter what, for building native tools you *are* using your native gcc 4.8 | 10:11 |
lpapp | you seem to not understand how this works. | 10:11 |
ndec | yes, it is... | 10:11 |
ndec | well, let me have some doubts about that... | 10:11 |
lpapp | bluelightning: internal toolchain has never been a plan to be used. | 10:11 |
lpapp | bluelightning: as I stated clearly, it is a complete no go | 10:11 |
bluelightning | sigh | 10:11 |
lpapp | according to everyone here. | 10:12 |
lpapp | I made a test for out of the curiosity, but I could not care less about it. | 10:12 |
lpapp | so again, what issue can present for arch for the intended goal? | 10:13 |
lpapp | (to get back on track) | 10:13 |
lpapp | mind pasting a bugreport or irc note? | 10:13 |
lpapp | or even email thread. | 10:13 |
* ndec lunch... | 10:13 | |
bluelightning | lpapp: I was including your recent attempts to use a debian chroot without completely setting it up | 10:14 |
lpapp | bluelightning: that is also not an intentional final goal. | 10:14 |
lpapp | the final goal is to get 4.3.3 from CS and Arch 64 bit host working. | 10:15 |
lpapp | I do not see any arch specific issue for that. | 10:15 |
lpapp | and I do not think the chroot is arch specific issue either | 10:15 |
lpapp | I would have the same trouble on other "supported" hosts, as well. | 10:15 |
lpapp | I just do not see what arch specific issue happened in here for arm2009q1 | 10:15 |
lpapp | perhaps, you are right, I just need to understand. | 10:16 |
lpapp | to me, all the issues look generic. | 10:16 |
*** belen <belen!~Adium@134.134.139.70> has joined #yocto | 10:17 | |
bluelightning | my original point was, cross-compilation *does* work | 10:18 |
bluelightning | if it did not nobody would use our system | 10:18 |
bluelightning | and many successfully do | 10:18 |
bluelightning | we know there is a problem with external toolchain support out of the box with recent versions | 10:18 |
bluelightning | and there are folks working on that problem | 10:19 |
bluelightning | in the mean time, while I'm in here arguing with you I'm not getting any actual work done | 10:20 |
lpapp | actually CS cross-compilation does not work | 10:21 |
lpapp | and everyone could reproduce the issue. | 10:21 |
lpapp | not with oe-core which belongs to Yocto. | 10:21 |
lpapp | but I had more problems than that, correct. | 10:22 |
lpapp | none of it is Arch specific though. | 10:22 |
lpapp | those are general issues. | 10:22 |
*** GunsNRose <GunsNRose!~GunsNRose@118.114.150.132> has quit IRC | 10:22 | |
lpapp | bluelightning: the problem is that you should not argue. | 10:22 |
lpapp | you claim me being wrong, even though the bugreports are accepted by the decision makers, so probably not, and then you wonder if I try to clarify my statement in more details. | 10:23 |
bluelightning | when someone is potentially misleading other people about the state of our project, sure I'll argue | 10:23 |
lpapp | facts are speaking for themselves. | 10:24 |
lpapp | no need to "mislead". | 10:24 |
lpapp | and that is the impression from the comments on my blog post as well. | 10:24 |
lpapp | it is not just me thinking that Yocto is not yet mature as it is. | 10:25 |
lpapp | for embeddded cross-compilation. | 10:25 |
lpapp | it is not just my opinion | 10:25 |
lpapp | and it is possibly not just me filing the bugreports, and spending a lot of time with improving things. | 10:25 |
*** e8johan <e8johan!~quassel@94.234.170.85> has joined #yocto | 10:25 | |
*** volker <volker!~quassel@host-80-81-19-29.customer.m-online.net> has quit IRC | 10:28 | |
ant_work | amen | 10:29 |
lpapp | just in case: https://bugzilla.yoctoproject.org/show_bug.cgi?id=4927 | 10:30 |
yocti | Bug 4927: normal, Undecided, ---, saul.wold, NEW , Make Archlinux a supported host distribution | 10:30 |
*** volker <volker!~quassel@host-80-81-19-29.customer.m-online.net> has joined #yocto | 10:30 | |
RP | lpapp: Remember that the people trying to help you *are* some of the decision makers on this project. Filing bug reports is good, I totally encourage that however it doesn't mean that they are verified as an issue or that people can find the time/resources to work on fixing them. I agree in an ideal world we should however the world is imperfect | 10:31 |
lpapp | RP: they were verified as issues yesterday. | 10:31 |
lpapp | RP: people were spending a day with one of them to be fixed. | 10:32 |
lpapp | it is just that critical... | 10:32 |
lpapp | currently 4923 is sitting on my as a blocker for arch | 10:34 |
lpapp | otherwise I would not need to use Ubuntu, or even Debian. | 10:34 |
*** mike23434 <mike23434!53eead1d@gateway/web/freenode/ip.83.238.173.29> has joined #yocto | 10:36 | |
*** ChanServ sets mode: +o RP | 10:40 | |
RP | Welcome to the Yocto Project | Learn more: http://www.yoctoproject.org | Join the community: http://www.yoctoproject.org/community | Yocto 1.4 (dylan) Released! http://www.yoctoproject.org/download | Channel logs available at https://www.yoctoproject.org/irc/ | 10:40 |
*** RP changes topic to "Welcome to the Yocto Project | Learn more: http://www.yoctoproject.org | Join the community: http://www.yoctoproject.org/community | Yocto 1.4 (dylan) Released! http://www.yoctoproject.org/download | Channel logs available at https://www.yoctoproject.org/irc/" | 10:41 | |
lpapp | RP: thanks | 10:43 |
lpapp | I requested this a few days ago to be compliant with the freenode rules. | 10:43 |
lpapp | nice to see it happening. | 10:43 |
bluelightning | lpapp: the delay was because he's on holiday and he's the only one with the ability to change it | 10:44 |
lpapp | bluelightning: the log could have been blocked in the meantime. | 10:44 |
lpapp | bluelightning: but it is solved now anyway | 10:44 |
bluelightning | lpapp: I'll point you to the freenode connect message which clearly states "you may wish to keep a notice in the topic" not "you must" | 10:46 |
bluelightning | lpapp: not that it's not a good idea, but let's be clear about what's stated | 10:46 |
lpapp | bluelightning: you might wanna contact #freenode then. | 10:49 |
lpapp | I have not seen a channel yet the last 10+ years who have not followed this btw. | 10:50 |
lpapp | it is not even ethical to publish private information about people without their agreement. | 10:51 |
bluelightning | this is not private information | 10:51 |
RP | regardless, the link is in the topic now | 10:52 |
bluelightning | right, and we have a pointer on our IRC page on the website | 10:52 |
lpapp | If you're publishing logs on an ongoing basis, your channel topic should reflect that fact. Be sure to provide a way for users to make comments without logging, | 10:52 |
lpapp | http://freenode.net/channel_guidelines.shtml | 10:52 |
lpapp | "should" | 10:52 |
lpapp | "Be sure" | 10:52 |
lpapp | etc | 10:52 |
lpapp | RP: yes, thanks. | 10:53 |
*** laur1 <laur1!~lau@192.198.151.43> has quit IRC | 10:58 | |
*** swex_ <swex_!~swex@88.210.25.36> has joined #yocto | 11:03 | |
*** swex <swex!~swex@178.17.201.225> has quit IRC | 11:03 | |
*** e8johan <e8johan!~quassel@94.234.170.85> has quit IRC | 11:09 | |
ant_work | just FYI there is another log service at http://logs.nslu2-linux.org/livelogs/yocto/ | 11:10 |
ant_work | this covers #oe as well | 11:10 |
lpapp | ant_work: good catch | 11:11 |
lpapp | let me raise the issue there. | 11:11 |
*** volker <volker!~quassel@host-80-81-19-29.customer.m-online.net> has quit IRC | 11:11 | |
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has quit IRC | 11:13 | |
ant_work | * Topic for #mtd is: fish | 11:17 |
ant_work | * Topic for #mtd set by ChanServ!services@services.oftc.net at Thu Mar 21 19:21:28 2013 | 11:17 |
ant_work | I don't dare bother them ;) | 11:18 |
*** zeeblex <zeeblex!~apalalax@134.134.137.71> has quit IRC | 11:18 | |
bluelightning | heh | 11:18 |
ant_work | (is not on freenode) | 11:18 |
*** zeeblex <zeeblex!~apalalax@134.134.137.71> has joined #yocto | 11:19 | |
*** laur <laur!lau@nat/intel/x-ouppzaobsewphxqq> has joined #yocto | 11:27 | |
lpapp | right, so tmp does not contain the packagers per layer... | 11:31 |
lpapp | that makes it very hard to verify the build results. | 11:31 |
ant_work | lpapp: long long ago there was a wiki page like that | 11:34 |
ant_work | http://www.openembedded.org/wiki/OEandYourDistro | 11:34 |
ant_work | but it has happened that most tools are now built as -native packages | 11:34 |
*** smartin_ <smartin_!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto | 11:34 | |
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC | 11:35 | |
*** honschu_ is now known as honschu | 11:35 | |
lpapp | not sure how that is related to my comment, | 11:35 |
lpapp | I would like to verify the layers one by one. | 11:36 |
ant_work | is about your generic Arch stuff | 11:36 |
lpapp | ? | 11:36 |
lpapp | I am more confused now. :) | 11:36 |
ant_work | take the time to open the link I posted ;) | 11:36 |
lpapp | I did, but it is actually fully outdated. | 11:37 |
lpapp | so did not bother to spend my time with it. | 11:37 |
ant_work | sure, any similar page would be inesorably out of date | 11:37 |
*** belen <belen!~Adium@134.134.139.70> has quit IRC | 11:37 | |
*** Stygia <Stygia!~gmpsaifi@0904ds6-noe.0.fullrate.dk> has joined #yocto | 11:38 | |
lpapp | or is Yocto only supposed to build a distro image? | 11:38 |
lpapp | where can I find it? | 11:38 |
ant_work | the packages are split per ARCH | 11:39 |
ant_work | not per layer | 11:39 |
lpapp | those are not exclusive ... | 11:39 |
lpapp | -> /tmp/deploy seems to be the right stuff. | 11:40 |
ant_work | that's only for images/bootloaders | 11:40 |
ant_work | the packages are i.e. under /ipk | 11:40 |
*** igrigorx <igrigorx!6d644604@gateway/web/freenode/ip.109.100.70.4> has joined #yocto | 11:45 | |
*** igrigorx <igrigorx!6d644604@gateway/web/freenode/ip.109.100.70.4> has quit IRC | 11:51 | |
*** Net147 <Net147!~Net147@60-242-179-244.static.tpgi.com.au> has joined #yocto | 11:53 | |
*** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has quit IRC | 11:54 | |
*** zerus <zerus!~epetmab@90-224-44-236-no67.tbcn.telia.com> has joined #yocto | 11:54 | |
*** joeythesaint <joeythesaint!~jjm@206-248-190-39.dsl.teksavvy.com> has joined #yocto | 11:58 | |
*** GunsNRose <GunsNRose!~GunsNRose@182.139.169.64> has joined #yocto | 12:03 | |
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has joined #yocto | 12:10 | |
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto | 12:15 | |
*** zerus <zerus!~epetmab@90-224-44-236-no67.tbcn.telia.com> has quit IRC | 12:16 | |
*** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has joined #yocto | 12:18 | |
*** belen <belen!~Adium@134.134.139.70> has joined #yocto | 12:20 | |
*** jackmitchell <jackmitchell!~Thunderbi@host217-34-104-101.in-addr.btopenworld.com> has quit IRC | 12:23 | |
* wmat gets more coffee :/ | 12:32 | |
*** Stygia <Stygia!~gmpsaifi@0904ds6-noe.0.fullrate.dk> has quit IRC | 12:34 | |
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto | 12:38 | |
*** forcev <forcev!~quassel@wafaa.eu> has quit IRC | 12:40 | |
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto | 12:44 | |
*** frank <frank!~frank@118.186.200.116> has joined #yocto | 12:50 | |
*** frank <frank!~frank@118.186.200.116> has quit IRC | 12:56 | |
-YoctoAutoBuilder- build #39 of buildtools is complete: Failure [failed Building Images Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org:8011/builders/buildtools/builds/39 | 13:01 | |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-zgisxyzprsayfldl> has joined #yocto | 13:02 | |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-fzhjnvjqxfmuxntx> has joined #yocto | 13:04 | |
*** fenrig <fenrig!55eac3e5@gateway/web/freenode/ip.85.234.195.229> has joined #yocto | 13:11 | |
fenrig | Hi, I'm having trouble with imx53 (freescale) and having a /dev/fb0 | 13:11 |
*** behanw <behanw!~behanw@216-58-123-51.cpe.distributel.net> has joined #yocto | 13:18 | |
mike23434 | witch recipe contains python libxml2 module? "python-lxml" don't work for me. I can't cross compile mesa because it requires it. | 13:19 |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-fzhjnvjqxfmuxntx> has quit IRC | 13:19 | |
-YoctoAutoBuilder- build #226 of nightly-non-gpl3 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-non-gpl3/builds/226 | 13:19 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 13:19 | |
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has quit IRC | 13:22 | |
-YoctoAutoBuilder- build #220 of nightly-x86-64-lsb is complete: Failure [failed Building Images] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-64-lsb/builds/220 | 13:22 | |
bluelightning | mike23434: hmm, our mesa recipes in OE-Core don't need python-lxml to build AFAIK | 13:22 |
mike23434 | I'm not using OE-Core mesa recipes, I want to cross compile upstream mesa+etnaviv driver (vivante graphics in imx6) | 13:24 |
bluelightning | mike23434: ah ok, so it is extra functionality you're enabling that needs python libxml2 bindings? | 13:25 |
*** zeeblex <zeeblex!~apalalax@134.134.137.71> has left #yocto | 13:26 | |
*** __frank_ <__frank_!~frank@1.202.252.122> has quit IRC | 13:27 | |
*** __frank_ <__frank_!~frank@1.202.252.122> has joined #yocto | 13:28 | |
mike23434 | glapi/gen regires libxml2, libxml2-python is mesa depency from january 2013 | 13:28 |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 13:32 | |
bluelightning | mike23434: hmm, looks like libxml2-python and lxml are two different things, I guess that explains why python-lxml doesn't work | 13:32 |
bluelightning | mike23434: I think you may have to write a new recipe for that, but presumably you could use the python-lxml recipe as a starting point | 13:32 |
mike23434 | great :) how do you build mesa witchout it? | 13:36 |
*** GunsNRose <GunsNRose!~GunsNRose@182.139.169.64> has quit IRC | 13:37 | |
lpapp | is it possible to get an image generated rather many small stuff? | 13:38 |
ndec | lpapp: what is a 'small stuff'? | 13:38 |
lpapp | package | 13:38 |
lpapp | sorry, I got off for two hours | 13:39 |
lpapp | we had a barbacue party. :-P | 13:39 |
ndec | the image is generated at the end of the build, when all packages are built. | 13:39 |
lpapp | ok, so there are many small packages _and_ also the image? | 13:39 |
ndec | yep. | 13:39 |
lpapp | fair enough | 13:39 |
ndec | in tmp/deploy/images | 13:40 |
ndec | you have to 'bitbake' an image, of course. | 13:40 |
ndec | image are .bb files too, which has a different 'task set', and include a do_rootfs() task. | 13:40 |
lpapp | core-image-minimal | 13:41 |
ndec | that's one of them. yes. | 13:41 |
mike23434 | bluelightning: can i put it to some common place that nobody has to do it again after i create new recipe? | 13:42 |
*** hollisb <hollisb!~hollisb@c-67-169-221-181.hsd1.or.comcast.net> has joined #yocto | 13:43 | |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-bpqxjakwberemvgu> has joined #yocto | 13:44 | |
lpapp | is the "tmp" layout documented somewhere? | 13:45 |
bluelightning | mike23434: certainly, it would be great if you could add it into the meta-oe layer and send a patch to openembedded-devel@openembedded.org that does that | 13:46 |
ndec | lpapp: http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#structure-build | 13:46 |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-bpqxjakwberemvgu> has quit IRC | 13:49 | |
*** volker <volker!~quassel@host-80-81-19-29.customer.m-online.net> has joined #yocto | 13:55 | |
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC | 13:56 | |
*** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has joined #yocto | 14:05 | |
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto | 14:08 | |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-fmsgmynwqumvjxxs> has joined #yocto | 14:13 | |
*** GunsNRose <GunsNRose!~GunsNRose@182.139.169.64> has joined #yocto | 14:17 | |
lpapp | ndec: I do not find u-boot.bin inside the /tmp folder. How can I debug it why not? | 14:17 |
lpapp | run bitbake on that particular package only? | 14:17 |
ndec | lpapp: does your machine specify that it needs uboot? | 14:17 |
lpapp | ndec: ? | 14:18 |
lpapp | shouldn't all the recipes be built by default? | 14:18 |
ndec | bitbake only builds what it is asked to build. | 14:18 |
ndec | define 'all'? | 14:19 |
lpapp | all means all | 14:19 |
lpapp | cannot explain more | 14:19 |
lpapp | all the .bb stuff in every layer | 14:19 |
lpapp | that belongs to a particular image. | 14:20 |
lpapp | I thought u-boot would be included in core-image-minimal? | 14:20 |
*** tsjsieb <tsjsieb!~tsjsieb@5469C560.cm-12-2d.dynamic.ziggo.nl> has quit IRC | 14:23 | |
ndec | lpapp: u-boot is a machine specific param. some machine don't need it. | 14:26 |
-YoctoAutoBuilder- build #103 of nightly-qa-systemd is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-qa-systemd/builds/103 | 14:26 | |
bluelightning | lpapp: your machine config should do EXTRA_IMAGEDEPENDS += "u-boot" | 14:26 |
bluelightning | lpapp: this is what meta-yocto/conf/machine/* do | 14:27 |
lpapp | bluelightning: also x-load, I believe. | 14:27 |
*** Corneliu <Corneliu!c0c69724@gateway/web/freenode/ip.192.198.151.36> has joined #yocto | 14:27 | |
bluelightning | lpapp: in the case of beagleboard, yes; and if that's valid for your board, that too | 14:28 |
ant_work | probably MACHINE_ESSENTIAL_EXTRA_RDEPENDS | 14:28 |
bluelightning | ant_work: no, EXTRA_IMAGEDEPENDS because it's not to be installed in the image, just built alongside it | 14:28 |
ant_work | the policies are in the manual | 14:28 |
ant_work | sorry, I ssaw uEnv.txt is installed like this | 14:29 |
ant_work | I meant target part | 14:29 |
ant_work | anyway it's all in the FM | 14:29 |
*** fitzsim <fitzsim!~user@nat/cisco/x-ioyofluolunadyzh> has joined #yocto | 14:30 | |
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has joined #yocto | 14:30 | |
*** Corneliu <Corneliu!c0c69724@gateway/web/freenode/ip.192.198.151.36> has quit IRC | 14:31 | |
*** eren <eren!~eren@unaffiliated/eren> has quit IRC | 14:36 | |
*** mckoan is now known as mckoan|away | 14:37 | |
*** joshkurland <joshkurland!6b00909c@gateway/web/freenode/ip.107.0.144.156> has joined #yocto | 14:42 | |
*** zeddii <zeddii!~ddez@128.224.252.2> has joined #yocto | 14:46 | |
*** Umeaboy <Umeaboy!~Umeaboy@213-21-78-12.customer.t3.se> has joined #yocto | 14:47 | |
*** GunsNRose <GunsNRose!~GunsNRose@182.139.169.64> has quit IRC | 14:47 | |
*** simon_b <simon_b!c06dbe58@gateway/web/freenode/ip.192.109.190.88> has quit IRC | 14:47 | |
*** GunsNRose <GunsNRose!~GunsNRose@182.139.169.64> has joined #yocto | 14:48 | |
*** fenrig <fenrig!55eac3e5@gateway/web/freenode/ip.85.234.195.229> has quit IRC | 14:52 | |
lpapp | is it enough to just rebuild? | 14:52 |
lpapp | after uncommenting the EXTRA_IMAGEDEPENDS line? | 14:52 |
lpapp | I mean without deleting anything. | 14:53 |
lpapp | will I get the u-boot.bin stuff? | 14:53 |
*** mike23434 <mike23434!53eead1d@gateway/web/freenode/ip.83.238.173.29> has quit IRC | 14:53 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 15:00 | |
*** davest <davest!~Adium@134.134.137.73> has joined #yocto | 15:01 | |
lpapp | bluelightning: ndec ^ | 15:03 |
ndec | i never delete everything | 15:04 |
lpapp | ERROR: Nothing PROVIDES 'u-boot' | 15:06 |
lpapp | ERROR: u-boot was skipped: because UBOOT_MACHINE is not set | 15:06 |
lpapp | ERROR: u-boot was skipped: because UBOOT_MACHINE is not set | 15:06 |
lpapp | ERROR: u-boot was skipped: because UBOOT_MACHINE is not set | 15:06 |
lpapp | ERROR: u-boot was skipped: because UBOOT_MACHINE is not set | 15:06 |
lpapp | hmm, apparently, I would need to set that, too. | 15:06 |
ndec | yep | 15:07 |
lpapp | ERROR: Required build target 'core-image-minimal' has no buildable providers. | 15:07 |
lpapp | Missing or unbuildable dependency chain was: ['core-image-minimal', 'u-boot'] | 15:07 |
lpapp | bluelightning: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf has no machine ... | 15:08 |
lpapp | I figured out the meta-sourcery issue | 15:09 |
ndec | it's a DISTRO layer. | 15:09 |
lpapp | silly meta-sourcery is demanding an empty folder | 15:09 |
ndec | meta-yocto. | 15:09 |
lpapp | which is not present for me as we use git | 15:09 |
lpapp | and git does not track empty folders | 15:09 |
bluelightning | lpapp: my mistake, meta-yocto-bsp/conf/machine/* | 15:10 |
lpapp | why on earth does CS ship an empty folder :D :D | 15:10 |
lpapp | bluelightning: yeah, I just grepped in the root, and that helped to figure out meta-yocto-bsp | 15:10 |
bluelightning | lpapp: re your earlier question, no need to delete anything, no | 15:10 |
lpapp | https://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html | 15:11 |
lpapp | it does not document UBOOT_MACHINE ... | 15:11 |
lpapp | nor does the reference guide. | 15:11 |
*** ant_work <ant_work!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has quit IRC | 15:12 | |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-fmsgmynwqumvjxxs> has quit IRC | 15:12 | |
bluelightning | lpapp: we can't really be expected to document every possible bootloader in the BSP guide | 15:12 |
lpapp | looks like a bugreport | 15:12 |
lpapp | bluelightning: the variable could be defined! | 15:12 |
*** Net147 <Net147!~Net147@60-242-179-244.static.tpgi.com.au> has quit IRC | 15:13 | |
lpapp | https://bugzilla.yoctoproject.org/show_bug.cgi?id=4928 | 15:14 |
yocti | Bug 4928: normal, Undecided, ---, saul.wold, NEW , No documentation for UBOOT_MACHINE | 15:14 |
*** sameo <sameo!~samuel@192.55.54.40> has quit IRC | 15:17 | |
-YoctoAutoBuilder- build #223 of nightly-x86-64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-64/builds/223 | 15:17 | |
*** ynezz <ynezz!ynezz@ibawizard.net> has quit IRC | 15:17 | |
Sput | lpapp: btw, several developers here use Yocto on Archlinux just fine. and on Gentoo, Debian, SuSE and kubuntu... | 15:17 |
lpapp | Sput: me and a few others are not those developers though. | 15:18 |
lpapp | bluelightning: what should I put into UBOOT_MACHINE? | 15:18 |
*** ynezz <ynezz!ynezz@ibawizard.net> has joined #yocto | 15:18 | |
Sput | lpapp: well, just mentioning it because in your blog you mentioned it doesn't work and resort to a chroot instead. but it's definitely possible... | 15:20 |
lpapp | Sput: if it is definitely possible, let me know how. | 15:21 |
bluelightning | lpapp: looking at the recipe, it's whatever you would specify as the machine config on the u-boot make command line | 15:21 |
lpapp | it just does not work for us. | 15:22 |
lpapp | Sput: and people could reproduce issues following my instructions. | 15:22 |
Sput | weird. only issue I am aware of that happened here was that gcc 4.8 on the Arch host couldn't build gcc 4.7 on target, but that was fixed afaik | 15:22 |
Sput | and sometimes you need to install some -native packages because the host tools are too new (bibtex-native comes to mind) | 15:23 |
Sput | not bibtex, what was it called? | 15:23 |
*** ynezz <ynezz!ynezz@ibawizard.net> has quit IRC | 15:23 | |
*** ynezz <ynezz!ynezz@ibawizard.net> has joined #yocto | 15:24 | |
ndec | Sput: lpapp initially was using denzil (or danny). which might not have the most recent fixes from master. | 15:24 |
Sput | docbook-native? | 15:24 |
ndec | it probably gets harder and harder to use Arch for stable OE releases, as time pass. | 15:24 |
lpapp | Sput: as I wrote in my posts implicitly, we do not use 4.8 | 15:24 |
lpapp | and we do not do native builds. | 15:24 |
lpapp | that is kinda the crucial part of the post, really. :) | 15:25 |
Sput | well, that might be true (but that's probably also true for other distros) | 15:25 |
Sput | lpapp: install native packages so Yocto has proper versions | 15:25 |
ndec | lpapp: i am sorry.. but you are still confused by native vs host vs target... | 15:25 |
Sput | no reason not to do it to make things work :) | 15:25 |
lpapp | Sput: what do you mean? | 15:25 |
ndec | Sput: sure... but it depends if you want to use OE, or fix it ;-) | 15:25 |
lpapp | ndec: dude, I have been developing for embedded for years | 15:25 |
lpapp | you presented yesterday the confusion about native vs. internal. | 15:26 |
Sput | -native packages go into the native sysroot. so if your host docbook or whatever it was is too new, you can still install the older version into the native sysroot, so Yocto can useit. | 15:26 |
ndec | i have no doubt. but you are confused about these terms in OE. | 15:26 |
lpapp | nope | 15:26 |
lpapp | usually people do native builds on arch | 15:26 |
lpapp | i.e. for x86 or x86_64 | 15:26 |
lpapp | not arm, whatsoever. | 15:26 |
lpapp | and that is exactly what I meant. | 15:26 |
lpapp | so for a very simple scenario it may work. | 15:27 |
lpapp | but we are kinda ... building a next generation stuff with bleeding edge technology. | 15:27 |
Sput | so are we. which is why we use the newest poky, actually | 15:27 |
Sput | and have contemporary distros and not some LTS stuff :) | 15:27 |
lpapp | Sput: that is the other thing, we do not use the newest poky. | 15:28 |
lpapp | we already have a technology in place. | 15:28 |
lpapp | as you may know, switching core components of the stack is not 2 pounds. | 15:28 |
*** ynezz <ynezz!ynezz@ibawizard.net> has joined #yocto | 15:28 | |
Sput | it's not so much next generation bleeding edge then :) | 15:29 |
lpapp | bluelightning: right, thanks. | 15:29 |
lpapp | bluelightning: make foo -> foo goes to UBOOT_MACHINE | 15:29 |
lpapp | bluelightning: so it is probably doing MAKE $UBOOT_MACHINE in the background then. | 15:29 |
lpapp | make* | 15:29 |
*** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 15:29 | |
lpapp | Sput: it is. | 15:29 |
lpapp | no one has done anything yet as such. | 15:29 |
lpapp | and we are the number one in this industry as far as I can tell. | 15:29 |
bluelightning | lpapp: that's effectively what it does yes | 15:29 |
lpapp | hope we can keep that position. :-) | 15:30 |
lpapp | all my energy goes into that. | 15:30 |
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 15:31 | |
Sput | well, dylan fixed lots of issues for us, so you might want to consider an upgrade nonetheless | 15:31 |
lpapp | not for now, no. | 15:32 |
lpapp | meta-sourcery is currently broken. | 15:32 |
lpapp | and it has been blocking me. | 15:32 |
lpapp | it requires empty folders for reading, etc. :) | 15:32 |
lpapp | funny, really. | 15:32 |
lpapp | it has to become mature before we will switch to it. | 15:32 |
lpapp | what would be more worthy is the toolchain upgrade. | 15:32 |
lpapp | to get C++11/C++14 features | 15:33 |
Sput | we also appreciated more or less proper systemd support | 15:33 |
lpapp | bluelightning: do we need to specify the enty point and load address, too? | 15:33 |
lpapp | entry* | 15:33 |
lpapp | bluelightning: ah, you meant this, ../meta/recipes-bsp/u-boot/u-boot.inc:43: oe_runmake ${UBOOT_MACHINE} | 15:34 |
bluelightning | lpapp: I have limited experience with u-boot, but based on other machine configs, probably yes | 15:35 |
lpapp | bluelightning: really strange. | 15:36 |
lpapp | because it is not necessary for building u-boot separately. | 15:36 |
lpapp | it is only necessary for things like openocd. | 15:37 |
lpapp | or when you update it over tftp. | 15:37 |
lpapp | perhaps it is possible to hard code the address into u-boot | 15:37 |
lpapp | which then cannot be changed later. | 15:37 |
lpapp | which might be just an optional feature if you otherwise plan to specify that separelty at flashing/updating time. | 15:37 |
bluelightning | not sure I'm afraid | 15:37 |
*** joshkurland <joshkurland!6b00909c@gateway/web/freenode/ip.107.0.144.156> has quit IRC | 15:37 | |
*** TuTizz <TuTizz!~TuTizz@46.18.96.158> has quit IRC | 15:38 | |
*** Guest67693 <Guest67693!~tbn@84.55.160.118> has quit IRC | 15:39 | |
*** TuTizz <TuTizz!~TuTizz@46.18.96.158> has joined #yocto | 15:39 | |
*** darknighte_znc is now known as darknighte | 15:40 | |
lpapp | bluelightning: it is ok | 15:41 |
*** Umeaboy <Umeaboy!~Umeaboy@213-21-78-12.customer.t3.se> has quit IRC | 15:41 | |
*** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC | 15:41 | |
lpapp | Sput: btw, the issues are not arch related. | 15:42 |
lpapp | there are general immatureness. | 15:42 |
lpapp | they* | 15:42 |
lpapp | but since I am now involved in full-time with fixing it for myself. | 15:42 |
bluelightning | I think you go too far with accusations of immaturity | 15:42 |
lpapp | It might be easier to move forward on this front. | 15:42 |
Sput | oh, yes, there are many issues (but many have been fixed in the past two poky releases, too), not disputing that | 15:42 |
Sput | I was just referring to your claim that Archlinux is the problem, which it isn't. | 15:42 |
lpapp | they are the issues with poky master HEAD fwiw | 15:42 |
lpapp | and meta-sourcery master | 15:43 |
lpapp | Sput: the problem is that with archlinux, they do not support it. | 15:43 |
seebs | One thing I like to do when I need help from people who are familiar with a given project is use terms with strong negative connotations a lot, because people who feel insulted are much more likely to be cooperative and helpful. | 15:43 |
lpapp | not even a single configuration. | 15:43 |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-nlwtupnnxapzfsaf> has joined #yocto | 15:43 | |
Sput | who cares about official support for any given distro? we're engineers, we can solve that | 15:44 |
lpapp | Sput: it is all voluntary work if there are issues which is not a reliable solution for a company. | 15:44 |
Sput | for real Yocto issues, I've found the people in this channel always very helpful | 15:44 |
lpapp | Sput: many companies including us, of course. | 15:44 |
lpapp | it is not about engineers | 15:44 |
lpapp | you think a lower layer than the business happens. | 15:44 |
Sput | lpapp: tbh, Archlinux is not a reliable solution for a company | 15:44 |
lpapp | "fixing" yourself is a lot of cost. | 15:44 |
Sput | RHEL would be | 15:44 |
lpapp | which a manager will not take. | 15:45 |
lpapp | a manager will say (rightfully) to use a supported distribution. | 15:45 |
lpapp | but that goes against the engineers' own wish. | 15:45 |
Sput | when I chose to use Gentoo at work, I did that knowing that I could not go to our IT and demand support | 15:45 |
lpapp | archlinux is a reliable solution | 15:45 |
lpapp | have done business for 6-7 years with it. | 15:45 |
Sput | but then I'm also not complaining if the tools we use require tinkering on my end | 15:45 |
lpapp | again, it is not about your money | 15:46 |
lpapp | you do not decide. | 15:46 |
lpapp | the stakeholders decide. | 15:46 |
*** TuTizz <TuTizz!~TuTizz@46.18.96.158> has quit IRC | 15:46 | |
lpapp | engineers wish. | 15:47 |
Sput | well, you use a rolling release distro with no enterprise support for professional purposes, and then go complaining that this distro isn't supported by a project like Yocto... doesn't sound too sane to me :) | 15:47 |
Sput | yet you can make it work, if you invest the time to make it work | 15:47 |
lpapp | no no, that is untrue | 15:47 |
lpapp | I am *definitely* not using Arch for enterprise. | 15:47 |
lpapp | as discussed here the whole day, I was using debian, and since that did not work, I use Ubuntu 12.10 | 15:47 |
lpapp | you are way beyond the facts. :) | 15:48 |
lpapp | I would love to use Archlinux, but I cannot. | 15:48 |
lpapp | because no one sells the argument the engineer like it, but upstream has no any support for it. | 15:48 |
lpapp | buys* | 15:48 |
lpapp | likes* | 15:48 |
Sput | ah well, I'm happily using Gentoo and Yocto does what it's supposed to do if you fix the occasional quirk, so I'm rather happy with it | 15:48 |
lpapp | I would not buy it either. | 15:49 |
Sput | I worked with MeeGo before, I'm rather glad I can use Yocto now :) | 15:49 |
*** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has quit IRC | 15:49 | |
lpapp | bluelightning: http://paste.kde.org/~lpapp/pab8e62ea/ | 15:49 |
lpapp | some issue with my machine. | 15:49 |
lpapp | MeeGo and Yocto ... | 15:50 |
lpapp | apple and orange ... | 15:50 |
Sput | thankfully. | 15:50 |
Sput | I like oranges more. | 15:50 |
bluelightning | lpapp: the x-load recipe declares that it's only compatible with a set list of machines using COMPATIBLE_MACHINE | 15:50 |
seebs | Arlo N' Janis did that one something like 20+ year ago. | 15:50 |
seebs | Arlo: One is hard, smooth, and red. The other is softer, with a dimpled skin, and orange. Janis: What are you doing? Arlo: Comparing apples and oranges. | 15:51 |
lpapp | 16:45 < Sput> yet you can make it work, if you invest the time to make it work -> I do not live 100 hours a day | 15:52 |
seebs | Oh, there's your problem. | 15:53 |
lpapp | if I am not allowed to work with unsupported stuff which is a reasonable decision to be fair, I cannot put anything more into it. | 15:53 |
lpapp | I am already involved with tons of other FOSS stuff, and I have real life, too ... ;-) | 15:53 |
bluelightning | lpapp: don't we all | 15:54 |
lpapp | and frankly, the lack of proper Qt5 bugs me a lot more than switching to ubuntu for now. | 15:54 |
lpapp | bluelightning: yes | 15:54 |
*** Umeaboy <Umeaboy!~Umeaboy@213-21-78-12.customer.t3.se> has joined #yocto | 15:55 | |
*** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has joined #yocto | 15:55 | |
lpapp | I wonder if we really need x-load. | 15:55 |
lpapp | I am afraid, we do. | 15:55 |
lpapp | I might be wrong actually. | 15:55 |
lpapp | if it is this stuff, we probably do not, http://en.wikipedia.org/wiki/Xload | 15:56 |
lpapp | but I bet it is different. | 15:56 |
bluelightning | entirely dependent on how your machine boots | 15:56 |
lpapp | eagle.s3.amazonaws.com/esc/Uboot-esc-chicago-2010.pdf | 15:57 |
lpapp | based on this, u-boot requires x-load. | 15:57 |
lpapp | page 2 -> boot up process. | 15:57 |
lpapp | but it is using ROM | 15:58 |
lpapp | if I understand correctly, x-load is usually used with nand flashes. | 16:00 |
lpapp | written into that. | 16:00 |
lpapp | but we use nor flash. | 16:00 |
ndec | x-load is completely deprecated. | 16:01 |
*** davest <davest!~Adium@134.134.137.73> has quit IRC | 16:01 | |
-YoctoAutoBuilder- build #195 of nightly-fsl-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-ppc-lsb/builds/195 | 16:01 | |
lpapp | ndec: well, beagleboard seems to use it though. | 16:03 |
*** shoragan <shoragan!~jlu@debian/developer/shoragan> has quit IRC | 16:03 | |
-YoctoAutoBuilder- build #236 of nightly-x32 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x32/builds/236 | 16:03 | |
ndec | hmm. that's weird.. | 16:03 |
lpapp | ../meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf does not though. | 16:03 |
lpapp | I personally just flashed the u-boot with openocd, so I did not need x-load | 16:05 |
lpapp | and it worked, so I will drop that for now. | 16:05 |
lpapp | but I would need to get a more thorough picture on the topic later. | 16:05 |
ndec | you don't need it, because it was probably already 'there' on the board. you can't boot with just uboot. | 16:06 |
lpapp | you can. | 16:06 |
lpapp | it was not on the board. | 16:06 |
lpapp | ndec: spl is in the u-boot tree. | 16:10 |
ndec | yes. | 16:10 |
ndec | SPL is the replacement for x-load | 16:10 |
lpapp | yes, it is coming with u-boot. | 16:10 |
*** davest <davest!~Adium@134.134.137.73> has joined #yocto | 16:11 | |
lpapp | who is the u-boot maintainer for oe-core? | 16:13 |
lpapp | is s/he lurking around in here? | 16:13 |
*** francois99 <francois99!~francois9@78-33-60-6.static.enta.net> has quit IRC | 16:15 | |
*** romain_ <romain_!d96c30f9@gateway/web/freenode/ip.217.108.48.249> has quit IRC | 16:15 | |
*** mihai <mihai!~mihai@80.97.15.150> has quit IRC | 16:18 | |
*** GunsNRose <GunsNRose!~GunsNRose@182.139.169.64> has quit IRC | 16:19 | |
*** davest <davest!~Adium@134.134.137.73> has quit IRC | 16:24 | |
*** zenlinux <zenlinux!~sgarman@c-50-139-96-211.hsd1.or.comcast.net> has quit IRC | 16:25 | |
*** mr_science <mr_science!~sarnold@net-cf9a4e91.cst.impulse.net> has joined #yocto | 16:25 | |
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto | 16:25 | |
-YoctoAutoBuilder- build #65 of minnow-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/minnow-lsb/builds/65 | 16:28 | |
lpapp | bluelightning: ndec ^ | 16:28 |
ndec | don't know | 16:28 |
*** smartin_ is now known as smartin | 16:31 | |
*** synthnassizer <synthnassizer!~quassel@143.233.242.130> has quit IRC | 16:35 | |
*** davest <davest!Adium@nat/intel/x-segtebhgvikcacxw> has joined #yocto | 16:37 | |
*** belen <belen!~Adium@134.134.139.70> has quit IRC | 16:39 | |
*** slaine <slaine!~slaine@84.203.137.218> has quit IRC | 16:41 | |
mr_science | moin | 16:42 |
lpapp | yo | 16:42 |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 16:44 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 16:44 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 16:45 | |
* mr_science smells a high-speed timing test on the horizon | 16:49 | |
mr_science | having sata link issues with ~10% of the motherboards... | 16:49 |
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC | 16:52 | |
*** zerus <zerus!~epetmab@90-224-44-236-no67.tbcn.telia.com> has joined #yocto | 16:57 | |
*** zenlinux <zenlinux!~sgarman@173-8-218-204-Oregon.hfc.comcastbusiness.net> has joined #yocto | 16:59 | |
-YoctoAutoBuilder- build #226 of nightly-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-ppc-lsb/builds/226 | 17:01 | |
*** zerus <zerus!~epetmab@90-224-44-236-no67.tbcn.telia.com> has quit IRC | 17:01 | |
*** conditionzero <conditionzero!~Unknown@2001:6f8:12d9:13:1e4b:d6ff:fedb:207c> has quit IRC | 17:04 | |
*** davest <davest!Adium@nat/intel/x-segtebhgvikcacxw> has quit IRC | 17:04 | |
*** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has quit IRC | 17:06 | |
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto | 17:06 | |
*** ka6sox is now known as ka6sox-away | 17:07 | |
-YoctoAutoBuilder- build #224 of nightly-world is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-world/builds/224 | 17:09 | |
*** pidge <pidge!~pidge@c-24-21-207-18.hsd1.or.comcast.net> has joined #yocto | 17:10 | |
mr_science | the sucky part is the lack of response from TI on the plethora of SATA problems posted by customers... | 17:12 |
mr_science | kinda makes me never want to buy another TI part ever again... | 17:13 |
lpapp | mr_science: have you tried e2e? | 17:13 |
lpapp | usually, they are very helpful in there. | 17:13 |
lpapp | mr_science: also, #linux-omap? | 17:14 |
mr_science | been all over the TI e2e forums | 17:14 |
mr_science | they tend to leave them unanswered | 17:14 |
ndec | mr_science: which board? | 17:15 |
mr_science | 816x/am389 family | 17:15 |
mr_science | our board is based largely on the dm8168evm | 17:15 |
*** zenlinux <zenlinux!~sgarman@173-8-218-204-Oregon.hfc.comcastbusiness.net> has quit IRC | 17:16 | |
mr_science | overal i am definitely *not* impressed with their support | 17:16 |
ndec | oh. i didn't know there was sata there | 17:16 |
*** zenlinux <zenlinux!~sgarman@c-50-139-96-211.hsd1.or.comcast.net> has joined #yocto | 17:17 | |
mr_science | everything seems to point to noise and/or timing issues | 17:18 |
mr_science | like i said, it's about a 10% failure rate on boards coming from the manufacturer | 17:19 |
lpapp | mr_science: can you show the forum url? | 17:19 |
mr_science | and our little hardware test suite only tests that the RTC can save/increment the clock | 17:20 |
mr_science | sata test uses the ddt filiesystem test | 17:20 |
lpapp | perhaps I have been lucky with TI, but I had excellent customer support. | 17:21 |
*** Umeaboy <Umeaboy!~Umeaboy@213-21-78-12.customer.t3.se> has quit IRC | 17:21 | |
lpapp | except the fact they do not wanna support C++11 for the TI toolchain, but that is hardly support issue. | 17:21 |
mr_science | lpapp: http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/178108.aspx | 17:21 |
mr_science | that's the one i posted on, but there are tons of others... | 17:21 |
mr_science | put "sata link" in the search box... | 17:22 |
mr_science | haven't asked in #linux-omap yet, so i'll try that... | 17:23 |
*** walters <walters!~walters@c-66-31-18-51.hsd1.ma.comcast.net> has joined #yocto | 17:24 | |
lpapp | mr_science: do not forget that it is holiday season btw. | 17:24 |
-YoctoAutoBuilder- build #229 of nightly-x86 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86/builds/229 | 17:30 | |
mr_science | outside th US you mean? | 17:33 |
lpapp | mr_science: yes | 17:34 |
lpapp | there are many support guys in France for instance. | 17:34 |
*** davest <davest!Adium@nat/intel/x-alktwxtgnjrapnti> has joined #yocto | 17:35 | |
b1gtuna | Morning everybody! including x11 in DISTRO_FEATURES is giving me a grief. GTK+ is refusing to build. I'm on Dylan. What can I do? | 17:37 |
lpapp | b1gtuna: what is the build error? | 17:37 |
b1gtuna | lpapp: one sec i was just about to pastebinit | 17:38 |
b1gtuna | lpapp: thanks | 17:38 |
b1gtuna | lpapp: http://paste.ubuntu.com/5915599/ it's quite large | 17:39 |
b1gtuna | lpapp: i tried cleanall on gtk+, still occuring as long as I have x11 in DISTRO_FEATURES | 17:40 |
lpapp | b1gtuna: and can you confirm you do not have this, /home/ubuntu/build/tmp/sysroots/overo/usr/lib/libXinerama.la | 17:40 |
kergoth | could be a missing dependency on xinerama | 17:40 |
kergoth | lpapp: I have a debootstrap running to test the /usr configuration on ubuntu to see if it works there. Don't have an arch chroot handy, but i expect it's the path that's the issue, rather than the host distro. we shall see | 17:41 |
b1gtuna | lpapp: ls: cannot access /home/ubuntu/build/tmp/sysroots/overo/usr/lib/libXinerama.la: No such file or directory | 17:42 |
b1gtuna | lpapp: so nope it's not there.. =( | 17:42 |
lpapp | b1gtuna: do you have /home/ubuntu/build/tmp/sysroots/overo/usr/lib/ ? | 17:42 |
b1gtuna | lpapp: yes it contains a lot of .la, .so files | 17:44 |
kergoth | b1gtuna: check the gtk recipe for a dependency on xinerama | 17:44 |
lpapp | b1gtuna: ok, so it is probably a missing dependency | 17:44 |
lpapp | is there a proper bitbake manual somewhere? | 17:44 |
b1gtuna | kergoth lpapp - i see doing it now thx | 17:45 |
lpapp | this comes up all the time when I look for one, but it is very short, and does not cover a lot of stuff: https://pixhawk.ethz.ch/_media/dev/oebb/bb_manual.pdf | 17:45 |
lpapp | RP: ^ | 17:46 |
lpapp | openembedded.googlecode.com/files/usermanual.pdf -> perhaps this one? | 17:46 |
lpapp | kergoth: right, I am trying to write a patch for the other issue now ... | 17:47 |
lpapp | I just need a helpful bitbake manual. | 17:47 |
b1gtuna | lpapp kergoth - no dependency on xinerama, will add it and try again | 17:48 |
kergoth | the bitbake manual is in the middle of being rewritten | 17:49 |
kergoth | http://docs.openembedded.org/bitbake/html/ is the old one | 17:50 |
kergoth | but it mostly covers recipe syntax and bitbake command syntax, most everything else is oe/yocto, not bitbake | 17:50 |
lpapp | see my last comment on 4923 | 17:51 |
lpapp | we cannot do much on our side for now. | 17:51 |
lpapp | we could switch away from git to some internal mirror, but meh. | 17:51 |
lpapp | I think distributing an empty folder is wrong from CS. | 17:52 |
*** zecke_ <zecke_!~ich@91-65-247-193-dynip.superkabel.de> has joined #yocto | 17:52 | |
lpapp | but since it cannot be fixed for 2013.05, it has to be solved somewhere. | 17:52 |
lpapp | and the logical workaround place looks meta-sourcery to me. | 17:52 |
lpapp | because that is the central place what everyone would probably use. | 17:52 |
kergoth | I already said in comment #4 that i'd add a check for it | 17:52 |
kergoth | and i will | 17:52 |
lpapp | well, I can help with that. | 17:52 |
lpapp | once I understand the bitbake stuff. | 17:53 |
kergoth | I do have a day job, you realize. supporting people on irc is only part of it | 17:53 |
kergoth | only so many hours in teh day | 17:53 |
kergoth | fair enough | 17:53 |
lpapp | to be honest, 4923 is higher priority for me. | 17:53 |
lpapp | than 4921 | 17:53 |
lpapp | 2013.05 is just a toy project at home. | 17:53 |
lpapp | the real issue is 2009q1 what we use at the company. | 17:53 |
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has quit IRC | 17:54 | |
* lpapp g2g | 17:54 | |
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC | 17:54 | |
sgw_ | lpapp can you please attach the run.do_install.8130 from your temp directory to 4923, I want to check some | 17:55 |
kergoth | already left | 17:55 |
sgw_ | just missed him | 17:55 |
kergoth | he's had a couple valid points, but in other cases his expectations are pretty out there | 17:57 |
* kergoth rolls eyes | 17:57 | |
*** zenlinux <zenlinux!~sgarman@c-50-139-96-211.hsd1.or.comcast.net> has quit IRC | 17:57 | |
b1gtuna | lol | 17:57 |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-nlwtupnnxapzfsaf> has quit IRC | 17:59 | |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-ibnylyfsmcojltvp> has joined #yocto | 18:01 | |
-YoctoAutoBuilder- build #229 of nightly-x86-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-lsb/builds/229 | 18:06 | |
-YoctoAutoBuilder- build #238 of nightly-mips-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-mips-lsb/builds/238 | 18:07 | |
b1gtuna | kergoth: adding xinerama to gtk+'s DEPENDS seems to have fixed. Is this a bug? | 18:12 |
kergoth | sounds like it, do mention w hich releas eyou're using if you open an issue | 18:13 |
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto | 18:13 | |
b1gtuna | kergoth: i will, great thanks | 18:13 |
JaMa | Have anyone seen do_populate_lic_setscene task failing in sstate_install with cp: will not create hard link `/OE/deploy/licenses/recipe' to directory `/OE/deploy/licenses/recipe' (same path) | 18:17 |
lpapp | sgw_: 4923 already got a change which I can test next week. | 18:22 |
sgw_ | lpapp: Ok, I saw that. | 18:22 |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 18:27 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 18:28 | |
b1gtuna | kergoth: should i post a patch or should i simply file through bugzilla? | 18:29 |
kergoth | up to you | 18:29 |
b1gtuna | kergoth: sweet ty | 18:31 |
-YoctoAutoBuilder- build #226 of nightly-ppc is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-ppc/builds/226 | 18:33 | |
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC | 18:34 | |
sgw_ | kergoth: if you have some time, can you look over Qi.Chen's RO ROOTFS changes, I know they would be of interest to you. | 18:35 |
kergoth | I haven't had time to read his reply on my thread even, neck deep in madness :) | 18:36 |
kergoth | will do when i find a moment | 18:36 |
sgw_ | kergoth: thanks | 18:36 |
*** zenlinux <zenlinux!~sgarman@c-50-139-96-211.hsd1.or.comcast.net> has joined #yocto | 18:46 | |
*** zenlinux <zenlinux!~sgarman@c-50-139-96-211.hsd1.or.comcast.net> has quit IRC | 18:51 | |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-ibnylyfsmcojltvp> has quit IRC | 18:51 | |
lpapp | kergoth: have you seen my comment on 4921 | 18:52 |
*** phdeswer_ <phdeswer_!~phdeswer@a88-113-104-180.elisa-laajakaista.fi> has joined #yocto | 18:54 | |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-husrscmbonahvvdw> has joined #yocto | 18:55 | |
*** davest <davest!Adium@nat/intel/x-alktwxtgnjrapnti> has quit IRC | 18:57 | |
*** davest <davest!~Adium@134.134.137.73> has joined #yocto | 18:57 | |
*** zecke_ <zecke_!~ich@91-65-247-193-dynip.superkabel.de> has quit IRC | 18:58 | |
-YoctoAutoBuilder- build #229 of nightly-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-arm-lsb/builds/229 | 18:59 | |
mr_science | b1gtuna: did building xinerama first fix it? | 19:02 |
* mr_science scrolling... | 19:03 | |
lpapp | mr_science: yes | 19:03 |
mr_science | yup, just found it... | 19:04 |
mr_science | kergoth: those are the patches i mentioned before | 19:04 |
mr_science | couldn't remember his name, but Qi.Chen is correct | 19:05 |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 19:21 | |
-YoctoAutoBuilder- build #198 of nightly-fsl-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm/builds/198 | 19:22 | |
*** tor <tor!~tor@c-ef66e655.125-1-64736c10.cust.bredbandsbolaget.se> has quit IRC | 19:59 | |
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 20:08 | |
*** posborne <posborne!ccb603ec@gateway/web/freenode/ip.204.182.3.236> has joined #yocto | 20:09 | |
posborne | Hey all, as you know the default Yocto root password is empty. I want to change this so that one exists, but I'm having some trouble tracking down how to do this. My image has shadow, but I haven't seen anything obvious looking at recipes-extended/shadow | 20:13 |
sgw_ | posborne: what rev are you using? | 20:20 |
posborne | I'm on Dylan | 20:22 |
-YoctoAutoBuilder- build #197 of nightly-fsl-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm-lsb/builds/197 | 20:24 | |
seebs | I have a tentative patch (still testing it a bit) to improve the consistency of how NO32LIBS is handled in pseudo.inc. | 20:25 |
seebs | Basically, the proposed behavior is: If NO32LIBS is 1, we just don't try to do a 32-bit build, and we say so. If NO32LIBS is unset, we try to build 32-bit if and only if stubs-32.h exists. If NO32LIBS is 0, we check for stubs-32.h, and emit a warning if we don't find it. | 20:25 |
lpapp | there should be no NO32LIBS | 20:26 |
lpapp | it should just work automatically IMHO. | 20:26 |
seebs | And then the actual compilation is contingent on whether we think we want to try for it, and if it fails, we have a better diagnostic in view. | 20:26 |
seebs | The background here is that for the vast majority of 64-bit systems, there's no reason at all to build a 32-bit libpseudo, and requiring everyone to have a working multilib toolchain is ridiculous. | 20:28 |
seebs | The one case where 32-bit libpseudo is needed on 64-bit hosts is when there's a compelling need to run 32-bit binaries, and the one case where that tends to come up is prebuilt toolchains (like the Code Sourcery/Mentor Graphics ones). | 20:29 |
seebs | The original behavior was to try to build 32-bit if stubs-32.h existed, but this was a source of build failures and various problems in cases where there really wasn't any need to do this anyway. | 20:29 |
seebs | Problem is, when we adopted the NO32LIBS configuration thing, we never removed the check for stubs-32.h, so you could have a configuration which thought it needed 32-bit libpseudo, but silently failed to actually build one and didn't mention that it was missing something it thought it needed. | 20:30 |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 20:30 | |
seebs | Since a couple of echoes in the pseudo-native/pseudo-nativesdk output are cheap, and the confusions caused by problems with this have been expensive, I'm adding a little extra output, including a message warning the reader (if they happen to go looking, anyway) that only a 64-bit libpseudo is being built in the common case. | 20:32 |
seebs | Will send out a draft patch for review soonish. | 20:32 |
lpapp | the toolchain option specifies what to build already, especially it is 32 bit, there is any doubt what it is. | 20:32 |
lpapp | uname -m returns the host architecture | 20:32 |
lpapp | it should be pretty clear that it is trying to build 32 bit on a 64 bit host if "uname -m" return x86_64, and the toolchain binary is 32 bit ELF. | 20:33 |
sgw_ | posborne: There was a patch for master recently to allow that, and it was discussed on the oe-core ML | 20:33 |
lpapp | I do not see any reason why interaction would be necessary for it to work. | 20:33 |
lpapp | this NO32LIBS feels like a hackaround, but not a real solution. | 20:33 |
sgw_ | posborne: for dylan I have no easy answer other than add some ROOTFS_POSTPROCESS_COMMAND to your image maybe that patches the passwd file | 20:34 |
seebs | The pool of programs which you *might* need to run, which could be 32-bit binaries, is extremely large. It's not restricted to the toolchain. | 20:34 |
seebs | Heck, nothing prevents a user from having a 64-bit gcc executable which calls a 32-bit cc1. | 20:34 |
lpapp | yada-yada | 20:35 |
mr_science | posborne: that's exactly what i so in the older bitbake world too | 20:35 |
lpapp | file works for any important executables, which is in my case gcc only, that would need to be checked. | 20:35 |
mr_science | s/so/do/ | 20:35 |
lpapp | I vote for removing NO32LIBS altogether for my use case, at least, but I feel the potential for removal in certain other scenarios, too. | 20:36 |
mr_science | i also made a pwgen native recipe and use it in my custom image function to generate the root password | 20:36 |
mr_science | since it goes along with adding a normal user with a known password... | 20:36 |
*** Jefro1 <Jefro1!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 20:39 | |
mr_science | posborne: let me know if you'd like to know any details (it's pretty straightforward) | 20:40 |
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 20:41 | |
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto | 20:42 | |
posborne | mr_science sgw_ Thanks, I'll look at the latest stuff. Before I got pulled away from my desk I was starting to look into ROOTFS_POSTPROCESS_COMMAND | 20:52 |
b1gtuna | Has anyone done gdm + xfce integration? Can't shutdown as a user. Kicks me back into the login screen instead. | 20:52 |
posborne | Related, is there a good way to trace backward from a file in the sysroot to see which recipe(s) touch it? | 20:52 |
lpapp | kergoth: have you made any progress on the arch chroot | 21:00 |
lpapp | or were you able to reproduce that on ubuntu | 21:00 |
lpapp | I need to leave soon. | 21:00 |
seebs | You mean 4919? | 21:01 |
seebs | I went and looked more closely at that because I'd been looking at the command line options. The huge pile of incompatible library directories isn't even remotely related to anything Yocto's doing except specifying "-m32" to a compiler that's not configured to know to look elsewhere for 32-bit libraries. | 21:02 |
mr_science | posborne: much easier to link the file to a package in the runtime | 21:02 |
seebs | The only -L in there is into a bitbake library directory which is in fact the correct directory for it to specify. | 21:02 |
mr_science | using opkg on the running system | 21:02 |
mr_science | posborne: let me pastebin something... | 21:03 |
*** davest <davest!~Adium@134.134.137.73> has quit IRC | 21:03 | |
lpapp | no, not 4919. | 21:03 |
posborne | mr_science: sure, whatever works | 21:07 |
mr_science | this relates root password thing as opposed to tracing a file... | 21:08 |
posborne | mr_science: ah, gotcha | 21:08 |
mr_science | http://paste2.org/pZp792G7 <= this is at the bottom of my image recipe, with some other custom stuff | 21:08 |
mr_science | lemme thing about the other one for a sec... | 21:09 |
mr_science | as i said, easy to go from "opkg search /usr/bin/foo" to a recipe that builds the package | 21:10 |
mr_science | traceability from the sysroot is a bit different... | 21:11 |
mr_science | posborne: if you tell me what the file is i might be able to answer, but i don't have a "query sysroot" answer to the bigger question atm | 21:12 |
mr_science | unless it's a file from one your own in-house packages | 21:14 |
posborne | Sure, that is fair. In this case, I was wondering about /etc/shadow | 21:14 |
mr_science | the recipe is also "shadow" | 21:17 |
mr_science | in oe-core | 21:17 |
mr_science | oe-core/meta/recipes-extended/shadow | 21:17 |
posborne | Right, initially looking at the recipe, it was hard to see that it actually generated the file. | 21:18 |
posborne | mr_science: thanks for the pastebin. building an image now to test | 21:18 |
*** zenlinux <zenlinux!~sgarman@c-50-139-96-211.hsd1.or.comcast.net> has joined #yocto | 21:19 | |
mr_science | posborne: recipes typically don't even have a function for compile or install unless they need to do something special or apply a workaround | 21:22 |
mr_science | so looking there is a little "iffy" | 21:22 |
mr_science | OTOH, sometimes you'll find a whole bunch of manual install stuff and file/path jiggering | 21:23 |
mr_science | it all depends on the condition of upstream | 21:23 |
mr_science | which is probably pretty obvious so i'll shutup now | 21:24 |
posborne | mr_science: haha, no problem. the help has been appreciated | 21:27 |
mr_science | maybe i'm stilla little numb from my lovely meeting where i was the only linux guy... | 21:28 |
mr_science | don't think they learned a thing, so i can't call it successful, at least from my perspective | 21:30 |
*** zerus <zerus!~epetmab@90-224-44-236-no67.tbcn.telia.com> has joined #yocto | 21:30 | |
posborne | mr_science: I'm on a couple projects like that right now; nothing more fun telling people what to type in the terminal over the phone | 21:30 |
*** davest <davest!Adium@nat/intel/x-beddoaxteprkdsml> has joined #yocto | 21:32 | |
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC | 21:38 | |
mr_science | if that's all it was i'd never have mentioned it... | 21:40 |
mr_science | well, maybe... | 21:40 |
mr_science | posborne: feel free to yell at me after hours (ping nerdboy) if you have more questions | 21:45 |
mr_science | since i have a pretty extensive set of custom_post_process stuff | 21:45 |
* mr_science goes bowling... | 21:47 | |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-husrscmbonahvvdw> has quit IRC | 21:48 | |
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC | 21:52 | |
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC | 21:52 | |
*** Umeaboy <Umeaboy!~Umeaboy@213-21-78-12.customer.t3.se> has joined #yocto | 21:58 | |
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto | 22:03 | |
*** ant_home <ant_home!~andrea@host88-64-dynamic.8-87-r.retail.telecomitalia.it> has joined #yocto | 22:08 | |
*** zerus <zerus!~epetmab@90-224-44-236-no67.tbcn.telia.com> has quit IRC | 22:23 | |
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto | 22:23 | |
*** eren <eren!~eren@unaffiliated/eren> has quit IRC | 22:25 | |
*** davest <davest!Adium@nat/intel/x-beddoaxteprkdsml> has quit IRC | 22:27 | |
*** challinan <challinan!~challinan@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has quit IRC | 22:29 | |
*** davest <davest!~Adium@134.134.137.73> has joined #yocto | 22:30 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 22:32 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 22:32 | |
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC | 22:37 | |
*** posborne <posborne!ccb603ec@gateway/web/freenode/ip.204.182.3.236> has quit IRC | 22:50 | |
*** darknighte is now known as darknighte_znc | 22:52 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 22:55 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 22:56 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 23:04 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 23:05 | |
*** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has quit IRC | 23:07 | |
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC | 23:13 | |
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto | 23:14 | |
*** hollisb <hollisb!~hollisb@c-67-169-221-181.hsd1.or.comcast.net> has quit IRC | 23:16 | |
*** bluelightning <bluelightning!~paul@cpc13-lewi17-2-0-cust74.2-4.cable.virginmedia.com> has joined #yocto | 23:20 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 23:20 | |
*** phdeswer_ <phdeswer_!~phdeswer@a88-113-104-180.elisa-laajakaista.fi> has quit IRC | 23:31 | |
*** Umeaboy <Umeaboy!~Umeaboy@213-21-78-12.customer.t3.se> has quit IRC | 23:35 | |
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC | 23:37 | |
*** fitzsim <fitzsim!~user@nat/cisco/x-ioyofluolunadyzh> has quit IRC | 23:39 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC | 23:44 | |
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto | 23:44 | |
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto | 23:57 |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!