2008-11-10 23:10:10.213429+00 by Dan Lyke 6 comments
I think Worst. Bug. Ever. is a bit of an understatement, but if you have one of those new Google phones, don't text rm -rf /* until you update your firmware... Apparently the last line of the initrc brought up a shell in the background, and all user I/O went through the same device...
Which brings me to: Anyone got a favorite method for putting together an ARM GCC toolchain on Linux?
[ related topics: Free Software Open Source ]
comments in ascending chronological order (reverse):
#Comment Re: made: 2008-11-11 01:25:50.138528+00 by: Mark A. Hershberger
some thing like this?
http://arstechnica.com/journal...s/2008/11/10/debian-ported-to-g1
#Comment Re: made: 2008-11-11 01:27:15.117931+00 by: Mark A. Hershberger
Don't forget this, too: http://mjg59.livejournal.com/100221.html
#Comment Re: made: 2008-11-11 04:11:20.08836+00 by: Dan Lyke [edit history]
No, actually, much simpler: I just want to type arm-elf-gcc test.c. So, something more like this.
#Comment Re: made: 2008-11-11 11:17:32.275649+00 by: John Anderson
The "we got a git server in California" line in the LJ post Mark linked made me LOL.
#Comment Re: made: 2008-11-11 14:38:23.710067+00 by: Dan Lyke
Grins. Yeah, I didn't read that too closely, and it's worth reading.
Since my link up there earlier was bad: CodeSourcery has cross-compiled versions of the GCC toolchain, including bigger pay-for-support packages that include Eclipse and such, good for working with people who think VisualStudio is something other than the manifestation of the eldritch gods come to eat our souls.
The reason this is a deal is that compiling GCC has become a multi-stage poorly documented bootstrap involving a couple of libraries that don't come in the original tar, and appear to need a "wait for the main compile to error, go try to compile those with the partially compiled gcc, then come back" sort of process.
#Comment Re: made: 2008-11-11 20:59:22.113329+00 by: Dan Lyke
Oh, the tool I wanted is buildroot.