From: dharshana <slimk2004@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: Xen XCI Build fails with trousers-0.3.2-1
Date: Tue, 16 Mar 2010 00:13:58 -0700 (PDT) [thread overview]
Message-ID: <27914169.post@talk.nabble.com> (raw)
In-Reply-To: <27887567.post@talk.nabble.com>
Hello gollum1,
Thank you so much for your reply. I tried what you have mentioned here, but
again the problem was there. Then i tried to use gcc3.4.1 (the latest one)
when i do the "make oldconfig" menu selection. But still the problem was
there, so i tried to atleast compile the trouser 0.3.4 alone and still it
failed. I think i'm missing some packages to compile trousers.
*** I have done this compilation inside a 32 bit debian guest running on top
of xen 3.4 since my dom 0 is a 64bit debian. (XCI cannot built on top of
64bit as they mention in their page, again i tried it but cant)
Have you done the make in a dedicated host ? what is the architecture( is it
a single core or a dual core)? and if you can please attach the out put of
$ dpkg -l > abc.txt since i do believe i am missing some packages here.
Thank you,
dharshana
gollum1 wrote:
>
> Hallo dharshana
>
> i had exactly the same problem, I fixed it by takeing the newest trousers
> 0.3.4 version. (change the .mk file)
>
> But after i run the make process again i had a error with the patch
> installation. But i think with the new version the patch is nomore needed.
> So i created the hidden file .stamp_patched into the
> /build/build_i686/trousers-0.3.4 Folder.
>
> So it works now !
>
>
>
> dharshana wrote:
>>
>> Hi,
>>
>> I'm trying to build xen xci through the source, and everything went so
>> perfect until i got some troubles with trousers package.
>>
>> include -Os -I/usr/src/build/build_i686/staging_dir/usr/include
>> -I/usr/src/build/build_i686/staging_dir/include
>> --sysroot=/usr/src/build/build_i686/staging_dir/ -isysroot
>> /usr/src/build/build_i686/staging_dir -mtune=i686 -march=i686
>> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -ggdb
>> -DBI_OPENSSL -I../include -W -Wall -Werror -Wno-unused-parameter
>> -Wsign-compare -DTCSD_DEFAULT_PORT=30003 -DTSS_VER_MAJOR=0
>> -DTSS_VER_MINOR=3 -DTSS_SPEC_MAJOR=1 -DTSS_SPEC_MINOR=2 -MT
>> ps_inspect-ps_inspect.o -MD -MP -MF .deps/ps_inspect-ps_inspect.Tpo -c -o
>> ps_inspect-ps_inspect.o `test -f 'ps_inspect.c' || echo './'`ps_inspect.c
>> cc1: warnings being treated as errors
>> ps_inspect.c: In function ‘main’:
>> ps_inspect.c:342: warning: format ‘%ld’ expects type ‘long int’, but
>> argument 3 has type ‘off_t’
>> make[2]: *** [ps_inspect-ps_inspect.o] Error 1
>> make[2]: Leaving directory
>> `/usr/src/build/build_i686/trousers-0.3.2-1/tools'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/usr/src/build/build_i686/trousers-0.3.2-1'
>> make: *** [/usr/src/build/build_i686/trousers-0.3.2-1/.stamp_built] Error
>> 2
>>
>> Please help me with this...:-((
>>
>
>
--
View this message in context: http://old.nabble.com/Xen-XCI-Build-fails-with-trousers-0.3.2-1-tp27764652p27914169.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
prev parent reply other threads:[~2010-03-16 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 6:25 Xen XCI Build fails with trousers-0.3.2-1 dharshana
2010-03-13 13:34 ` gollum1
2010-03-15 11:47 ` gollum1
2010-03-16 7:18 ` dharshana
2010-03-16 7:13 ` dharshana [this message]
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=27914169.post@talk.nabble.com \
--to=slimk2004@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 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.