[SOLVED] Xen-tools fails to compile

[PeGa!]

Hi all!

I'm trying to build a custom AMI (amazon machine image) taking ideas from Gentoo's Xen Guide and a post on this forum.

I'm stuck building the custom kernel, mainly because xen-tools isn't able to compile.

So, I did an image (dd if=/dev/zero... etc), copied a stage3, portage, and everything else we know. When installing (inside the chroot) xen-tools, it failed:

Code: Select all

>>> Compiling source in /var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1 ...
make -j3 CC=x86_64-pc-linux-gnu-gcc LD=x86_64-pc-linux-gnu-ld -C tools 
make: Entering directory `/var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools'
make[1]: Entering directory `/var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools'
make -C check all
make[2]: Entering directory `/var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools/check'
PYTHON=python LIBXENAPI_BINDINGS=n ACM_SECURITY=n ./chk build
Xen CHECK-BUILD  Tue Apr 17 17:16:35 Local time zone must be set--see zic manual page 2012
Checking check_crypto_lib: OK
Checking check_curl: unused, OK
Checking check_openssl_devel: OK
Checking check_python: OK
Checking check_python_devel: 
 *** check_python_devel FAILED: can't find python devel files
Checking check_uuid_devel: OK
Checking check_xgettext: OK
Checking check_xml2: unused, OK
Checking check_zlib_devel: OK
Checking check_zlib_lib: OK
make[2]: *** [check-build] Error 1
make[2]: Leaving directory `/var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools/check'
make[1]: *** [subdir-all-check] Error 2
make[1]: Leaving directory `/var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools'
make: *** [subdirs-all] Error 2
make: Leaving directory `/var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools'
emake failed
 * ERROR: app-emulation/xen-tools-4.1.1-r6 failed (compile phase):
 *   compile failed
 * 
 * Call stack:
 *     ebuild.sh, line  85:  Called src_compile
 *   environment, line 4921:  Called die
 * The specific snippet of code:
 *       emake CC=$(tc-getCC) LD=$(tc-getLD) -C tools ${myopt} || die "compile failed";

I mounted /proc, /sys (filesystem sysfs), dev (with --rbind) and did env-update and sourced profile.

The image's profile:

Code: Select all

# eselect profile list|grep \*
  [8]   default/linux/amd64/10.0/server *

(I used a server profile just because I wanted a minimalist one)

Other than that, the new system is pretty default (as I previously said, just portage, tweaked some flags, emerged xen-sources, but I wasn't able to install xen-tools.

Just in case, emerge -pv xen-tools:

Code: Select all

[ebuild  N     ] app-emulation/xen-tools-4.1.1-r6  USE="-api -custom-cflags -debug -doc -flask -hvm -pygrub -qemu -screen -xend" 0 kB

What am I missing? I've read (on this forum) reports that xen-tools doesn't compile with gcc other than 4.1.1, but the post is pretty old.

Any hint?

Thanks in advance,

Paul.

[m47730]

i solved the same problem making python version 2 default

Code: Select all

$ eselect python list
Available Python interpreters:
  [1]   python2.7 *
  [2]   python3.2


$ eselect python set 1

[PeGa!]

m47730, you've made my day!

In order to add more data, I've pinpointed the exact file complaining about not finding that infamous "python_devel":

Code: Select all

/var/tmp/portage/app-emulation/xen-tools-4.1.1-r6/work/xen-4.1.1/tools/check

Here's its content:

Code: Select all

#!/bin/sh
# CHECK-BUILD

. ./funcs.sh

if test -z ${PYTHON}; then
  PYTHON=python
fi
has_or_fail ${PYTHON}

${PYTHON} -c '
import os.path, sys
for p in sys.path:
        if os.path.exists(p + "/config/Makefile"):
                sys.exit(0)
sys.exit(1)
' || fail "can't find python devel files"

I barely can read python, but I as far I can see, it is trying to verify some non-existent directories.

Again, m47730, thank you very much!

[m47730]

Yup. You found the guilty...
i tried to execute the code and with python2 it works, with python3 it fails.

i guess the reason is a behavior changes from version:

http://mail.python.org/pipermail/python ... 39985.html (seems the same problem)

i don't have the experience to make a patch for this check with python, but if someone could it will be cool!

Again, m47730, thank you very much!

you're welcome

[razamatan]

i went ahead and made a patch to make the 4.1.1-r6 ebuild force python2, and updated the tracking bug, so hopefully it gets into prod soon:

https://bugs.gentoo.org/show_bug.cgi?id=413493

if you're too impatient, feel free to apply yourself.

i don't have the experience to make a patch for this check with python, but if someone could it will be cool!