From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Trying to compile Xen 4 for a Debian package fail
Date: Fri, 16 Apr 2010 18:47:00 +0100 [thread overview]
Message-ID: <C7EE6124.11828%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <j2t6b7f6eb1004160931s93886d6fh7cfda819cfd4f02f@mail.gmail.com>
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@gmail.com>
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@eu.citrix.com>
>> 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@gmail.com>
>> 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
>>
>>
>
>
next prev parent reply other threads:[~2010-04-16 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 6:09 Trying to compile Xen 4 for a Debian package fail Martinx - ジェームズ
2010-04-16 6:33 ` Keir Fraser
2010-04-16 16:31 ` Martinx - ジェームズ
2010-04-16 17:47 ` Keir Fraser [this message]
2010-04-16 18:23 ` Martinx - ジェームズ
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=C7EE6124.11828%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=thiagocmartinsc@gmail.com \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).