Package Details: xen 4.19.1pre-1

Git Clone URL: https://aur.archlinux.org/xen.git (read-only, click to copy)
Package Base: xen
Description: Open-source type-1 or baremetal hypervisor
Upstream URL: https://xenproject.org/
Keywords: hypervisor virtualization xen
Licenses: GPL2
Submitter: sergej
Maintainer: Refutationalist
Last Packager: Refutationalist
Votes: 185
Popularity: 0.67
First Submitted: 2009-11-09 11:22 (UTC)
Last Updated: 2024-09-20 00:31 (UTC)

Dependencies (63)

Sources (7)

Pinned Comments

Refutationalist commented on 2024-05-22 22:08 (UTC) (edited on 2024-05-23 00:07 (UTC) by Refutationalist)

As of now (2024-22-05) Xen with stubdom doesn't build because of a problem in the imported code. Been this way for about two weeks. Anyone else seeing this behavior?

Also, there is a lot of work happening on Xen in my development repo, thanks to @Serus. Check it out at: https://github.com/refutationalist/saur

Latest Comments

« First ‹ Previous 1 .. 27 28 29 30 31 32 33 34 35 36 37 .. 101 Next › Last »

KamijouTouma commented on 2016-01-18 08:12 (UTC)

checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... i686-xen-elf checking for a BSD-compatible install... /usr/bin/install -c checking whether ln works... yes checking whether ln -s works... yes checking for gcc... gcc checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. Makefile:83: recipe for target 'cross-root-i686/i686-xen-elf/lib/libc.a' failed make[1]: *** [cross-root-i686/i686-xen-elf/lib/libc.a] Error 77 make[1]: Leaving directory '/tmp/yaourt-tmp-kami/aur-xen/src/xen-4.5.1/stubdom' Makefile:73: recipe for target 'install-stubdom' failed make: *** [install-stubdom] Error 2 ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build xen. ==> Restart building xen ? [y/N]

alaricljs commented on 2016-01-05 22:09 (UTC)

Recently did an orphaned package cleanup and lost a couple of xen-required libs: #> pacman -Qi vde2 libnl |egrep "Name|Required" Name : vde2 Required By : None Name : libnl Required By : libpcap Without libnl 'xl -list' doesn't work (and no doubt more) Without vde2 hvm VMs don't work

jakogut commented on 2015-12-21 22:36 (UTC)

It seems binutils dropped support for PE binary linking, which broke the EFI binary generation in the Xen build process. The Fedora guys made a patch to replace it with mingw64, which you can find here: https://github.com/jakogut/xen-igvtg-aur/blob/master/xen_efi_build.patch

kline commented on 2015-12-17 04:19 (UTC) (edited on 2015-12-17 04:20 (UTC) by kline)

Did the xen-syms changes get worked into i686? Xen won't build right now on a pretty clean Arch install: http://pastebin.com/raw/SkCgkpNh

baratharon commented on 2015-11-30 07:09 (UTC)

I can compile and install it, thanks! Tested on up-to-date Arch x86_64.

bullekeup commented on 2015-11-29 19:47 (UTC)

If you want to try with the latest Xen release (4.5.2) and an updated PKGBUILD, I've put my modifications on my personal website and I'm waiting for feedback before requesting merging. It may solve some building issues encountered before and also enables OVMF support (tested on an Ubuntu 15.10 VM). https://www.bullekeup.net/files/arch/packages/xen/srctarballs/ xen-ovmf packages are intended for people who want a standard Bios Xen boot, xen-efi is for people who want to actually boot xen via efi. Last one needs a PEP enabled binutils, which PKGBUILD is available here : https://www.bullekeup.net/files/arch/packages/binutils-pep/srctarballs/

baratharon commented on 2015-11-22 18:01 (UTC)

Still, failed to build the package: checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... i686-xen-elf checking for a BSD-compatible install... /usr/bin/install -c checking whether ln works... yes checking whether ln -s works... yes checking for gcc... gcc checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. Makefile:83: recipe for target 'cross-root-i686/i686-xen-elf/lib/libc.a' failed make[1]: *** [cross-root-i686/i686-xen-elf/lib/libc.a] Error 77 make[1]: Leaving directory '/home/build/xen/src/xen-4.5.1/stubdom' Makefile:73: recipe for target 'install-stubdom' failed make: *** [install-stubdom] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

bullekeup commented on 2015-11-11 00:44 (UTC) (edited on 2015-11-13 00:24 (UTC) by bullekeup)

@ImATiger : I'm unable to reproduce the problem you encounter... I just have rebuild xen from scratch, just to be sure, no problem... Maybe a network problem ? (proxy, DNS, ...) @ata : You need to apply the patch supplied earlier (see previous comments) in order to be able to compile 32 bit executables. Or you can apply this patch for the PKGBUILD, with build dependencies on each package instead of multilib-devel meta package: --- PKGBUILD 2015-07-05 01:43:49.000000000 +0200 +++ PKGBUILD_new 2015-11-11 01:32:11.575921000 +0100 @@ -14,6 +14,7 @@ depends=(bridge-utils curl gnutls iproute2 libaio libcap-ng libiscsi libjpeg-turbo libpng libseccomp lzo2 nss pixman pciutils python python2 sdl yajl spice usbredir) [[ "$CARCH" == "x86_64" ]] && depends+=(lib32-glibc) makedepends=(bin86 cmake dev86 git iasl markdown ocaml-findlib figlet wget spice-protocol) +[[ "$CARCH" == "x86_64" ]] && makedepends+=(gcc-multilib lib32-fakeroot lib32-libltdl) optdepends=('xen-docs: Official Xen Documentation' 'openvswitch: Optional Networking support') conflicts=(xen-4.2{,-testing-hg} xen-{gdbsx,hg-unstable,rc,git} xen-4.3{,-testing-hg}) backup=(etc/modules-load.d/$pkgname.conf etc/$pkgname/xl.conf etc/conf.d/xen{stored,consoled,domains,commons} etc/$pkgname/grub.conf) @cokomoko : Have you enough RAM available to compile the package ? I had issues in the past with many packages because they were to heavy to be compiled in RAM and since yaourt works in RAM by default (tmpfs)... Maybe try compiling the package yourself outside /tmp ? If this is not the problem, I don't think it is linked with makepkg / AUR system (I personally have successfully build this package several times). Maybe try searching in Xen mailing lists, and report your issue upstream if needed.

ImATiger commented on 2015-11-10 04:26 (UTC)

I've been trying to build xen for a couple days. It times out trying to download from xenbits.xen.org. This is just to inform anyone who can fix it.

ata commented on 2015-11-08 16:47 (UTC)

checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... i686-xen-elf checking for a BSD-compatible install... /usr/bin/install -c checking whether ln works... yes checking whether ln -s works... yes checking for gcc... gcc checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. Makefile:83: recipe for target 'cross-root-i686/i686-xen-elf/lib/libc.a' failed make[1]: *** [cross-root-i686/i686-xen-elf/lib/libc.a] Error 77 make[1]: Leaving directory '/tmp/yaourt-tmp-ata/aur-xen/src/xen-4.5.1/stubdom' Makefile:73: recipe for target 'install-stubdom' failed make: *** [install-stubdom] Error 2 ==> HATA: build() içinde bir hata oluştu. Çıkılıyor... ==> HATA:makepkg xen'i inşa edemedi.