Something I’ve wanted to make work for a long, long time…
The Actors
$ uname -a Darwin bose 8.8.0 Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC Power Macintosh powerpc $ ssh artni uname -a Linux artni 2.6.16-1.2096_FC5smp #1 SMP Wed Apr 19 05:31:55 EDT 2006 i686 i686 i386 GNU/Linux $ _
The Production
$ make
i686-unknown-linux-gnu-gcc -static hello-kitty.c
-o hello-kitty
$ file hello-kitty
hello-kitty: ELF 32-bit LSB executable, Intel 80386,
version 1 (SYSV), for GNU/Linux 2.4.3,
statically linked, not stripped
$ _
Staging
$ scp hello-kitty artni:/tmp hello-kitty 100% 458KB 30.5KB/s $ _
Action!
$ ssh artni /tmp/hello-kitty Hello, kitty! $ _
Sweet! Woot! Special thanks to Dan Kegel for crosstool!
Now if only those Linux kids wouldn't make their filenames case-dependent.
(Foo.h and foo.h in the same directory, I mean, really!)
Congrats…but FYI regarding the Foo.h vs. foo.h:
Granted it takes special setup during (or before) install time, but for the past several years I’ve installed all of my Mac OS X boxes with a drive formatted to be “Mac OS Extended (Case-sensitive, Journaled)”. To do that at install time, after booting from the install DVD you can select Utilities->Disk Utility and use that to reformat the drive as desired. Quit out of that and resume the install as usual.
It has been a while since I saw any kind of issues with that either, right now the only app that I ever use that seems to have a problem is audicity (that I rarely use, I just run it from a case-insensitive dmg). Everything else I use seems to be written properly.
That’s a good tip. Sadly I’m not too keen to reinstall my 4 Mac OS X boxes, one of which has been through the entire trip from 10.2.8 to 10.4.8.
Once upon a time, installing with the case-sensitive FS was a sure fire way for death and mystery.
Perhaps it would be worth it, but it would represent a fair amount of pain. :-/
Sounds like a GREAT reason for a new Mac though ….