According to generated 'configure' the option should not be needed. --with-libtool-sysroot=DIR Search for dependent libraries within DIR (or the compiler's sysroot if not

Yes, in my case the script sourced also resolves the path correct to CONFIGURE_FLAGS, but that is not automatically used by a generated configure script is it!? I guess that is why I need to add it

In my case '--with-libtool-sysroot' is correctly resolved by the SDK setup, but ./configure complains it does not recognize it, so I end up not being able to test generated (dynamically linked)

The '='-sign is still a mystery to me. But it does not seem to matter much. If I configure my packages (built from the SDK toolchain)

Hi. I recently discovered that our populated SDK can not properly build much at all :( libtool complains about .la files that have been moved and not being able to find dito. The rootfs builds fine

Sorry, my setup is a RAID0 striped SSDx2 configuration as well, not RAID1. I have a 3TB standard drive for performing backup, since I can lose data anytime, if any one of the drives fail. The cooling

Very interesting figures indeed. Not sure about the water cooling stuff, does that come in "standard", or did you build and tweak your server yourself? Up to now, I was thinking about an off-the-shelf

No problem, at least it forces me to look at RAID-5, RAID-1 and now RAID-0, thanks! ;)

Attendees: Nitin, JeffP, Belen, Cristiana, AlexD, AlexG, Paul, Saul, Richard, TomZ, Belen, DaveST, Corneliu, LaurentiuP, Jefro, ScottR, Björn, PeterB, Jessica, MatthewW, Bruce, Eren, MihaiL,

Attendees: Nitin, JeffP, Belen, Cristiana, AlexD, AlexG, Paul, Saul, Richard, TomZ, Belen, DaveST, Corneliu, LaurentiuP, Jefro, ScottR, Björn, PeterB, Jessica, MatthewW, Bruce, Eren, MihaiL,

Dear List, I try to build lttng by calling the package group for profiling, and I've got this error: Does anyone has tried profile package group lately? ERROR: Error executing a python function in

That's basically the spec I run (water cooling also keeps the noise down!). I generally get build times of just over 50 minutes for my system which has 'X' / GLES / Boost with something like 5500

Did you see my correction to this? I meant to say RAID 0. Sorry for the confusion. Running from RAM would be fastest - it really comes down to how much you have and how much you want to keep. That

Quite right. That'll teach me to hack out an e-mail late at night whilst packing for a road-trip :-( I meant to say RAID 0. No, mainly because two SSDs for RAID 0 was enough cash to spend ;-) Chris

Hello, The latest point release of the Yocto Project, 1.4.2 (dylan 9.0.2) is now available for download

The trend graphs for work week 35 have been updated automatically at https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend. The weighted defect density increased from last week's 1537 to 1643, the report

If you need it in the SDK, then absolutely. The other options to solve this issue for tightly coupled packages is to have them look at the kernel source directly (the staged version), since by

<bruce.ashfield@...> wrote: Definitely not. This is a unique header bound to a kernel module that is needed by user-space for ioctl() handling etc. In this case I think /usr/include/linux is

Read https://bugzilla.yoctoproject.org/show_bug.cgi?id=4102 maybe it's the same cause and find command in last comment will help you. -- Martin 'JaMa' Jansa jabber: Martin.Jansa@...