xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Safa Hamza <safahamza1@gmail.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Subject: error while compiling Xen from the source
Date: Thu, 2 Jun 2016 16:22:25 +0100	[thread overview]
Message-ID: <CAFwQ9hGSk3L4v-S3xVjC=LqbV4SyVDM0p-hP5PzCguV-=OexDw@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1583 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 1810 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2016-06-02 15:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 15:22 Safa Hamza [this message]
2016-06-02 15:26 ` error while compiling Xen from the source 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

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='CAFwQ9hGSk3L4v-S3xVjC=LqbV4SyVDM0p-hP5PzCguV-=OexDw@mail.gmail.com' \
    --to=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).