extract_firmware breaks on OS X Lion

[GoogleCodeExporter]

What steps will reproduce the problem?

1. svn checkout http://firmware-mod-kit.googlecode.com/svn/trunk/ 
firmware-mod-kit-read-only
2. cd  firmware-mod-kit-read-only/trunk
3. ./extract_firmware.sh ~/Downloads/tomato.trx ~/custom-tomato

What is the expected output? 

    successfully extracted tomato.trx to ~/custom-tomato

What do you see instead?

    coolaj86@AJs-MacBook-Air:trunk $ cat extract.log 
    gcc -I. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -O2   -c -o asustrx.o asustrx.c
    asustrx.c:74:24: error: ppc/endian.h: No such file or directory
    asustrx.c: In function ‘main’:
    asustrx.c:291: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘long unsigned int’
    asustrx.c:291: warning: format ‘%d’ expects type ‘int’, but argument 5 has type ‘long unsigned int’
    make: *** [asustrx.o] Error 1
    coolaj86@AJs-MacBook-Air:trunk $ arch
    i386

What version of the product are you using?

    trunk

On what operating system?

    OS X Lion

Please provide any additional information below.

It's probably about time to drop OS X PPC support altogether isn't it?
Who's using a mac from before 2005 these days? I guess there are still a few, 
but it seems that most mac people upgrade every few years or run Linux.

Original issue reported on code.google.com by coola...@gmail.com on 26 Sep 2011 at 8:00

[GoogleCodeExporter]

Accepted, but low priority; will fix when I get time.

Original comment by heffne...@gmail.com on 9 Oct 2011 at 2:50

• Changed state: Accepted

[GoogleCodeExporter]

I saw we should NEVER worry with this UNLESS we get some new contributor who 
actually has an OS X box and wants to keep it maintained. After all, people can 
run a linux distro in a VM ...

Original comment by jeremy.collake@gmail.com on 10 Oct 2011 at 8:39

[GoogleCodeExporter]

Yes, we had said that previously, but you sent me an email about this which I 
took as an indication that you wanted it fixed. :)

If that wasn't your intention, then we should: 1) Drop OS X support altogether, 
or 2) Leave this open until we or someone else can fix and maintain it. I'm 
fine with either, but personally lean towards #1.

Original comment by heffne...@gmail.com on 10 Oct 2011 at 8:49

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Other comments deleted for clarity.

Agreed. For now, OS X support removed. Recommendation for users is install 
Ubuntu in a VM (free, free).

Original comment by jeremy.collake@gmail.com on 10 Oct 2011 at 9:45

[GoogleCodeExporter]

Gotcha, sorry for the confusion. I'll clean out any lingering OS X specific 
stuff in the code and add an explicit statement in the wiki that only Linux is 
supported.

Original comment by heffne...@gmail.com on 10 Oct 2011 at 10:28

[GoogleCodeExporter]

Thanks, likewise I'll update the old docs on bitsum.com to say no OS X .. 

Original comment by jeremy.collake@gmail.com on 10 Oct 2011 at 10:40

[GoogleCodeExporter]

Done.

Original comment by heffne...@gmail.com on 12 Oct 2011 at 1:14

• Changed state: WontFix