Matthew Lye wrote: > Hey, > > Putting the GUID debacle behind us. Ahem. > > I've been noticing this lately, so I ran build.sh for a 'clean' (un- > fiddled with) version of GTKG, and got the same error. Basically, the > __powerpc__ token isn't defined on my machine.
You can peek at such definitions like this: echo | gcc -E -g3 - I guess your system defined __ppc__ and it should be semantically equivalent to __powerpc__, except for endianness maybe but that doesn't matter here. > I don't know when or > how in the compile this is supposed to happen, nor how to track it > down, but I suspect that (a) gcc-darwin uses a different token for the > processor or (b) this breaks compiles which are optimized for a > particular PPC chip. [This last point just occurred to me.] > > For myself, I just threw in > > #define __powerppc__ > right before the IEEE 754 check, and everything worked fine. That's not recommendable. -- Christian ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ gtk-gnutella-devel mailing list gtk-gnutella-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
