I'm working on compiling CodeBlocks on mac OS X 10.4 Intel. I must be the only one to ever try this because it's totally broken on 10.4 due to the change in vesions to GCC. Autotools are passing the wrong options to build a library causing the compile to annilate itself. Since the hack of a package causes Mac OS X not to recongize it's a Rosetta binary, it fails to laucnh all together. Autotools needs to be upgraded to 1.9 or badly hacked to build.
That being said, why the hell are we using autotools, it's one of the worst POSes these days.
EDIT: Ok, I mutated libtool, and made a few code patches in place, and got it to build a i686-apple-darwin binary. Since so few of us have Intel macs, I'll make it a universal binary, give me a minute.
EDIT 2.0: Ugh. Some of my system tools built against non-universal binaries, I'm going to have to do massive work to make this compile properly as a universal binary. I should be able to do a seperate PPC binary build though.
EDIT 3.0: It seems only wxMac is actually failing a universal binary build, it's got an XCode project file, so I'm trying to use that. With any luck, I can them simply recompile CodeBlocks for a universal binary
EDIT 4.0: wxMac's XCode project is broken, it doesn't properly build a dymanic library (it fails out of linking). I tweaked its configure scripts a tad, and built universal binaries (;-). Unfortunity, Code::Blocks, when seeing the powerpc compiler (or maybe this is libtool/autotools) tries to create a universal binary, but not all if properly compiles. I'm going to use lipo to stick all the bits together.