!LemuOOvbWqRXodtSsw:nixos.org

NixOS Reproducible Builds

539 Members
Report: https://reproducible.nixos.org Project progress: https://github.com/orgs/NixOS/projects/30125 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
12 Jul 2021
@hexa:lossy.networkhexathanks!17:04:51
@hexa:lossy.networkhexa
error: could not compile gkrust
17:34:36
@hexa:lossy.networkhexanot reproducible! :D17:34:41
17 Jul 2021
@mlieberman85:matrix.org@mlieberman85:matrix.org joined the room.04:07:23
@shadowninja55:matrix.org@shadowninja55:matrix.org joined the room.19:37:57
@shadowninja55:matrix.org@shadowninja55:matrix.org has anyone used tinycc? gcc seems to read NIX_CFLAGS_COMPILE or something that includes include paths, while tinycc is missing a ton and requires me to specify them manually. 19:38:44
@shadowninja55:matrix.org@shadowninja55:matrix.orgit makes me think tinycc on nixpkgs isn't wrapped correctly or something. 19:38:53
@shadowninja55:matrix.org@shadowninja55:matrix.org * it makes me think tinycc on nixpkgs isn't wrapped correctly or something.19:38:58
@shadowninja55:matrix.org@shadowninja55:matrix.org * it makes me think tinycc on nixpkgs isn't wrapped correctly or something19:39:00
18 Jul 2021
@yusdacra:nixos.devdusk joined the room.08:01:04
@yusdacra:tchncs.deyusdacra changed their profile picture.08:04:26
@dan:corne.co.ukdan joined the room.13:22:27
19 Jul 2021
@rgrunbla:matrix.orgReventlovRedacted or Malformed Event10:58:45
@rgrunbla:matrix.orgReventlovRedacted or Malformed Event10:58:59
@raboof:matrix.orgraboof
In reply to @rgrunbla:matrix.org
Is there some information somewhere about the minimal package set needed to bootstrap a nix system ?
I'm not aware of any, but agree it's interesting ;)
11:02:43
@rgrunbla:matrix.orgReventlovRedacted or Malformed Event11:03:00
@andi:kack.itandi-

You can look at the bootstrap tarball. From the top of my head those contain:

  • static busybox (with unxz, ash and tar applet in i686 mode but could be 64bit as well on x86)
  • patchelf to patch the binaries included in the tarball
  • glibc
  • a reduced set of GCC libs (for example the C++ std::fs .so is missing)
  • a version of bash, gzip, coreutils and i believe GNU make
11:31:25
@andi:kack.itandi- *

You can look at the bootstrap tarball. From the top of my head those contain:

  • static busybox (with unxz, ash and tar applet in i686 mode but could be 64bit as well on x86)
  • patchelf to patch the binaries included in the tarball
  • glibc
  • a reduced set of GCC libs (for example the C++ std::fs .so is missing)
  • a version of bash, gzip, coreutils and i believe GNU make
  • obviously a copy of glibc
11:31:54
@andi:kack.itandi-I've a branch where I tried to get rid of patchelf during the bootstrap phase we ca could use relative RPATHs.11:32:38
@andi:kack.itandi- * I've a branch where I tried to get rid of patchelf as during the bootstrap phase we can could use relative RPATHs.11:32:49
@andi:kack.itandi-That work ended up requriing patching each and every binary in the tarball (after unpacking) with a wrapper script that invokes the correct dynamic loader with them... Not sure how Guix gets around that issue of the bootstrap files requiring a dynamic loader.11:34:08
@andi:kack.itandi-All the talk about the minimal bootstrap are great but how do you execute the very first shell that you spawn you MES stuff with?11:34:40
@andi:kack.itandi- * All the talk about the minimal bootstrap are great but how do you execute the very first shell that you spawn your MES stuff with?11:34:49

Show newer messages


Back to Room ListRoom Version: 6