Nikita Karetnikov <nik...@karetnikov.org> skribis: >> You could run ‘nix-build -A stdenv -K /path/to/nixpkgs’. Upon glibc >> build failure, just get into the failed build tree: > > Yep, it failed with the same error.
Then there may be something wrong with your setup, because glibc is known to build on Fuloong, right? We’d need to compare the derivation and output paths with Lluís, but I think you already did that. > make[2]: Nothing to be done for `subdir_lib'. > make[2]: Leaving directory > `/tmp/nix-build-46dkvs7arjnsb0073n603lr7c6r6wskl-glibc-2.13.drv-1/glibc-2.13/catgets' > building math/subdir_lib > smake subdir=math -C math ..=../ subdir_lib > make[1]: *** [math/subdir_lib] Killed > make[1]: Leaving directory > `/tmp/nix-build-46dkvs7arjnsb0073n603lr7c6r6wskl-glibc-2.13.drv-1/glibc-2.13' > make: *** [all] Error 2 Can you run ‘strace -f -o log make’ to see exactly what gets killed? (Do that in the build tree after having sourced ‘env-vars’.) > I've found some (probably related) links. [1,2] That seems different: they get an actual compiler error, whereas you get no error, just “Killed”. Ludo’.
