News for hackers. Stuff that matters.
Re:Bootstrapping trust in compilers by jdudek on Tuesday December 08, 2015 @08:39AM (#10696227)
Pardon my ignorance, but why is cross-compilation not an option in this case?
Re:Bootstrapping trust in compilers by jperkin on Tuesday December 08, 2015 @10:12AM (#10696763)
Cross-compilation is sometimes an option, but not necessarily a good one.

It is usually a significantly manual process (I now have to download and install an OS which is supported by the runtime and build a cross-compiler for my target platform, which may or may not even be possible, or even work), isn't always supported by the runtime, usually requires changes to the build procedure, often requires special patches - and at the end of all that users are still left with either having to repeat all this themselves, or trust someone else's binary bootstrap.

Compared to a simple, portable, C-based bootstrap where any user can type 'make' and ensure provenance directly from source. For what gain?

Uninformed? Perhaps. I haven't designed and written my own language, and I'm certainly no expert. I'm just someone who gets asked to port these new languages to platforms which aren't Linux or OSX, and it's a lot of hard work. I just know that if I did it write my own it would look a lot more like perl/python/lua than ghc or go from a build perspective.

Re:Bootstrapping trust in compilers by e40 on Tuesday December 08, 2015 @09:02AM (#10696332)
It is and that's how it's done. The rant you replied to was just uninformed.
Re:Bootstrapping trust in compilers by nickpsecurity on Tuesday December 08, 2015 @10:00AM (#10696687)
Typically, yes. My method is for high trustworthiness but people merely concerned with reliability can do this. Got a tool that you've used to successfully make your other tools? Use it on the next tool. Crazy idea, eh?