[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] [ARM][XSM][Building Problem][what is the matter to make problem?



Hello...

I tried to configure xen for ARM, but got failure on debian jessie(8.x version)

when executed "XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-linux-gnueabihf- debug=y XSM_ENABLE=y CONFIG_EARLY_PRINTK=lager ./configure", some package need to configure were installed. finally got the message like below.

.....<<..>>........

charles-debian@debian:~/charles-data/xen-4.6.0$ XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-linux-gnueabihf- debug=y XSM_ENABLE=y CONFIG_EARLY_PRINTK=lager ./configure
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
Will build the following subsystems:
 xen
 tools
 stubdom
 docs
configure: creating ./config.status
config.status: creating config/Toplevel.mk
config.status: creating config/Paths.mk
=== configuring in tools (/home/charles-debian/charles-data/xen-4.6.0/tools)
configure: running /bin/bash ./configure --disable-option-checking '--prefix=/usr/local'Â --cache-file=/dev/null --srcdir=.
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for bison... no
checking for flex... no
checking for perl... /usr/bin/perl
checking for awk... /usr/bin/awk
checking for ocamlc... no
checking for ocaml... no
checking for ocamldep... no
checking for ocamlmktop... no
checking for ocamlmklib... no
checking for ocamldoc... no
checking for ocamlbuild... no
checking for ocamlfind... no
checking for gawk... /usr/bin/awk
checking for checkpolicy... checkpolicy
checking for bash... /bin/bash
checking for python... /usr/bin/python
checking for python version >= 2.3 ... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
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 as86... /usr/bin/as86
checking for ld86... /usr/bin/ld86
checking for bcc... /usr/bin/bcc
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... yes
checking uuid.h usability... no
checking uuid.h presence... no
checking 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
checking for clear in -lncurses... yes
checking for define_key in -ltinfo... yes
checking for pkg-config... no
checking for glib... no
configure: error: in `/home/charles-debian/charles-data/xen-4.6.0/tools':
configure: error: The pkg-config script could not be found or is too old. Make sure it
is in your PATH or set the PKG_CONFIG environment variable to the full
path to pkg-config.

Alternatively, you may set the environment variables glib_CFLAGS
and glib_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

To get pkg-config, see <http://pkg-config.freedesktop.org/>.
See `config.log' for more details
configure: error: ./configure failed for tools

.....<<..>>........

I attached log file for configuration.

BR

Thanks.

2015-10-28 11:08 GMT+09:00 ììí <charlescho64@xxxxxxxxx>:
Hello

I have used ubunte14.04 system to build it and didnot modify anything before building. I tried to build using Debian Jessie.

BR

Thanks.

2015-10-27 0:35 GMT+09:00 Julien Grall <julien.grall@xxxxxxxxxx>:
On 26/10/15 02:52, ììí wrote:
> Hello..

Hello,

> /xen-4.6.0# make -C tools/flask/policy
> make: Entering directory
> `/home/charles/charles_data/Project/xen/lager/xen-4.6.0/tools/flask/policy'
> checkpolicy -t Xen -c 24 policy.conf -o xenpolicy-4.6.0
> checkpolicy:Â loading policy configuration from policy.conf
> policy.conf:1:ERROR 'syntax error' at token '' on line 1:

I've seen this error few month ago, but I can't remember how I fixed it.

FWIW, I don't have any issue to build the policy on Debian Jessie on
both ARM 32/64bits.

Can you give us the distribution your are using and if you modify Xen
before building the policy?

Regards,

--
Julien Grall



--
Happy Virus....
ì ìíÂ



--
Happy Virus....
ì ìíÂ

Attachment: config.log
Description: Text Data

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.