Skip to content
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

KDE won't build on i686 #195710

Closed
sg2002 opened this issue Oct 12, 2022 · 13 comments · Fixed by #192907 or #200670
Closed

KDE won't build on i686 #195710

sg2002 opened this issue Oct 12, 2022 · 13 comments · Fixed by #192907 or #200670
Labels

Comments

@sg2002
Copy link
Contributor

sg2002 commented Oct 12, 2022

Steps To Reproduce

Steps to reproduce the behavior:

  1. Try building KDE on i686 machine.

Build log

Build log is availible on Hydra

Additional context

I've been struggling with building KDE for a few recent NixOS versions. I've managed to get it running recently and made 2 MRs that fix it: #192903 and #192907. The first one was merged, while the other one wasn't.

Creating this as an issue to add as a 22.11 blocker to hopefully get KDE running on i686 in 22.11. Whether it is really a blocker and whether #192907 should be merged is up to the dev team to decide of course.

Notify maintainers

@NixOS/qt-kde

@sg2002 sg2002 added the 0.kind: build failure A package fails to build label Oct 12, 2022
@vcunat vcunat linked a pull request Oct 12, 2022 that will close this issue
14 tasks
@mweinelt
Copy link
Member

mweinelt commented Nov 2, 2022

I think it is time to let go of i686-linux. Keeping it around for wine/steam is fine, but we haven't even been able to build firefox for i686-linux since 2020.

@FRidh
Copy link
Member

FRidh commented Nov 2, 2022

Note we also have an RFC covering this. i686-linux is a tier 3 platform. Tier 3 platforms are non-blocking.
https://github.com/NixOS/rfcs/blob/553b132ca05e0ad19b563b80b08d17330df205cf/rfcs/0046-platform-support-tiers.md

@vcunat
Copy link
Member

vcunat commented Nov 2, 2022

The build log in OP is misleading, as that's from 22.05 and doesn't apply anymore. Here's a link that should work all the time:
https://hydra.nixos.org/job/nixos/trunk-combined/nixos.closures.kde.i686-linux

@sg2002
Copy link
Contributor Author

sg2002 commented Nov 2, 2022

The build log I've provided as an example of what's going on there in 22.05, the last stable version, trunk may or may not have some other issues on top of the ones present in 22.05, since it obviously changes all the time.

Since I'm commenting on this issue again, can someone elaborate on the existence of binary cache for i686? From what I could gather, even if we get Hydra jobs working correctly, the binary cache still wouldn't exist as it was disabled for the entire i686 architecture?

@vcunat
Copy link
Member

vcunat commented Nov 2, 2022

cache.nixos.org has everything that's built on Hydra.nixos.org. Immediately.

@sg2002
Copy link
Contributor Author

sg2002 commented Nov 2, 2022

I'm sorry, but I keep getting conflicting information on this and all of it got me somewhat confused.

What about Nix? If a binary cache for i686 should exist and I'm rebuilding Nixos from a local nixpkgs repo copy set to a revision already built Hydra, for example the latest 22.05 revision from status.nixos.org, it should not be building Nix from scratch, right? It should get it from the binary cache?

@vcunat
Copy link
Member

vcunat commented Nov 2, 2022

Yes, you do get it (just tried).

@sg2002
Copy link
Contributor Author

sg2002 commented Nov 2, 2022

Did you try it on i686? For some reason it's trying to build it from scratch for me.

@vcunat
Copy link
Member

vcunat commented Nov 2, 2022

I got i686-linux version of the nix attribute on the latest nixos-22.05 channel. You can download e.g. by

nix-store --realize -Q /nix/store/wxrffrz1kaqjrfm3fa16j2m30ddfvc7i-nix-2.8.1

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/nix-the-package-manager-itself-hydra-job/22928/3

@SuperSandro2000
Copy link
Member

Now upower fails to build.

Personally I don't think we need to support i686 beyond wine and steam because 4GB RAM is to little to run nix comfortable anyway and more and more upstream projects done support it.
I would vote for closing this.

@sg2002
Copy link
Contributor Author

sg2002 commented Nov 4, 2022

Upower issue is already reported upstream. Seems like some kind of Python integer precision issue, I'll make an MR to fix it.

@mweinelt
Copy link
Member

mweinelt commented Nov 4, 2022

A month ago with no reaction so far. Doesn't look promising. We could patch that test downstream, or disable the specific test, if the test runner supports that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
6 participants