From: "David Nyström" <david.nystrom@enea.com>
To: "Prica, Mihai" <mihai.prica@intel.com>
Cc: "meta-virtualization@yoctoproject.org"
<meta-virtualization@yoctoproject.org>
Subject: Re: Meta-virtualization build
Date: Wed, 12 Dec 2012 10:51:15 +0100 [thread overview]
Message-ID: <50C85393.2070300@enea.com> (raw)
In-Reply-To: <97BD068FB200C44AA73C2B641F162ECF8F4FF0@IRSMSX101.ger.corp.intel.com>
Build Configuration:
BB_VERSION = "1.16.0"
TARGET_ARCH = "x86_64"
TARGET_OS = "linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "1.3"
TUNE_FEATURES = "m64"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp = "danny:27af23e65f63b41962a7cfddba9e9372d5212396"
meta-oe = "danny:f8ad0760abf8055bac27036853c56f56b40a36c7"
meta-virtualization = "nova:ab6b70a1f495f4ba5e2752878c2d37572cf59c4e"
Build of kvm image with your patches is successful with unmodificed
libvirt PACKAGECONFIG, when adding:
PACKAGECONFIG_pn-libvirt = "libvirtd remote qemu yajl test"
to local.conf and rebuilding.
I get errors below:
64/usr/lib/libgpg-error.so -lcap ../gnulib/lib/.libs/libgnu.a -lrt
-lpthread -lutil -ldl -pthread
|
/media/sdb5/eel/build/tmp/work/x86_64-poky-linux/libvirt-1.0.0-r0/libvirt-1.0.0/src/.libs/libvirt.so:
undefined reference to `vboxRegister'
|
/media/sdb5/eel/build/tmp/work/x86_64-poky-linux/libvirt-1.0.0-r0/libvirt-1.0.0/src/.libs/libvirt.so:
undefined reference to `openvzRegister'
|
/media/sdb5/eel/build/tmp/work/x86_64-poky-linux/libvirt-1.0.0-r0/libvirt-1.0.0/src/.libs/libvirt.so:
undefined reference to `curl_global_init'
|
/media/sdb5/eel/build/tmp/work/x86_64-poky-linux/libvirt-1.0.0-r0/libvirt-1.0.0/src/.libs/libvirt.so:
undefined reference to `esxRegister'
|
/media/sdb5/eel/build/tmp/work/x86_64-poky-linux/libvirt-1.0.0-r0/libvirt-1.0.0/src/.libs/libvirt.so:
undefined reference to `vmwareRegister'
| collect2: error: ld returned 1 exit status
After bitbake -c cleanall libvirt; bitbake libvirt;
Build is successful, with new packageconfig.
It seems rebuilds (from sstate ??) is not playing nicely with
PACKAGECONFIG modifications.
Br,
David
On 12/11/2012 03:30 PM, Prica, Mihai wrote:
>
> I tried with the PACKAGECONFIG you suggested and I get other errors, with an undefined reference. If I leave it in its initial form I get other errors from openbsd-netcat and netcf, but I think these are due to my proxy settings. I'll continue to look into these errors.
> I've attached you my patches for kvm. Can you apply them in your repo and see if the build succeeds ?
>
> Thanks,
> Mihai
>
> ________________________________________
> From: David Nyström [david.nystrom@enea.com]
> Sent: Tuesday, December 11, 2012 4:00 PM
> To: Prica, Mihai
> Cc: ray.danks@se-eng.com; bruce.ashfield@gmail.com
> Subject: Re: Meta-virtualization build
>
> Well,
>
> Setting packageconfig to only qemu might not be enough for libvirtd on KVM.
>
> Packageconfig "qemu" included --with-yajl in the old recipe, it does not
> in the new.
>
> OLD config line when setting "qemu" in packageconfig:
> EXTRA_OECONF = "--with-libvirtd --with-test=yes --with-remote=yes
> --with-macvtap=no --with-polkit=no"
> PACKAGECONFIG[qemu] = "--with-qemu --with-yajl, ......
>
> To get the same config line with libvirt_1.0.0.bb
>
> PACKAGECONFIG = "libvirtd remote qemu yajl test"
>
> Try setting packageconfig to above, when building qemu/kvm/libvirt 1.0
>
> Br,
> David
>
> How about if you build with no modifications
>
> On 12/11/2012 02:43 PM, Prica, Mihai wrote:
>> Hi,
>>
>> I tried now to build on a x86-64 target using a fresh poky repo(the latest) and I got the same error. I reverted the 2 commits and the build was successful. I set PACKAGECONFIG to "qemu" to build only for KVM.
>>
>> It seems like a libvirt error, I don't think it has anything to do with kvm.
>>
>> Thanks,
>> Mihai
>>
>>
>> ________________________________________
>> From: David Nyström [david.nystrom@enea.com]
>> Sent: Tuesday, December 11, 2012 2:37 PM
>> To: Prica, Mihai
>> Cc: ray.danks@se-eng.com; bruce.ashfield@gmail.com
>> Subject: Re: Meta-virtualization build
>>
>> Hi,
>>
>> I built for a x86-64 target,on danny branch and did not see this when
>> building, tested images using kvm on laptop.
>>
>> Try reverting commits:
>> 1c75f19747b91d5d9556aff20b0f740eeffd8028
>> c83fd72a864acdaf4f9790dbfd14c153ac0a1d4f
>>
>> and rebuild if you suspect the new libvirt additions.
>>
>> What changed did you make in poky ?
>> "mprica:b75157885432312bbdb3189acfb7adf3cdaf8b93"
>>
>> Br,
>> David
>>
>> On 12/11/2012 12:11 PM, Prica, Mihai wrote:
>>> Hi,
>>>
>>> I've developed some patches for KVM integration but I wasn't able to build an image because of an error at libvrit compile:
>>>
>>> | ../src/.libs/libvirt.so: undefined reference to `virNetTLSInit'
>>>
>>> don't think this is caused by my changes. Did meta-virtualization build ? This is my build configuration:
>>>
>>> BB_VERSION = "1.17.0"
>>> BUILD_SYS = "x86_64-linux"
>>> NATIVELSBSTRING = "Ubuntu-12.04"
>>> TARGET_SYS = "i586-poky-linux"
>>> MACHINE = "qemux86"
>>> DISTRO = "poky"
>>> DISTRO_VERSION = "1.3+snapshot-20121211"
>>> TUNE_FEATURES = "m32 i586"
>>> TARGET_FPU = ""
>>> meta
>>> meta-yocto
>>> meta-yocto-bsp = "mprica:b75157885432312bbdb3189acfb7adf3cdaf8b93"
>>> meta-oe = "master:c75fc2573b88576b577946ff834b10446e591532"
>>> meta-virtualization = "mihaip:7e9649d297ecddde556a0aa7ed1251e1a7279696"
>>>
>>> Thanks,
>>> Mihai
>>>
next parent reply other threads:[~2012-12-12 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <97BD068FB200C44AA73C2B641F162ECF8F4F22@IRSMSX101.ger.corp.intel.com>
[not found] ` <50C72905.7030003@enea.com>
[not found] ` <97BD068FB200C44AA73C2B641F162ECF8F4F6E@IRSMSX101.ger.corp.intel.com>
[not found] ` <50C73C64.5020702@enea.com>
[not found] ` <97BD068FB200C44AA73C2B641F162ECF8F4FF0@IRSMSX101.ger.corp.intel.com>
2012-12-12 9:51 ` David Nyström [this message]
2012-12-12 11:07 ` Meta-virtualization build Prica, Mihai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50C85393.2070300@enea.com \
--to=david.nystrom@enea.com \
--cc=meta-virtualization@yoctoproject.org \
--cc=mihai.prica@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.