-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xen fails to build on unstable #108479
Comments
Actual error (from
Possibly triggered by the GCC 10 upgrade. |
@andersk I found this patch https://lists.ipxe.org/pipermail/ipxe-devel/2020-May/007047.html |
Also, it seems to me that |
Can confirm here, also I am bit confused too, in my case xen is failing to build for libguestfs which in turn is needed for vagrant, and I did not understand why, from a quick search Debian neither Arch uses xen as a dep in neither of this packages.
Will try. EDIT: For ref, Gentoo team bug report: https://bugs.gentoo.org/722930 (Already solved) |
I submitted a PR to remove Xen as dependency from Gnome-boxes. #108716 |
Guys I am a bit lost here, I failed to apply the patches here, one motive is that is for 4.13+ and we are in 4.10, other is the needed options for building in GCC10, I do not know exactly where to put it, based on the patches from Gentoo (xen-tools-4.13.0-gcc10.patch and xen-tools-4.13.0-ipxe-gcc10.patch, available here https://github.com/hydrapolic/gentoo-dist/blob/master/xen/xen-gentoo-patches-21.tar.xz and here https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ab132ad91fa4e41eca3bc48eebae586c6ba58a11) the IPXE one, set the CFLAGS for the whole project, for example:
The other patch changes some little things plus a modifies a CFLAG for a specific module:
But there is no definition for this in our makefile (source https://github.com/xen-project/xen/blob/stable-4.10/Makefile). I did try to add it on But adding
Without it, advances a lit bit more but also fails:
From a bit more of research, Vagrant depends on libguestfs because of the libvirt plugin, which in turn depends on xen, I think is better to version bump our xen then patches it for GCC10. For now I using |
If version bumping Xen fixes this, I can’t imagine a reason that wouldn’t be our first choice—we should do it. |
It will help, but we will still need patches for GCC10 until we have a release to address that (from upstream). At least that's what I understood by reading the issues and PR from the Gentoo team. |
Quick update, libguestfs doesn't need xen as a dependency, I'm trying to compile it without xen to allow vagrant and friends to build it again. EDIT: Reference https://libguestfs.org/guestfs-building.1.html |
Ok, the bump of autoconf to 2.70 also breaks building libguestfs on unstable, on 20.09 I can build libguestfs without xen and any problem. |
@bryanasdev000 I saw that autoconf needs this patch https://git.savannah.gnu.org/cgit/autoconf.git/commit/?h=branch-2.70&id=35b1708c3961dce31e4ce43014e71d77aa4b5e31 |
@bryanasdev000 I submitted a PR to remove Xen from libguestfs: #108882 I needed to change autoconf to version 2.64. |
I was just trying to force the build with an older version of autoconf, I tried to update libguestfs to version 1.44, it reduced the errors but it still did not build. Thanks! Excellent job! |
Guys with the fix of Vagrant (Libguestfs) I did not check Xen anymore, did anyone advance with that? If not I can try to mess with it, but somebody will need to test since I don't use Xen at all. |
Describe the bug
Xen is not building this is the error:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result."x86_64-linux"
Linux 5.10.4, NixOS, 21.03.20210104.1a57d96 (Okapi)
yes
yes
nix-env (Nix) 2.4pre20201201_5a6ddb3
"nixos-21.03pre250162.34ad166a830"
/etc/nixpkgs
Maintainer information:
The text was updated successfully, but these errors were encountered: