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

Nixpkgs’s pkgsi686Linux.nodejs package fails to build on x86_64-linux with bcachefs #813

Open
Jayman2000 opened this issue Jan 9, 2025 · 0 comments

Comments

@Jayman2000
Copy link

Jayman2000 commented Jan 9, 2025

Steps to reproduce

  1. Make sure that you have the Nix package manager installed by running this command:

    nix-build --version

    If that command succeeds, then you’re good to go. If that command fails, then you need to install the Nix package manager.

  2. Make sure that you’re on an x86_64-linux system by running this command:

    nix-instantiate --eval --expr 'assert builtins.currentSystem == "x86_64-linux"; "You’re using the correct type of system."'
  3. If you don’t already have one, then make a local clone of the Nixpkgs repo by running this command:

    git clone https://github.com/NixOS/nixpkgs
  4. Change directory into your clone of the Nixpkgs repo by running this command:

    cd <path-to-nixpkgs-repo>
  5. (Recommended) Switch to a Git commit where this problem is know to occur by running this command:

    git switch --detach 53ae2f054bfc06d82dcda03d921a94a675cc3ea2
  6. Try to build the pkgsi686Linux.nodejs package by running this command:

    nix-build -A pkgsi686Linux.nodejs

Results

When I try following the steps to reproduce on a bcachefs filesystem, the last command finishes with an exit status of 1, and prints instructions for how to retrieve a build log (link to log).

When I try following the steps to reproduce on an ext4 filesystem, the last command finishes with an exit status of 0.

Weirdly enough, Nixpkgs’s x86_64-linux version of the nodejs package builds fine on bcachefs. For whatever reason, building that package doesn’t trigger #809.

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

No branches or pull requests

1 participant