From: Wei Liu <wei.liu2@citrix.com>
To: Safa Hamza <safahamza1@gmail.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: error while compiling Xen from the source
Date: Fri, 10 Jun 2016 16:11:17 +0100 [thread overview]
Message-ID: <20160610151117.GL28116@citrix.com> (raw)
In-Reply-To: <CAFwQ9hFZ0AmCPgBXa8ORHn27VF2-oR5jcsfuwSbo7aNyhfoggw@mail.gmail.com>
On Fri, Jun 10, 2016 at 04:03:30PM +0100, Safa Hamza wrote:
> i'm really confused
> i build xen from the source in pc running ubuntu mate but while trying to
> do the same steps in order to build xen on other pc running 12.04 i got
> this error
>
> this is the log where xen is build successfully
>
> checking for python-config... /usr/bin/python-config
> checking Python.h usability... yes
> checking Python.h presence... yes
> checking for Python.h... yes
> checking for PyArg_ParseTuple in -lpython2.7... yes
> checking whether Python setup.py brokenly enables -D_FORTIFY_SOURCE... yes
> checking for xgettext... /usr/bin/xgettext
> checking for iasl... /usr/bin/iasl
> checking uuid/uuid.h usability... yes
> checking uuid/uuid.h presence... yes
> checking for uuid/uuid.h... yes
>
>
>
> *checking for uuid_clear in -luuid... yeschecking uuid.h usability...
> nochecking uuid.h presence... nochecking for uuid.h... no*
> checking curses.h usability... yes
> checking curses.h presence... yes
> checking for curses.h... yes
> checking for clear in -lcurses... yes
> checking ncurses.h usability... yes
> checking ncurses.h presence... yes
> checking for ncurses.h... yes
>
> and this is the log where the error is shown
>
> checking uuid/uuid.h usability... yes
> > checking uuid/uuid.h presence... yes
> > checking for uuid/uuid.h... yes
> >
>
>
> *checking for uuid_clear in -luuid... no > checking uuid.h usability... no
> > checking uuid.h presence... no > checking for uuid.h... no*
> > configure: error: cannot find a valid uuid library
> > configure: error: ./configure failed for tools
> >
>
> the problem is there is no difference
>
The only way to find out what went wrong is to dig into all the
configure output files. And then take appropriate steps to fix your
system.
If you're not very familiar with GNU autotools I suggest you go get some
advice from people in your local area who might be comfortable working
with a Linux system and building software from source.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-10 15:11 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 [this message]
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=20160610151117.GL28116@citrix.com \
--to=wei.liu2@citrix.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).