LiveCode Forums.

A swift reply:

From the screenshot, I see __LITTLE_ENDIAN__ defined but you're also building against the cached object files in .../i386/release... which may be why you're getting both BIG_ENDIAN and LITTLE_ENDIAN defined. Or that may be a red herring and i386 is just the default build directory in any case.

Are you issuing just a "make" command? If so, try

make clean
make all

I (rather obviously) don't have the linux-ppc include libraries installed here, so I can't follow along with you.

OK. Here, I think, is the problem:

Note that the PowerPC and Sparc chips are also switchable between Little Endian and Big Endian. However, the Apple PowerMac implementation of the PowerPC chip is stuck in Big Endian mode.

http://support.microsoft.com/kb/102025

So, while (on my system at least) /usr/include/bits/endian.h defines the byte order as little endian, the ppc code *must* be compiled as big endian. At this point, I'm confused, because in /usr/include/endian.h I see both LITTLE_ENDIAN and BIG_ENDIAN defined if __USE_BSD is defined, so I'm not sure why this should be a problem. (and the less said about PDP_ENDIAN the better)

This is the command I issued:

MODE=release make development

Make clean didn't do me much good either.

Looks like I'll need to do some tweaking of the header files to make sure things build on PowerPC - they probably assume all Linux builds are little-endian these days (and not very many people are familiar with the origin of those terms!). I'll let you know when I've made the changes.

The terms Big_Endian and Little-Endian come from Jonathan Swift's "Gulliver's Travels".

Here's a confusing picture.
I wonder what 'gcc' is, and how it should 'know'?

Hi-Ho, Hi-Ho, it's off to work we go!

Well; here I am over on my INTEL cooker while the MacMini does a system upgrade.

Anyway, I'm trying to track down 'gcc' and am getting badly confused as have found these directories:

/usr/lib/gcc/
/usr/libexec/gcc/

/usr/share/doc/gcc/

/usr/share/doc/gcc-4.8-base/gcc/

"usr/lib/gcc/" looks the most plausible as it contains directories that seem to make sense (even if one of them looks gae minging).

I will look in the equivalent directory over on the PPC in a while, and am wondering if the "clever" thing (cough, cough, cough) is to
remove any directories that seem to refer to Little Endian stuff.

Hi Richmond,

It is almost certainly a problem with the LiveCode source files rather than the system ones in /usr (i.e something I should probably fix). "GCC" is the name of the compiler that is most commonly used on Linux systems. I'm trying to get UbuntuPPC installed on my G5 but it isn't happy with it so it may take a while before I get a chance...

Fraser

Presumably it is "simply" a matter of commenting out some line in a document in the source files.

I may be talking complete rubbish, but I notice that when the Terminal "bailed out" it was here:
and I wonder if that is where to go hunting.

Well?

The funny thing is that 10.3.9 and so on makes me feel "all Macintoshy".

Commenting out the second line in "score,txt" (the one about INTEL 10.4.0) like this:
did not do much good:

At the risk of being accused of horrendous anthropomorphism:

I think that the Livecode code (LOL) has a problem; because on PPC, even though running Ubuntu 12.04 it seems to think
it is working under Mac OS:

Hi Richmond,

I can honestly say I have no idea what those score.txt files are! Could you alter your make command slightly when you run it:
Might give the build system the kick it needs to convince it to not do Intel-type things.

Yes, I'll give that a go.

However, my younger son, who has a fairly old Mac laptop has pinched the long LAN cable for a spot (his WiFi died in his laptop about 6 months ago).

So, "sexy screenshops' may have to wait a bit.