Xen Query ...

Xen Query ...

[Bruce Ashfield]

Hi all,

Just sending a question to see who else is building Xen from meta-virtualization
master against yocto/oe-core master ?

All my builds have been failing on eglibc after adding xen and aufs to
the DISTRO_FEATURES.
I've worked around the problem and converted them to IMAGE_FEATURES to get full
functionality, but I'm wondering if anyone else has seen this .. I
want to rule out my
build machine, and it being a one-off, before I dig any deeper.

Cheers,

Bruce


-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: Xen Query ...

[Chris Patterson]

[-- Attachment #1: Type: text/plain, Size: 2144 bytes --]

I did a couple of fresh builds yesterday against oe-core master without
issue (I do this pretty regularly...).

For the two distros that I build, they share:
DISTRO_FEATURES_append = " tpm txt usb3 xen opengl aufs "

Another build I do extends that even further.  They are regularly updated
to master on oe-core/meta-oe/meta-intel/meta-virtualization/meta-measured.

As another test, I took my existing "vanilla" build tree (nodistro, no
additional flags), created a new distro config and built xen-image-minimal:

oe-xen.conf:
DISTRO = "oe-xen"
DISTROOVERRIDES = ""
DISTRO_FEATURES_append = " xen aufs "

eglibc and the image built OK.

Then, in the same build tree, I went back to nodistro, with the same
DISTRO_FEATURES_append instead placed into local.conf.  eglibc and the
image built OK.

I will note that on occasion, I have seen the rare oddball errors (eglibc
sounds like a familiar one, but couldn't say for sure) - usually after a
substantial fetch and/or layer changes.  I've gone into the rabbit hole on
a couple of them without much success.  In all cases, wiping out
tmp/cache/sstate and starting fresh fixed the issues for me.

Out of curiosity, what's the error you are seeing?

Cheers,
-Chris

On Sat, Nov 16, 2013 at 10:42 PM, Bruce Ashfield
<bruce.ashfield@gmail.com>wrote:

> Hi all,
>
> Just sending a question to see who else is building Xen from
> meta-virtualization
> master against yocto/oe-core master ?
>
> All my builds have been failing on eglibc after adding xen and aufs to
> the DISTRO_FEATURES.
> I've worked around the problem and converted them to IMAGE_FEATURES to get
> full
> functionality, but I'm wondering if anyone else has seen this .. I
> want to rule out my
> build machine, and it being a one-off, before I dig any deeper.
>
> Cheers,
>
> Bruce
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization
>

[-- Attachment #2: Type: text/html, Size: 3532 bytes --]

Re: Xen Query ...

[Bruce Ashfield]

On Sun, Nov 17, 2013 at 3:58 PM, Chris Patterson <cjp256@gmail.com> wrote:
> I did a couple of fresh builds yesterday against oe-core master without
> issue (I do this pretty regularly...).
>

Excellent. First rule of debugging: if you see an error that is so
fundamental that
no one could possibly build .. assume that your environment is completely
tainted. Which was my starting assumption :)


> For the two distros that I build, they share:
> DISTRO_FEATURES_append = " tpm txt usb3 xen opengl aufs "
>
> Another build I do extends that even further.  They are regularly updated to
> master on oe-core/meta-oe/meta-intel/meta-virtualization/meta-measured.
>
> As another test, I took my existing "vanilla" build tree (nodistro, no
> additional flags), created a new distro config and built xen-image-minimal:
>
> oe-xen.conf:
> DISTRO = "oe-xen"
> DISTROOVERRIDES = ""
> DISTRO_FEATURES_append = " xen aufs "
>
> eglibc and the image built OK.
>
> Then, in the same build tree, I went back to nodistro, with the same
> DISTRO_FEATURES_append instead placed into local.conf.  eglibc and the image
> built OK.
>
> I will note that on occasion, I have seen the rare oddball errors (eglibc
> sounds like a familiar one, but couldn't say for sure) - usually after a
> substantial fetch and/or layer changes.  I've gone into the rabbit hole on a
> couple of them without much success.  In all cases, wiping out
> tmp/cache/sstate and starting fresh fixed the issues for me.

And the same thing with me. I've hit a few of these over the years, and when
the c library and toolchain builds go bad, I've never been able to sort them out
with clean and rebuilds. Only a full removal of tmp/. This time, I thought I'd
try and sort it out.

>
> Out of curiosity, what's the error you are seeing?

Here's the last snippet of the error:

86_64-poky-linux/eglibc/2.18-r0/build-x86_64-poky-linux/libc_pic.os:
relocation R_X86_64_PC32 against undefined hidden symbol
`__nss_not_use_nscd_group' can not be used when making a shared object
| /home/bruce/poky/build/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-poky-linux.gcc-cross-initial/gcc/x86_64-poky-linux/4.8.1/ld:
final link failed: Bad value
| collect2: error: ld returned 1 exit status
| make[2]: *** [/home/bruce/poky/build/tmp/work/x86_64-poky-linux/eglibc/2.18-r0/build-x86_64-poky-linux/libc.so]
Error 1
| make[2]: Leaving directory
`/home/bruce/poky/build/tmp/work/x86_64-poky-linux/eglibc/2.18-r0/eglibc-2.18/libc/elf'
| make[1]: *** [elf/subdir_lib] Error 2
| make[1]: Leaving directory
`/home/bruce/poky/build/tmp/work/x86_64-poky-linux/eglibc/2.18-r0/eglibc-2.18/libc'
| make: *** [all] Error 2
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.


Cheers,

Bruce

>
> Cheers,
> -Chris
>
> On Sat, Nov 16, 2013 at 10:42 PM, Bruce Ashfield <bruce.ashfield@gmail.com>
> wrote:
>>
>> Hi all,
>>
>> Just sending a question to see who else is building Xen from
>> meta-virtualization
>> master against yocto/oe-core master ?
>>
>> All my builds have been failing on eglibc after adding xen and aufs to
>> the DISTRO_FEATURES.
>> I've worked around the problem and converted them to IMAGE_FEATURES to get
>> full
>> functionality, but I'm wondering if anyone else has seen this .. I
>> want to rule out my
>> build machine, and it being a one-off, before I dig any deeper.
>>
>> Cheers,
>>
>> Bruce
>>
>>
>> --
>> "Thou shalt not follow the NULL pointer, for chaos and madness await
>> thee at its end"
>> _______________________________________________
>> meta-virtualization mailing list
>> meta-virtualization@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-virtualization
>
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: Xen Query ...

[Philip Tricca]

Morning Bruce,

On 11/16/2013 10:42 PM, Bruce Ashfield wrote:
> Just sending a question to see who else is building Xen from meta-virtualization
> master against yocto/oe-core master ?
> 
> All my builds have been failing on eglibc after adding xen and aufs to
> the DISTRO_FEATURES.
> I've worked around the problem and converted them to IMAGE_FEATURES to get full
> functionality, but I'm wondering if anyone else has seen this .. I
> want to rule out my
> build machine, and it being a one-off, before I dig any deeper.

I've not seen this in my builds (yet?). I generally pull from upstream
master oe-core/meta-oe/meta-selinux/meta-virtualization every day or two
so I'd expect I would have run into the same issue.

Got any build output?

Regards,
Philip