<OriansJ>I am in the process of writing a self bootstrapping hex assembler who's only dependency is itself, I was hoping to help the reproducible build process by reducing the number of binaries that have to be trusted to 1 in the case of C. A 1416 Byte Hex file that produces a hex assembler that is exactly half that size.
<OriansJ>I have already written it in assembly but thus far have only made it for AMD64
<OriansJ>To have it compile, one needs only hex < Sourcefile.hex > binary
<OriansJ>It supports line comments and is case insensitive, for testing and validation; I have created its partner program which converts any file to its hex equivelent. That too has been written in assembly
<sneek>civodul, ng0 says: Okay, thanks. I see how and if I can or want to mirror this (a fix would be if there already was a .onion of the whole gnu.org/s/ space.. partyvan.eu has a mirror, but i haven't checked for /s/guix
<OriansJ>Well I feel guix needs a lower level bootstrap, so I am working on that. [Hand assembled Hex eats time] But if someone feels like getting guix to support network proxies, I would appreciate it.
<jmd>In 4 days, I have found lots of issues, which render it essentially unusable, except for VERY trivial uses. If there had been continuous work over 10 years these would have inevitably been discovered and fixed.
<rain1>but it's just so strange to me that I'm trying to be positive and helpful with this and you keep telling me that I am wrong
<jmd>Odd. I got the feeling you were continually tell me that I'm wrong.
<mark_weaver>rain1: on Guix, you normally need to use the ld within 'ld-wrapper', which automatically adds rpaths to the linker command line so that the built executable can find its shared libraries in the non-standard places
<mark_weaver>rain1: it's best to use 'gcc-toolchain', which includes gcc, binutils, glibc, and ld-wrapper