Re: [Hampshire] Compiling old source

Top Page

Reply to this message
Author: James Courtier-Dutton via Hampshire
Date:  
To: Hampshire LUG Discussion List
CC: James Courtier-Dutton
Subject: Re: [Hampshire] Compiling old source
Hi,

I got elkulator compiled and working
> PRINT "HELLO"

HELLO


It required a fair bit of editing to get it working.
The main problem was getting it to recognize the allegro4.x is installed.
Download:
https://github.com/liballeg/allegro5/releases/download/v4-2-3-1/allegro-4.2.3.1.tar.gz
The only thing you need from the tar file is allegro.m4.
copy the allegro.m4 file into the elkulator folder in a new sub directory
in ./m4/allegro.m4
in the elkulator directory run
aclocal -I m4
mv configure configure.old
autoconf
This should re-generate your "configure" script.
./configure
If it fails looking for install-sh.
rm install-sh depcomp missing compile COPYING INSTALL
autoreconf -vi
then try ./configure again.

I also found that ./src/uef.c needed editing:
--- t3/src/uef.c 2010-07-17 09:15:23.000000000 +0100
+++ src/uef.c 2020-10-15 21:44:01.283483882 +0100
@@ -12,7 +12,7 @@

int tapelcount,tapellatch,pps;
int intone=0;
-gzFile *uef;
+gzFile uef;
int cswena;

 int inchunk=0,chunkid=0,chunklen=0;
@@ -256,6 +256,6 @@
         if (uef)
  {
            gzclose(uef);
- uef=(gzFile *)NULL;
+ uef=(gzFile )NULL;
  }
 }


Tell me if this helped.

Kind Regards

James



On Wed, 14 Oct 2020 at 15:30, Rob via Hampshire <
hampshire@???> wrote:

> Hi all
>
>
>
> I’m trying to compile a very old source file (see
> http://elkulator.acornelectron.co.uk/) on Bionic Beaver and having little
> luck. I’ve not been into the source itself but the README suggests I need
> 4 libraries:
>
>
>
> Allegro 4.x
>
> OpenAL
>
> ALut
>
> Zlib
>
>
>
> I’ve not (yet) researched whether or not these have forked into other
> projects because what I really need to know is whether (for example)
>
>
>
> Apt-get install liballegro-dev
>
>
>
> (or whatever allegro is now called) is all I need to satisfy the first
> requirement or do I need to tell the compiler the library’s there in some
> other way? Or will it find it for itself? I don’t really want to dig
> into the source itself (and no – there is no binary package before anyone
> asks) but am I going to be forced to?
>
>
>
> As you can tell, I’ve never been too hot on C libraries – well not these
> libraries anyway!
>
>
>
> Cheers
>
> R
> --
> Please post to: Hampshire@???
> Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
> LUG URL: http://www.hantslug.org.uk
> --------------------------------------------------------------

--
Please post to: Hampshire@???
Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL: http://www.hantslug.org.uk
--------------------------------------------------------------