From: Meng Xu <xumengpanda@gmail.com>
To: Safa Hamza <safahamza1@gmail.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: error while compiling Xen from the source
Date: Wed, 15 Jun 2016 11:32:15 -0400 [thread overview]
Message-ID: <CAENZ-+m4-3JrcwVtHA9DJw31Env3LShH8OC7C2WZFY1x7u+CCA@mail.gmail.com> (raw)
In-Reply-To: <CAFwQ9hGSk3L4v-S3xVjC=LqbV4SyVDM0p-hP5PzCguV-=OexDw@mail.gmail.com>
On Thu, Jun 2, 2016 at 11:22 AM, Safa Hamza <safahamza1@gmail.com> wrote:
> hello
> in order to build Xen from the source on my host (Intel x86-x64 running
> Ubuntu mate)
> I downloaded Xen Source Code from
> git clone git://xenbits.xen.org/xen.git then
> git checkout -b RELEASE-4.3.1 RELEASE-4.3.1
> I configured it successfully but when I want to compiled, an error showed up
>
>
>
> cc1: all warnings being treated as errors
> /home/safa/xen/tools/blktap/drivers/../../../tools/Rules.mk:89: recipe for
> target 'block-qcow.o' failed
> make[5]: *** [block-qcow.o] Error 1
> make[5]: Leaving directory '/home/safa/xen/tools/blktap/drivers'
> /home/safa/xen/tools/blktap/../../tools/Rules.mk:105: recipe for target
> 'subdir-install-drivers' failed
> make[4]: *** [subdir-install-drivers] Error 2
> make[4]: Leaving directory '/home/safa/xen/tools/blktap'
> /home/safa/xen/tools/blktap/../../tools/Rules.mk:100: recipe for target
> 'subdirs-install' failed
> make[3]: *** [subdirs-install] Error 2
> make[3]: Leaving directory '/home/safa/xen/tools/blktap'
> /home/safa/xen/tools/../tools/Rules.mk:105: recipe for target
> 'subdir-install-blktap' failed
> make[2]: *** [subdir-install-blktap] Error 2
> make[2]: Leaving directory '/home/safa/xen/tools'
> /home/safa/xen/tools/../tools/Rules.mk:100: recipe for target
> 'subdirs-install' failed
> make[1]: *** [subdirs-install] Error 2
> make[1]: Leaving directory '/home/safa/xen/tools'
> Makefile:74: recipe for target 'install-tools' failed
> make: *** [install-tools] Error 2
>
>
> how can I fix it... it may be a missing package!! I didn't find the
> solution after spending a long time googling
> i I’ll appreciate your help
>
There is a video about how to install RT-Xen at [1]. Since the
installation of RT-Xen and Xen are exactly same, you may want to have
a look and follow the video's instruciton. Hopefully it will be
helpful..
https://www.youtube.com/watch?v=PCIG5clWROo
Best,
Meng
-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-06-15 15:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 15:22 error while compiling Xen from the source Safa Hamza
2016-06-02 15:26 ` Wei Liu
2016-06-03 15:21 ` Safa Hamza
2016-06-03 15:23 ` Wei Liu
2016-06-10 12:03 ` Safa Hamza
2016-06-10 13:23 ` Wei Liu
2016-06-10 13:53 ` Safa Hamza
2016-06-10 14:25 ` Safa Hamza
2016-06-10 14:33 ` Wei Liu
2016-06-10 14:41 ` Safa Hamza
2016-06-10 14:47 ` Wei Liu
2016-06-10 15:03 ` Safa Hamza
2016-06-10 15:11 ` Wei Liu
2016-06-15 15:07 ` Konrad Rzeszutek Wilk
2016-06-15 15:26 ` Wim ten Have
2016-06-15 16:11 ` Wei Liu
2016-06-15 16:34 ` Konrad Rzeszutek Wilk
2016-06-15 17:11 ` Wim ten Have
2016-06-15 15:32 ` Meng Xu [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=CAENZ-+m4-3JrcwVtHA9DJw31Env3LShH8OC7C2WZFY1x7u+CCA@mail.gmail.com \
--to=xumengpanda@gmail.com \
--cc=safahamza1@gmail.com \
--cc=xen-devel@lists.xenproject.org \
/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).