Arculator v2.1 released!

[SarahWalker]

I can't honestly think of any ARM3-intolerant games. Except maybe Zarch.

There are enough games that benefit from ARM3 that I think it's sensible to use it as the default.

[sweh]

Hmm, on my Debian 11 machine.

% git clone https://github.com/sarah-walker-pcem/arculator/

I read Readme-Linux and it told me to run ./configure ... so I did...

% ./configure --enable-release-build
configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.."

This is because

% ls -l install-sh
lrwxrwxrwx 1 sweh sweh 35 Dec 12 18:44 install-sh -> /usr/share/automake-1.15/install-sh

But

% locate install-sh | grep autom
/usr/share/automake-1.16/install-sh

Same for config.sub and config.guess

And then the Makefile has hardcoded aclocal-1.15 and automake-1.15 and at this stage I'm wondering if I'm doing something wrong!

I suspect I could spend a lot of time kludging this

lrwxrwxrwx 1 sweh sweh 32 Dec 12 18:44 INSTALL -> /usr/share/automake-1.15/INSTALL
lrwxrwxrwx 1 sweh sweh 32 Dec 12 18:44 compile -> /usr/share/automake-1.15/compile
lrwxrwxrwx 1 sweh sweh 37 Dec 12 18:44 config.guess -> /usr/share/automake-1.15/config.guess
lrwxrwxrwx 1 sweh sweh 35 Dec 12 18:44 config.sub -> /usr/share/automake-1.15/config.sub
lrwxrwxrwx 1 sweh sweh 32 Dec 12 18:44 depcomp -> /usr/share/automake-1.15/depcomp
lrwxrwxrwx 1 sweh sweh 35 Dec 12 18:44 install-sh -> /usr/share/automake-1.15/install-sh
lrwxrwxrwx 1 sweh sweh 32 Dec 12 18:44 missing -> /usr/share/automake-1.15/missing

Is there a pre-step I should have taken? I think I'm making a mistake, somewhere!

[paulb]

Is there a pre-step I should have taken? I think I'm making a mistake, somewhere!

I did the following to fix this:

Code: Select all

aclocal
automake --force-missing --add-missing
autoconf

You should then be able to do the whole configure and make thing after that.

I also found that I had to install some dependencies again since I upgraded my system, so I now have the following list of packages not necessarily likely to be present:

Code: Select all

libasound2-dev libopenal-dev libsdl2-dev libwxgtk3.0-gtk3-dev zlib1g-dev

[sweh]

Thanks; it looks like it was the --force-missing --add-missing options that fixed most things!

Of course now it tells me "No ROMs available"...

[Sophira]

The ROMs aren't included with the git source, but they are included with the binary download of Arculator.

Your best bet is to download the binary distribution of Arculator 2.2 and copy the "roms" directory into your git-compiled version.

[sweh]

I looked at that site originally, but it has TLS cert issues, and then doesn't seem to know about that directory; eg "The requested URL /arculator/Arculator_V2.2_Linux.tar.gz was not found on this server."

The server claims b-em.bbcmicro.com but the cert is for www.bbcmicro.co.uk and there's no matching SAN entry.

So I assumed that site was no longer valid, which is why I tried to compile from scratch.

[IanJeffray]

I looked at that site originally, but it has TLS cert issues, and then doesn't seem to know about that directory; eg "The requested URL /arculator/Arculator_V2.2_Linux.tar.gz was not found on this server."

Odd. "Works for me". ...

[sweh]

Hmm, I tried from my home machine, from Panix Internet shell account in New York, from a server in Holland; all return the same error

Code: Select all

% curl --insecure -v https://b-em.bbcmicro.com/arculator/Arculator_
V2.2_Linux.tar.gz
*   Trying 82.148.225.178:443...
* Connected to b-em.bbcmicro.com (82.148.225.178) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=www.bbcmicro.co.uk
*  start date: Jan 20 11:23:12 2023 GMT
*  expire date: Apr 20 11:23:11 2023 GMT
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
* using HTTP/1.1
> GET /arculator/Arculator_V2.2_Linux.tar.gz HTTP/1.1
> Host: b-em.bbcmicro.com
> User-Agent: curl/8.3.0
> Accept: */*  
>
< HTTP/1.1 404 Not Found
< Date: Wed, 13 Dec 2023 02:38:08 GMT
< Server: Apache
< Content-Length: 343
< Content-Type: text/html; charset=iso-8859-1
<
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>   
<title>404 Not Found</title>
</head><body>  
<h1>Not Found</h1>
<p>The requested URL /arculator/Arculator_V2.2_Linux.tar.gz was not found on this server.</p>
<hr>
<address>Apache Server at <a href="mailto:hostmaster@stardot">b-em.bbcmicro.com</a> Port 443</address>
</body></html>
* Connection #0 to host b-em.bbcmicro.com left intact

They also show an expired certificate of April 2023 which looks like a server side config error for the SNI named virtual host.

[Sophira]

Yeah, unfortunately the site seems to be reacting differently depending on whether you access it by TLS or not as the site hasn't been set up properly for TLS. If you try to access it by TLS, it acts as though it was responding for https://www.bbcmicro.co.uk - and of course the Arculator directory doesn't exist on that site.

I believe your only option to download the binary release of Arculator is to do so via plaintext HTTP for now - or alternatively, I'm happy to re-upload the tarball here to the forum if you'd prefer.

[IanJeffray]

YMMV...

Code: Select all

ian@puffin:~$ wget http://b-em.bbcmicro.com/arculator/Arculator_V2.2_Linux.tar.gz
--2023-12-13 11:49:25--  http://b-em.bbcmicro.com/arculator/Arculator_V2.2_Linux.tar.gz
Resolving b-em.bbcmicro.com (b-em.bbcmicro.com)... 82.148.225.178
Connecting to b-em.bbcmicro.com (b-em.bbcmicro.com)|82.148.225.178|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9254000 (8.8M) [application/x-gzip]
Saving to: ‘Arculator_V2.2_Linux.tar.gz’

Arculator_V2.2_Linux.tar.gz                  100%[==============================================================================================>]   8.83M  11.7MB/s    in 0.8s

2023-12-13 11:49:26 (11.7 MB/s) - ‘Arculator_V2.2_Linux.tar.gz’ saved [9254000/9254000]

ian@puffin:~$

[Sophira]

YMMV...

The issue is that sweh is attempting to get the file using the https:// protocol (ie. using this non-working link), not http://. Most sites are set up for that and will give you the same thing, but in the case of Arculator's site, it's not - it's currently only accessible via http://, which is less secure.

[IanJeffray]

YMMV...

The issue is that sweh is attempting to get the file using the https:// protocol

Yes. Why? The link posted was http://b-em.bbcmicro.com/arculator/Arcu ... nux.tar.gz - so why try and make pain where there is none? The link works. Job done.

[sweh]

When I mouse over the link, the browser just shows b-em.bbcmicro... without a schema ('cos Chrome doesn't show a schema in the mouseover)

When I clicked on it, chrome tried to go to the https site, maybe because I use the https version of the stardot site? Dunno. That gave an error. I had no reason to assume the link was http.

When testing from the command line, I just cut'n'pasted what was in the URL bar and tried that in curl. Again I had no reason to assume the link was http.

Similarly, when I googled arculator, the first link was to the same site, and the browser went to the https site.

So there was PLENTY of pain there.

And it did highlight a misconfiguration of the server.

[baz4096]

I had the same issue using the HTTP link that IanJ provided. My particular configuration of Chrome will, by default, ignore http:// links to download files. The same links, but with https:// instead result in a normal file download proceeding.

I've configured b-em.bbcmicro.com to use SSL by default. Existing http:// links should redirect transparently to the https:// equivalent, however if someone can give me a decent reason not to do that, I'll disable the redirect.

The issue is that sweh is attempting to get the file using the https:// protocol (ie. using this non-working link), not http://. [snip] but in the case of Arculator's site, it's not - it's currently only accessible via http://, which is less secure.

This statement is a little out of date as of a few minutes ago. HTTPS links now work.