Re: [Hampshire] Compiling old source

Top Page

Reply to this message
Author: Chris Liddell via Hampshire
Date:  
To: Hampshire LUG Discussion List
CC: Chris Liddell
Subject: Re: [Hampshire] Compiling old source
Since the source archive for Elkulator includes a configure script, I
would expect on *most* distros it to be sufficient to install the
dependencies and run ./configure && make.

There are always exceptions, of course, with incomplete or minimally
tested configure scripts not being unknown - autoconf is, at best,
rather baroque!

If it doesn't just work, let us know and I, or someone else can grab it,
and experiment a bit.

Chris


On 14/10/2020 15:30, Rob via 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
--------------------------------------------------------------