**** BEGIN LOGGING AT Sat Dec 14 02:59:59 2013
Dec 14 03:06:02 <ausjke> can i list all rpm installed? rpm -qa errs
Dec 14 03:06:48 <ausjke> i c it's a rpm from busybox that can only install pkg?
Dec 14 03:08:41 <ausjke> sucks, comparing to dpkg
Dec 14 08:19:13 <Smitty> .
Dec 14 08:19:20 <Smitty> skipping incompatible /usr/lib/libX11.so when searching for -lX11
Dec 14 08:19:25 <Smitty> Build error
Dec 14 08:19:52 <Smitty> Just following Quick Start Guide.
Dec 14 08:20:19 <Smitty> Why wouldn't Yocto be linking against its own toolchain or sysroot X11 ?
Dec 14 08:51:35 <Smitty> http://pastebin.com/Ls8qcpqu
Dec 14 08:51:41 <Smitty> I'm confused
Dec 14 08:52:28 <Smitty> Why is Yocto building ARM architecture when I am targetting qemu86
Dec 14 08:53:44 <Smitty> And why is it looking anywhere other than its sysroot for available link lbraries
Dec 14 09:15:16 <Smitty> Is anybody here ?
Dec 14 12:20:55 <Smitty> I am still no wiser after what I consider fairly extensive (over 1 hour) investigation into my build issue:  http://pastebin.com/Ls8qcpqu
Dec 14 12:23:54 <Smitty_> http://pastebin.com/2jvCf4DP
Dec 14 13:20:35 <Smigers> anyone home ?
Dec 14 13:20:59 <Smigers> Please see:  http://pastebin.com/2jvCf4DP
Dec 14 13:22:03 <Smigers> I am really getting frustrated by this.  I assume that the Quick Start Guide *should* work.  I've followed the instructions exactly, three times in a row, and continue to run into trouble each time.
Dec 14 13:32:23 <Crofton|work> smartin, loks like it is catching libs from the build machine
Dec 14 13:32:44 <Crofton|work> Smigers, that is
Dec 14 13:32:49 <Crofton|work> that shoudn't ahppen
Dec 14 13:32:54 <Smigers> I know
Dec 14 13:33:02 <Crofton|work> not many people around over the weekend either
Dec 14 13:33:11 <Smigers> The question is how it's even possible for such a huge error
Dec 14 13:33:15 <Crofton|work> what distro is your build machine running
Dec 14 13:33:27 <Smigers> Fedora 19 with latest updates
Dec 14 13:33:33 <Crofton|work> weird
Dec 14 13:33:36 <Crofton|work> same as me
Dec 14 13:34:07 <Smigers> I'm willing to start over *again*.  Is there anything other than the yocto source tree that I should wipe our
Dec 14 13:34:09 <Smigers> out
Dec 14 13:34:36 <Crofton|work> the build dir, but I think you are catching that
Dec 14 13:34:44 <Crofton|work> but this is really weird
Dec 14 13:35:06 <Smigers> I'll delete poky-dora-10.0.0, and extraxt the tar again, and just run through the quick start once more.
Dec 14 13:35:33 <Smigers> that's all under poxy-dora right ?
Dec 14 13:38:56 <Crofton|work> should be
Dec 14 13:39:34 <Smigers> So, I'm not storing any kind of state in a hidden directory in HOME, or /etc, or somethign silly like that
Dec 14 13:40:21 <Crofton|work> shouldn't be
Dec 14 14:23:09 <Smigers> During the build I see these types of warnings
Dec 14 14:23:11 <Smigers> WARNING: Failed to fetch URL ftp://ftp.ossp.org/pkg/lib/uuid/uuid-1.6.2.tar.gz, attempting MIRRORS if available
Dec 14 14:23:13 <Smigers> I Have tried to log into that server via ftp and get disconnected immediately
Dec 14 14:24:19 <Smigers> Actually it seems quite a few of the links are out of date
Dec 14 14:24:44 <Smigers> I am now failing to download from  http://www.apache.org/dist/apr/apr-1.4.8.tar.bz2
Dec 14 14:25:48 <Smigers> Presumably I will see an error rather than a warning if the download can never be resolved
Dec 14 14:31:03 <bluelightning> Smigers: correct, if it's just a warning, no need to worry
Dec 14 14:31:53 <bluelightning> upstreams do disappear / remove versions from download quite often unfortunately, that's why we have mirrors
Dec 14 14:33:21 <Smigers> Understood.  Maybe contacting the host admin and asking for the package to be preserved so that the Quick Start Guide doesn't have to be constantly adjusted  would be a good idea
Dec 14 14:34:38 <Smigers> rahter I should say so that poky-10.0.0 recipes don't need to be maintained
Dec 14 14:35:51 <Smigers> either that or host all the poky-10.0.0 packages on the Yocto server
Dec 14 14:51:22 <bluelightning> Smigers: well, we don't really need to update the qs guide in these instances because we automatically fall back to our mirror
Dec 14 14:51:51 <Smigers> Ah
Dec 14 14:51:55 <bluelightning> Smigers: we always have all sources available in our mirror - disk space is cheap ;)
Dec 14 15:07:27 <RP> dora build looks good on the AB at least...
Dec 14 15:10:31 <bluelightning> RP: great stuff
Dec 14 15:19:38 <Smigers> Same problem:   http://pastebin.com/U50EUDU5
Dec 14 15:24:27 <Smigers> Seems like a pretty fundamental error to me
Dec 14 15:25:21 <Smigers> Why would y64 even be built if I am targetting i586 running under qemu ?
Dec 14 15:25:30 <Smigers> x64
Dec 14 15:26:37 <Smigers> TARGET_SYS        = "i586-poky-linux"
Dec 14 15:26:39 <Smigers> MACHINE           = "qemux86"
Dec 14 15:27:24 <Smigers> or is it trying to build  qemu for my host machine ?
Dec 14 15:37:57 <Smigers> OK, looking through the Yocto release logs, it seems that Fedora 19 was a problematic build host platform until more recent releases of yocto.  I'm-a try latest yocto rather than the prescribed version in the Quick Start Guide.
Dec 14 15:42:30 <Smigers> Actually, they are the same version
Dec 14 15:42:50 <Smigers> OK, so, now I am totally confused.
Dec 14 15:52:31 <Smigers> OK, it seems that for some reason the link line is not finding the 64 bit libX, rather it finds the 32 bit version, and then says it's no goo (obviously)
Dec 14 15:53:58 <Smigers> where would I adjust that so that it points to the right place.
Dec 14 16:09:22 <Smigers> I find this system completely unfathomable.  TO the point where I am beginning to doubt that it works.
Dec 14 17:17:28 <nerdboy> hmm, toolchain with fortran/java seems a little incomplete
Dec 14 17:28:33 <nerdboy> what's the proper bugzilla product for a toolchain bug?
Dec 14 18:00:25 <nerdboy> building another crossdev toolchain with java...
Dec 14 18:00:27 <sgw_> nerdboy: oecore/devtools
Dec 14 18:06:05 <nerdboy> thx
Dec 14 18:07:19 * nerdboy <= ignoring oe-classic homework
Dec 14 18:10:23 <nerdboy> damn that little x86 vm is fast...
Dec 14 18:16:44 <flihp> is there a way to manipulate bb variables like 'SRC_URI' from shell functions or do I need to use python i.e. d.appendVar?
Dec 14 18:17:55 <kergoth`> shell functions are run at task execution time, not parse time
Dec 14 18:18:03 <kergoth`> so it wouldn't make much sense for them to be able to alter bitbake metadata
Dec 14 18:18:06 <kergoth`> what would it affect?
Dec 14 18:18:23 <kergoth`> if you just want to *use* the variable, just dereference it with ${SRC_URI}
Dec 14 18:18:29 <kergoth`> if you need to alter it, you can use inline python
Dec 14 18:18:43 <kergoth`> ${@','.join(SRC_URI.split())} or whatever
Dec 14 18:19:16 <flihp> thanks kergoth, very clear
Dec 14 18:20:45 <kergoth`> np
Dec 14 18:30:20 <nerdboy> no gcj out of crossdev either, at least using the native 4.6.4 i built a while back, which apparently doesn't have it enabled...
Dec 14 18:32:02 <nerdboy> let's try that again
Dec 14 18:32:51 <kergoth`> crossdev, that's the gentoo cross toolchain generator, or the ubuntu one?
Dec 14 18:34:23 <kergoth`> I just installed windows 3.11 in dosbox, with the right drivers to run it in 1024x768 and all, installed quicktime and video for windows.. now for trumpet winsock to get internet working in there :D
Dec 14 18:34:27 * kergoth` is in a nostalgic mood
Dec 14 18:35:06 <nerdboy> you're one big giant mystery...
Dec 14 18:35:20 * kergoth` chuckles
Dec 14 18:35:26 <nerdboy> crossdev is the gentoo version of crosstool
Dec 14 18:35:31 <kergoth`> ahh, right
Dec 14 18:35:33 <kergoth`> cool
Dec 14 18:35:57 <nerdboy> rebuilding gcc with java, then try cross with java again
Dec 14 18:37:25 <nerdboy> and i don't see the ecj-4.x.jar file in poky downloads either
Dec 14 18:37:44 <nerdboy> might it be missing that dep?
Dec 14 18:41:35 <nerdboy> seems like it should work as long as c++ is also enabled and the lib source is available
Dec 14 19:00:34 <nerdboy> boy do you get a buttload of javax/swing headers if you enable java and gtk
Dec 14 20:32:13 <nerdboy> that looks like a fail for crossdev and gcj
Dec 14 20:32:35 <nerdboy> it did build all the fortran stuff, but no java
Dec 14 21:35:03 <nerdboy> tags no longer work as a git SRCREV?  hmmm...
Dec 14 22:34:06 <Smigers> Please help
Dec 14 22:34:08 <Smigers> http://pastebin.com/598mjykJ
Dec 14 22:34:52 <Smigers> I cannot understand how this could be happening without Yocto itself being completely broken
Dec 14 22:35:40 <Crofton|work> have you tried some other machines?
Dec 14 22:36:22 <Smigers> I've already targetted qemux86, and this time qemux86-64
Dec 14 22:36:31 <Crofton|work> try setting MACHINE to beagleboard
Dec 14 22:37:02 <Crofton|work> I am grasping at straws, becuase I do not understand how something that should be that well test will find things on the build machine
Dec 14 22:37:14 <Smigers> Why ?
Dec 14 22:37:16 <Smigers> I don't have a beagleboard, and it's not the target
Dec 14 22:37:18 <Crofton|work> so tryin gan arm target might give us some clues
Dec 14 22:37:22 <Crofton|work> I know
Dec 14 22:37:40 <Crofton|work> see the "I am grasping at straws"
Dec 14 22:37:50 <Smigers> Sure, I appreciate the help
Dec 14 22:37:53 <Crofton|work> I want to see if we can make anything work
Dec 14 22:38:55 <Smigers> BUT, If it can't do the Quick Start Guide , which should be absolutely tested, why would I ever imagine it could do some other variant
Dec 14 22:39:19 <Crofton|work> Yes, this is very curious
Dec 14 22:39:28 <Smigers> More than curious
Dec 14 22:39:41 <Smigers> Almost like none of this really works
Dec 14 22:39:44 <Crofton|work> annoying, most of the people that care about that particular path aren't usually around on weekends
Dec 14 22:40:23 <Smigers> That particualr path is the test system
Dec 14 22:40:44 <Smigers> if I can't build the cannonical system, why would I do anything else
Dec 14 22:41:17 <Crofton|work> just try the beaglebone
Dec 14 22:41:24 <Crofton|work> er board :)
Dec 14 22:41:50 <Crofton|work> your ip suggests you are in .de?
Dec 14 22:42:01 <Crofton|work> can you try asking on Monday morning?
Dec 14 22:44:22 <Smigers> Sure, Monday is not a problem.  But, How could this be broken.  I'm doing nothing but trying to follow the QSG.  How could that not work on a supported environment ?
Dec 14 22:46:37 <Smigers> It makes me think worry that actually none of it is correctly tested.  I really have to wonder about the standard of the developer when I can't even follow the basic example.
Dec 14 22:47:07 <Smigers> without an error occuring
Dec 14 22:53:05 <nerdboy> Smigers: what branch are you on?
Dec 14 22:53:17 <Smigers> what do you mean ?
Dec 14 22:53:29 <nerdboy> meta-yocto-bsp    = "<unknown>:<unknown>"
Dec 14 22:53:52 <Smigers> how do I tell yout the answer to that question
Dec 14 22:53:57 <nerdboy> did you try master or one of the other branches?
Dec 14 22:54:16 <nerdboy> git status in your poky/oe dirs
Dec 14 22:54:17 <Smigers> I don't understand the question
Dec 14 22:54:33 <Smigers> ??
Dec 14 22:55:19 <Smigers> Please, if you are asking me to do something, be precise.
Dec 14 22:55:28 <nerdboy> you followed the quickstart and downloaded a tarball?
Dec 14 22:55:32 <Smigers> yes
Dec 14 22:55:57 <nerdboy> hmm, haven't tried that...
Dec 14 22:56:08 <Smigers> What ?
Dec 14 22:56:38 <nerdboy> tarball
Dec 14 22:56:44 <Smigers> How did you possibly get started without using some kind of documentation.
Dec 14 22:56:58 <nerdboy> would you like to try the cloning the layers?
Dec 14 22:57:03 <Smigers> Did you just guess your way though the whole process
Dec 14 22:57:20 <nerdboy> no, i followed the readme
Dec 14 22:57:33 <Smigers> Idiotic
Dec 14 22:57:49 <nerdboy> https://github.com/sarnold/meta-raspberrypi/blob/master/README
Dec 14 22:58:02 <Smigers> I follow the instructions that are presented to me on the documentation page
Dec 14 22:58:16 <Smigers> Why would I ever do anything other than that
Dec 14 22:58:28 <nerdboy> i'm just talking building from git clones instead of the tarball
Dec 14 22:58:45 <Smigers> What would compell me to do that
Dec 14 22:58:46 <nerdboy> then you can switch branches between different releases
Dec 14 22:59:03 <Smigers> how would I even know that that was an option
Dec 14 22:59:36 <Smigers> That is simply stupidity
Dec 14 22:59:46 <nerdboy> it's in the regular docs, just not the quickstart i guess
Dec 14 23:00:03 <Smigers> I am following the documentation.  If the docs are wrong the whole project is wrong
Dec 14 23:00:18 <nerdboy> you're following one version of one doc
Dec 14 23:00:37 <Smigers> the proect "lives" in the documentation
Dec 14 23:00:47 <kergoth`> the quickstart guide is only part of the yocto documentation
Dec 14 23:00:54 <kergoth`> there are other documents
Dec 14 23:01:30 <Smigers> I am following the documentation on the most significant link of the main page of the Yocto project web site#
Dec 14 23:01:33 <kergoth> regardless, I don't think continuous complaints are going to resolve your problem any faster
Dec 14 23:01:45 <Smigers> That's a bullshit respone
Dec 14 23:01:56 <nerdboy> http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#intro-getit
Dec 14 23:01:56 <kergoth> Yet, completely accurate
Dec 14 23:01:57 <Smigers> I want to learn
Dec 14 23:02:16 <Smigers> but I am unable to learn from the provided documentation
Dec 14 23:02:26 <kergoth> you haven't bothered to read all the documentation
Dec 14 23:02:29 <nerdboy> "You can set up the Source Directory by downloading a Yocto Project release tarball and unpacking it, or by cloning a copy of the upstream Poky Git repository"
Dec 14 23:02:49 <nerdboy> try method #2
Dec 14 23:03:20 <Smigers> Why would I try method #2 when method #1 fails in ways that are totally stupid
Dec 14 23:03:46 <nerdboy> because method 1 fails maybe?
Dec 14 23:04:27 <Smigers> Method 1 fails, so I am expected to continue to waste my time following another method which might also fail ?
Dec 14 23:04:48 <nerdboy> while you were complaining i just tried bitbake qemu-native -c build and it builds fine
Dec 14 23:05:12 <Smigers> Sorr, I can't belive it
Dec 14 23:05:20 <nerdboy> you're the one who said you wanted to learn
Dec 14 23:05:39 <nerdboy> maybe uncorking your attitude would help
Dec 14 23:05:52 <nerdboy> NOTE: Tasks Summary: Attempted 164 tasks of which 137 didn't need to be rerun and all succeeded.
Dec 14 23:05:54 <Smigers> Please list the "exact" steps that you took to build
Dec 14 23:06:07 <nerdboy> see method #2
Dec 14 23:06:29 <nerdboy> i have git clones i just updated today
Dec 14 23:06:45 <Smigers> NOTE: Tasks Summary: Attempted 5075 tasks of which 5074 didn't need to be rerun and 1 failed.
Dec 14 23:06:50 <nerdboy> usually build off master, but you're free to build a release branch
Dec 14 23:07:03 <Smigers> I'm trying to follow the QSG
Dec 14 23:07:18 <Smigers> if that doesn't work, I assume the whole prodict is crap
Dec 14 23:07:45 <nerdboy> maybe the quickstart is out of date, aor maybe that particular tarball is borked
Dec 14 23:07:57 <nerdboy> or maybe your build env isn't sane
Dec 14 23:08:03 <nerdboy> i have no idea
Dec 14 23:08:18 <Smigers> How could my build env be not sane if I am following the QSG
Dec 14 23:09:16 <nerdboy> normal stuff builds fine for most people, so obviously something is amiss
Dec 14 23:09:46 <Smigers> Please, I beg you.  Start our on a vanilla Fedora x86-64 machine.  The follow the QSG, and let me know how you progress
Dec 14 23:10:04 <nerdboy> i build on gentoo/debian/ubuntu
Dec 14 23:10:13 <nerdboy> don't have fedora handy
Dec 14 23:10:23 <Smigers> Great. Das hilft mich ncht
Dec 14 23:10:25 <nerdboy> but other people do
Dec 14 23:11:00 <Smigers> do it on a virtua machine
Dec 14 23:11:10 <nerdboy> try pasting the output of bitbake -e
Dec 14 23:12:00 <nerdboy> i native/chroot/vm setups, still don't have any fedora...
Dec 14 23:12:06 <nerdboy> *have
Dec 14 23:18:32 <Smigers> So I tried to past the output, but there some much of it that it fails.
Dec 14 23:18:43 <Smigers> Even in a pastebin
Dec 14 23:20:08 <nerdboy> and you have all host packages installed listed here?  http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#required-packages-for-the-host-development-system
Dec 14 23:23:03 <Smigers> WTF is all that ?
Dec 14 23:23:40 <Smigers> I have just run that and suddenöly it seems I neeed to insatall 200 Mb of packages
Dec 14 23:24:00 <Smigers> Yet, I have all the dependeincies specified in the QSG
Dec 14 23:24:39 <Smigers> So, are you saying the QSG is a completely irrelevent piece of dreck, or what ?
Dec 14 23:25:44 <Smigers> And anyway, none of those packages provide the missing X11 library anyway
Dec 14 23:25:44 <bluelightning> er, that's the same info that's in the quick start guide, just broken out for specific use cases...
Dec 14 23:25:51 <Smigers> no
Dec 14 23:25:54 <Smigers> it is not
Dec 14 23:25:59 <bluelightning> it is, I wrote it...
Dec 14 23:26:05 <Smigers> buull
Dec 14 23:26:09 <Smigers> Sorry
Dec 14 23:26:11 <bluelightning> well, I provided the list at any rate
Dec 14 23:26:17 <Smigers> It is simply wrong to say that
Dec 14 23:26:25 <bluelightning> where are you looking then?
Dec 14 23:26:32 <Smigers> I followed the QSG verbatim 5 times
Dec 14 23:26:43 <Smigers> and ever time I fail at the same place
Dec 14 23:26:55 <bluelightning> no, where in the quick start guide are you getting a list that is different from that given in the link above?
Dec 14 23:27:48 <Smigers> I am following this QSG: http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html
Dec 14 23:28:33 <Smigers> exactly as written
Dec 14 23:29:16 <bluelightning> right, and the list of packages given there is the exactly the same as "Essentials" and "Graphical Extras" in the reference manual section linked above
Dec 14 23:29:32 <Smigers> What ?
Dec 14 23:30:20 <Smigers> The essential and graphical packages you need for a supported Fedora distribution are shown in the following command:
Dec 14 23:30:24 <Smigers>      $ sudo yum install gawk make wget tar bzip2 gzip python unzip perl patch \
Dec 14 23:30:26 <Smigers>      diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath \
Dec 14 23:30:28 <Smigers>      ccache perl-Data-Dumper perl-Text-ParseWords SDL-devel xterm
Dec 14 23:30:35 <Smigers> I did that
Dec 14 23:31:07 <bluelightning> right, so then you should have all that is needed installed
Dec 14 23:31:31 <Smigers> But clearly I don't
Dec 14 23:31:46 <Smigers> So, rather than blame me, why not try it yourself
Dec 14 23:32:14 <bluelightning> I'm not blaming you
Dec 14 23:32:23 <Smigers> so, What is wrong
Dec 14 23:33:26 <bluelightning> I'm not sure, I can tell you I have done builds on F19 and not seen that error
Dec 14 23:33:38 <bluelightning> I can try one now
Dec 14 23:33:52 <Smigers> And besides.....If all these stupid things are required, why doesn't the yocto build resolve and download them itself
Dec 14 23:34:25 <Smigers> this is childs play
Dec 14 23:35:14 <bluelightning> we do download and build a lot of tools, but for some things it is better for the host system to provide them
Dec 14 23:36:33 <Smigers> I have a Cmakae system that lets me do all of this already.  BUT for some stupid marketing reason I am forced to used Yocto - bperhaps because the name is cute, or perhaps because my comapny has to kowtow to the Japanese - I am supposed to use Yocto.   But from what I can see it provides absolutely nothing but more chaos and broken 'crap' that I have to deal with.
Dec 14 23:37:16 <Smigers> BS on you last statement
Dec 14 23:37:26 <bluelightning> you know, if you want help from people you'd do well to be a bit more polite
Dec 14 23:37:26 <Smigers> If you need it, you download it
Dec 14 23:37:38 <Smigers> Come on
Dec 14 23:37:46 <Smigers> I'm really trying here
Dec 14 23:38:01 <Smigers> But I'm getting completely frustrated with this
Dec 14 23:38:08 <bluelightning> I can see that
Dec 14 23:38:22 <Smigers> Yocto should be able to resolve everythign it needs
Dec 14 23:38:38 <Smigers> why doesn't it do that
Dec 14 23:38:53 <Smigers> My own, homegrown CMake system does that already
Dec 14 23:39:01 <bluelightning> it's not that simple
Dec 14 23:39:15 <Smigers> really ?
Dec 14 23:39:20 <bluelightning> yes really
Dec 14 23:39:20 <Smigers> Why not ?
Dec 14 23:40:04 <bluelightning> look, I'm in here on my weekend, if you want help with your problem I will try to help, but I'm not going to go through everything justifying it, sorry
Dec 14 23:40:18 <Smigers> I appreciate that
Dec 14 23:40:28 <Smigers> I understand completely
Dec 14 23:40:34 <Smigers> I am on my own time too
Dec 14 23:41:12 <Smigers> So, let's work together to try to figure this lunacy out
Dec 14 23:42:08 <Smigers> Can you do voice ?
Dec 14 23:43:07 <bluelightning> no, I'm afraid not
Dec 14 23:43:23 <Smigers> OK
Dec 14 23:43:32 <Smigers> Well, how do we progress ?
Dec 14 23:43:47 <bluelightning> I'm starting a build here now
Dec 14 23:44:05 <Smigers> what build ?
Dec 14 23:44:49 <Smigers> I am running x86-64 Fedora 19 and would like to target qemux86-64
Dec 14 23:45:40 <Smigers> Now, why I would specify qemux86-64 rather than simply x86-64, I must admist I really don't understand
Dec 14 23:46:03 <bluelightning> that's just what the machine is called
Dec 14 23:46:18 <Smigers> Yeh, it's dumb.
Dec 14 23:46:25 <bluelightning> it isn't
Dec 14 23:46:32 <Smigers> qemu is an emulator
Dec 14 23:46:52 <Smigers> if I buld an x86 I expect qemu to run it
Dec 14 23:47:10 <Smigers> if I buld x86-64 I also expect qemu to run it
Dec 14 23:47:16 <bluelightning> we have qemux86-64 and genericx86-64; the distinction (mainly level of functionality) is a useful one
Dec 14 23:48:04 <Smigers> if I build zilog6800, the of course I would expect a problem find a VM that can run that
Dec 14 23:48:42 <Smigers> but if it is a supported target, it should buld, regardless of my ability to actually run the target
Dec 14 23:50:57 <Smigers> do you understand ?
Dec 14 23:51:35 <bluelightning> I agree, it should build, but I don't think this has anything to do with the failure
Dec 14 23:51:42 <Smigers> I do
Dec 14 23:51:55 <Smigers> The failure is really fundamental
Dec 14 23:52:29 <bluelightning> it's apparently failing to find an appropriate libx11 on your system, though it thinks it should be there
Dec 14 23:52:38 <Smigers> Exactly.
Dec 14 23:53:05 <Smigers> If it needs a specific version of X11, it should FREAKING  build it
Dec 14 23:53:24 <Smigers> hpw complicated is that
Dec 14 23:53:55 <Smigers> that's what thwe whole damned system is about
Dec 14 23:54:23 <Smigers> When I buld for a target, I want the buld system to resolve the target dependencies
Dec 14 23:54:44 <Smigers> I shouldn't have to resolve them myselve
Dec 14 23:54:49 <bluelightning> that doesn't work; we've had problems trying to do that in the past; I don't know the full details off the top of my head
Dec 14 23:55:03 <bluelightning> no of course you shouldn't have this failure, but every piece of software has bugs
Dec 14 23:55:06 <Smigers> Really
Dec 14 23:55:22 <Smigers> that's a üretty fundamental bug
Dec 14 23:56:31 <Smigers> module ZZZ required libX (version ???) and doesn't resolve it ????
Dec 14 23:56:33 <Smigers> WTF is the build system doiing if it isnt't doing that
Dec 14 23:56:46 <bluelightning> well, if we run test builds on F19 (and our QA team does regularly) and we don't see this error, then how would we know to go and fix it?
Dec 14 23:57:14 <Smigers> No, you are missing the point
Dec 14 23:57:34 <Smigers> Everything is resolvable
Dec 14 23:58:12 <Smigers> the whole point of a build system like Yocto is that it takes this resolution issue away from the developer
Dec 14 23:58:46 <Smigers> I sould not have to worry about resolving the dependencies of a module that I include
Dec 14 23:59:02 <Smigers> that's what Yocto is supposed to be doing for me
Dec 14 23:59:23 <bluelightning> this is not a missing dependency though
Dec 14 23:59:32 <Smigers> Let'S be clear
Dec 14 23:59:47 <Smigers> I am typing this on my "host machine"
Dec 15 00:00:01 <Smigers> it is fedora x86-64
Dec 15 00:00:31 <Smigers> fedora 19 with the latest updates as of 13.12.2013
Dec 15 00:02:05 <bluelightning> yes, I understand that
Dec 15 00:02:40 <Smigers> For example, I want to build an app that runs on an ARM ARMv8-A  (or something)
Dec 15 00:03:36 <Smigers> Assuming Yocto supports that , I should simply specify that in some config, and start the build
Dec 15 00:04:42 <Smigers> I have clearyl tried that already with a target of x86, x86-64, some weird variant called qemux86, and another one called qemux86-64
Dec 15 00:04:48 <Smigers> None of the builds
Dec 15 00:04:56 <Smigers> they all fail at the same place
Dec 15 00:05:07 <Smigers> none of them builds
Dec 15 00:07:45 <Smigers> The manner in which they fail indicates that the build system is looking in *poison* directories.  In other words, Since I am running x86-64 Fedora, and the bulld system is targetting qemux86, then it shoudl never look in my system for a link library.  It should only ever look in its idea of sysroot
Dec 15 00:09:19 <Smigers> Why  would Yocto ever look outside of its own target sysroot environment for a library.  That's simply wrong
Dec 15 00:10:40 <Smigers> This is such a fundamental problem that I can't imagine what Yocto is doing
Dec 15 00:10:48 <Smigers> other than something wrong
Dec 15 00:18:42 <bluelightning> it can't start building for the target until it's build some native tools
Dec 15 00:19:01 <bluelightning> that is why it is looking at your host system and that is why it fails in the same place no matter what the target is
Dec 15 00:20:36 <Smigers> Native tools ?
Dec 15 00:21:03 <Smigers> You meam something other than the toolchain ?
Dec 15 00:21:30 <Smigers> Toolchiain being gcc, ld, nm, etc...
Dec 15 00:21:46 <Smigers> if it needs it, it should download it and buld it
Dec 15 00:22:00 <Smigers> or specify it as a prerequisite
Dec 15 00:22:15 <Smigers> neither is happening
Dec 15 00:23:42 <Smigers> Since neither sis happening, Yocto is broken
Dec 15 00:39:39 <sgw_> Smigers: I am curious, do you have multilib binaries or libraries installed on your host machine?  I have not read back, but it seems like that.
Dec 15 00:44:10 <Smigers> SGW I am am sorry, but I don't understand your question
Dec 15 00:46:42 <Smigers> Please provide some kind of shell command which would allow me to answer your question sensibly
Dec 15 00:55:21 <bluelightning> Smigers: rpm -qa | grep libX11.*686
Dec 15 00:55:32 <bluelightning> Smigers: or actually, rpm -qa | grep libX11
Dec 15 02:15:02 <bluelightning> well, FWIW I was able to build qemu-native on my F19 VM here...
Dec 15 02:15:12 * bluelightning needs sleep
**** ENDING LOGGING AT Sun Dec 15 03:00:00 2013