[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Trying to compile Xen 4 for a Debian package fail


  • To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • From: Martinx - ジェームズ <thiagocmartinsc@xxxxxxxxx>
  • Date: Fri, 16 Apr 2010 15:23:54 -0300
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Sun, 18 Apr 2010 08:47:55 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:x-goomoji-body:date :message-id:subject:to:cc:content-type; b=QgYIoNNKhsodU3p8NAJq/e73knU/NV+KXXNb5JdhinUvOgrcZdqkHMgECeKWL3Qc8c uzRYHRlrYkBg2ceh74ceo1KAQqlIRxxPdvoosA1UaLLm78sbtCcBcdGKXE6BgyGioQ6G 8M7wNSMcOweydxShzbuzGt2IY7GUkWMNJzndk=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Thank you again Keir!  

I have not applied any patch to the original Xen, I'm just trying to pack/compile the original xen-4.0.0.tar.gz (hypervisor, tools and docs) using the debian/rules makefile file.
I will investigate more deeply the order.

Cheers,
Thiago

2010/4/16 Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Okay, well then I can tell you that it is almost certainly a build-ordering
problem. Do your packages have patches on top of our build system? Because
we do parallel builds all the time and we would generally know pretty
quickly if our build dependencies and orderings are wrong.

 -- Keir

On 16/04/2010 17:31, "Martinx - ジェームズ" <thiagocmartinsc@xxxxxxxxx>
wrote:

> Well, thank you anyway Keir... But I'm the maintainer of this unofficial
> package... I
> just trying to do a new package based on my experiences with the Xen...
>
> Regards,
> Thiago
>
> 2010/4/16 Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
>> Could be a build ordering problem -- building blktap2 before the libxc
>> library that it depends on -- perhaps? Unless this reproducible on one of
>> our mainstream trees, this is an issue to report to the debian maintainer.
>>
>>  -- Keir
>>
>> On 16/04/2010 07:09, "Martinx - ジェームズ" <thiagocmartinsc@xxxxxxxxx>
>> wrote:
>>
>>> make -C lib all
>>> make[7]: Entering directory
>>> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blk
>>> ta
>>> p2/vhd/lib'
>>> make[7]: Nothing to be done for `all'.
>>> make[7]: Leaving directory
>>> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blk
>>> ta
>>> p2/vhd/lib'
>>> make[6]: Leaving directory
>>> `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blk
>>> ta
>>> p2/vhd'
>>> gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing
>>> -std=gnu99
>>> -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
>>> -D__XEN_TOOLS__ -MMD -MF .vhd-util.d -D_LARGEFILE_SOURCE
>>> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
>>> -mno-tls-direct-seg-refs -Werror -Wno-unused -I../include -D_GNU_SOURCE
>>> -Wp,-MD,.vhd-util.d -o vhd-util vhd-util.o           -L../../tools/libxc
>>> -lxenctrl    -L../../tools/libxc -lxenctrl    -Llib -lvhd -luuid
>>> /usr/bin/ld: cannot find -lxenctrl
>>> collect2: ld returned 1 exit status
>>
>>
>
>



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.