News for hackers. Stuff that matters.
Re:OS X Isn't for Developers by ironchef on Thursday March 10, 2011 @06:55PM (#2311349)
I don't get it. What's wrong with "sudo port install gcc46 ruby19 ruby186"?
Re:OS X Isn't for Developers by kluikens on Thursday March 10, 2011 @07:02PM (#2311376)
Assuming no other available build toolchain (e.g. Xcode 3), you won't have macports installed. How will you compile gcc, ruby if you don't already have a compiler?
Re:OS X Isn't for Developers by ironchef on Thursday March 10, 2011 @08:53PM (#2311784)
Got it...thanks. I didn't get that he was talking about the bootstrapping issue.
Re:OS X Isn't for Developers by tvon on Thursday March 10, 2011 @07:04PM (#2311384)
Well, I'm pretty sure gcc can bootstrap and self-compile, but I don't know if macports is setup for that.

edit: apparently it's not self-compiling, at least not in the way I was thinking.

Re:OS X Isn't for Developers by scott_s on Thursday March 10, 2011 @07:54PM (#2311588)
You need an initial compiler for the boostrapping process.

Obvious question: how did the first C compiler exist, then? Answer: it was implemented in assembly. And the first assembler was written in machine code.

Re:OS X Isn't for Developers by scott_s on Friday March 11, 2011 @12:07AM (#2312208)
It's been long enough that I can't edit what I wrote, but I forgot my history. The first C compiler was grown by modifying a B compiler that was implemented in B. That B compiler, however, was originally implemented in assembly: http://cm.bell-labs.com/cm/cs/who/dmr/chist.html
Re:OS X Isn't for Developers by Wientje on Friday March 11, 2011 @03:39AM (#2312695)
It kinda makes you think. If we delete all compilers in the world, there would be no easy way to make new compilers. It also means that your compiler on your PC can trace its heritage back to the first machine coed compiler ever written, like life itself evolving from one generation to the next.
Re:OS X Isn't for Developers by Locke1689 on Friday March 11, 2011 @05:38AM (#2312928)
You're basically just saying that if you delete all copies of X software in the world it would be really hard to recreate X software.

Anyway, writing a C-- compiler in x86 ASM isn't really that bad. It'd probably be even easier to run the compiler in an interpreter.

Re:OS X Isn't for Developers by scott_s on Friday March 11, 2011 @07:13AM (#2313074)
I was thinking of a similar orign-of-life analogy, but unlike life, compilers have sprung up independently of each other many times over. That is, in the early days, it was common to implement everything over again in assembly on a new machine.
Re:OS X Isn't for Developers by fpgeek on Thursday March 10, 2011 @07:45PM (#2311556)
Even gcc is not that metacircular. There needs to be some compiler at the bottom of the bootstrapping.
Re:OS X Isn't for Developers by k33l0r on Thursday March 10, 2011 @07:00PM (#2311367)
Because requiring yet another third party tool is just an extra barrier. And not everyone uses MacPorts anyway, personally I don't want to see MacPorts anywhere near my computer...
Re:OS X Isn't for Developers by jcapote on Thursday March 10, 2011 @07:03PM (#2311383)
Not to mention you need GCC to build GCC
Re:OS X Isn't for Developers by pohl on Thursday March 10, 2011 @07:31PM (#2311488)
Well,you would need some C compiler. You could build FCC with clang.