LiveCode Forums.

Definitely not.
Now if that's not a Barry Humphries moment I don't know what is.

Stomping off for a cup of coffee.

Well; editing Rodney did NO good at all:

So, the big and burning question is whether the Terminal output means:

a. That file is missing, or
b. That file has something wrong with it?

Certainly looks like the latter:

At which point the question is:

How does one generate this file?

St. Jude: the patron saint of lost causes
was not daft enough to try building things from
code on a Linux PPC box . . . LOL.

Richmond-

I'm going to recommend that the moderators move this thread down to the Engine Contributors section, as it has now veered off from being a feature request to being a full-blown experiment in creating a linux ppc build of the engine.

Next, I'd advise you to do the following before getting too involved in more work:
This will, in order:
save all the changes you've made so far,
revert back to the original download files
create a new git branch for your changes and go there
recover your changes into the new branch

What this will do is allow you to pull down more changes to the master branch as the rev team makes them without messing up the changes you're making. Otherwise you either run the risk of being stuck with the current master branch changes (6.5.2) or possibly having to resolve merge changes yourself (which isn't that bad but is probably a later git lesson).

Thanks Mark.

However, what with one thing and another very little is likely to happen further until Wednesday as I have a lot on my
plate between now and then.

Considering I did muck around with the 'Rodney' files, and move those files intil the thirdparty/engine directory and so on I was
a bit surprised at this:

And I always knew "Pop" was not a git, normally it's Grandpa who is a git, LOL:

Let's hope there is room on the broom for Linux PPC:

I hate git submodules, but we're stuck with that for the moment.
before issuing the git commands above. There's a separate git repository for the thirdparty libraries, and because thirdparty is a submodule of the livecode repository, it doesn't know (and doesn't have to know) about any changes there.

Aha: all I did was 'cd livecode'.

I wonder if "git pop" will bite?

Let you know in about 5 secs.

Um; still doesn't see all that keen on 'git pop':

Anyway; I'm off to bed as I have to be up "bright and early" tomorrow to
poison the minds of Bulgarian youth.

Obviously I am going to have to search through a very large number
of documents to track down the problem that switches are set to perform both a LITTLE_ENDIAN
and a BIG_ENDIAN build.

I'll probably meet Darth Vader, Sauromon and Vladimir Putin along the way.

I recently installed 2 applications for looking and fiddling around with code on my Linux INTEL box:
Code::Blocks IDE

and
CodeLite

and they look like jolly good stuff.

What I cannot work out is how to open /home/livecode in either of them.

They SHOULD make the whole exercise rather better, at least, possibly, in
doing searches for text strings (such as "LITTLE_ENDIAN" !) through
the whole stramash of directories with all their documents.