Linux PPC build?

[richmond62]

Examining the "libcrypto.a" and "libcurl.a" in that directory (see picture above) shows me that
they are different things, despite having the same names. So, I jalouse that those are 32-bit Intel and 64-bit Intel versions;
and what I should be speirin after is 32-bit PPC versions.

So, after another cup of coffee, I shall charge up the MacMini (currently on the Intel Box) and see what Synaptic can cough up,
and or a general search within the file system.

[LCfraser]

Richmond -

Those files in /prebuilt/bin are old (Revolution 2.x, I believe) versions of the engine. They are used to run a couple of scripts to generate things such as the error message tables and a hash table to speed up the parser. Way back in the mists of time (i.e the beginning of this thread ) I mentioned a few files that need to be copied over from an Intel box - if you copy them and then run the "touch" command on each of them, the Make process won't try to run the old engines because it sees the generated files as being up-to-date. (This is the process I use when I'm daft enough to build LiveCode on a RaspberryPi).

That should at least get you a bit further. I think there will be a few additional problems further on when it tries to link to some of the prebuilt libraries but, as a friend of mine says, we can burn that bridge when we get to it!

[richmond62]

Well I did copy the files over from the Intel machine, but didn't 'touch' them.

So, I had better do that.

[richmond62]

Learning as I go along :/

touching.png

[richmond62]

AS usual (n Bulgaria, at least) everything took longer than planned: accountant, haircut

Back on task; just did the 'touchy-feely' bits:

touchingUp.png

while LXDE is jolly useful for under-powered machines such as my MacMini it does not allow drag-and-drop onto the Terminal,
so I have to type each pathway explicitly.

[richmond62]

So, here I am on the Intel Box while the MacMini chews its way through another attempt at a build.

I do wish I had a faster machine; and I must say that I cannot quite understand why Ubuntu + LXDE should be so clunky
compared with Mac OS 10.4.11.

Obviously people (such as myself) who want to run G3 iMacs with some type of PPC Linux that is relatively current
( and that is very much part of the rub) are going to have to use something a bit lighter than the clunky great
monster that Ubuntu has managed to become.

I do feel that Mr Slugworth and his merry men have forgotten their initial mission statement and are, now, setting out
to conquer the world and forgetting about the people who end up with machines thrown at them by the supposedly
well-intentioned first world with no operating system to run on them that will allow them to run any sort of
contemporary software.

mark-shuttleworth.jpg

It is interesting to note he is developing that messianic look rather like the late Steve Jobs.

Possibly Mr Slugworth (at Ubuntu / Canonical) has forgotten that there is, sadly, no everlasting gobstopper!

gunter_meisner.jpg

Give me the late, great Gunter Meisner any day.

After this "little adventure", I shall scrub my hard drive and have a go with MintPPC: http://www.mintppc.org/

That might be more 'the thing'.

[richmond62]

I'm not sure whether I am nearer finding the Grail or not, quite frankly:

latestHashUp.png

Although I find this a bit odd:

../../prebuilt/lib/linux-i386/libcrypto.a(cryptlib.o): could not read symbols: File in wrong format

[richmond62]

Hopeful, as ever, it does look like the only barriers might just be:

../../prebuilt/lib/linux-i386/libcrypto.a(cryptlib.o): could not read symbols: File in wrong format

and

make[1]: *** [../../_build/linux/i386/release/revsecurity.so] Error 1
make[1]: Leaving directory `/home/jrm/livecode/thirdparty/libopenssl'
make: *** [revsecurity] Error 2

And I wonder if I should have done the build with ROOT permissions?

[richmond62]

This makes me think about the remarks about possibly needing PPC versions of libcrypto.a, libcurl.a and libssl.a.

Now: I wonder where I might find them?

Wow; talk about "out on a wing"! I must be as mad as a hatter; I downloaded this: http://www.findthatzip-file.com/search- ... tar.gz.htm

and sucked the libcrypto.a and libssl.a out of the compressed file, swapped out the files in /livecode/prebuilt/lib/Linux-i386/ [well, I just made a new directory called 'Backup' and put them there] and
went for a build.

[richmond62]

And here is what happened in the terminal:

nearerFarrer.png

Definitely time for an afternoon snooze!

[richmond62]

Well; however daft that last exercise was, it did (I belive) prove that there needs to be PPC versions of libcrypto.a, libcurl.a and libssl.a for things to proceed.

One of the odd things is that those components show up on Linux as compressed resources, but I cannot work out how to look inside them . . .

Opening them with a text editor is rather uninformative as well:

whatsthis.png

[richmond62]

Oh, well, I did hope . . .

aRightBgr.png

[richmond62]

Well, LibreOffice did open /livecode/prebuilt/lib/linux-i386/libcrypto.a

libcryptoAjoy.png

and I suppose it would do the same for /livecode/prebuilt/lib/linux-x86_64/libcrypto.a

but, running to 12925 pages as the first one does my motivation to plough through those, compare them, and try to understand them, and how
one might go about setting up a PPC version is zero.

[mwieder]

I think Fraser was wrong about copying the files from an Intel box, as the file formats will indeed be different. What I *think* should be done (and no doubt Fraser will set me straight and send me packing) is to copy the binary files in the prebuilt directory and its subdirectories from an older ppc LC build (i.e., install rev 2.x and then copy the files and touch them. That said, I'm not at all sure that all the files will be available in the older rev directory hierarchy.

[mwieder]

...and the .a files aren't readable text, so it's no use trying to examine them with a text editor.