PiDP-8/I SoftwareUpdate of "OS Compatibility"
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.


Artifact ID: e823003cf5bacb3f476ae29faaf5acce89e9b730
Page Name:OS Compatibility
Date: 2019-05-11 14:06:24
Original User: tangent
Parent: 63931dbc8a301e9b3a1894517f9e22fa4d41bd26 (diff)
Next c36b4e61744f2f858e4ea5ece4a173b67c92789b

The Situation

Although the core software underlying the PiDP-8/I software distribution is broadly portable, the dominance of Raspbian in the Raspberry Pi space means it gets the most attention when it comes to testing and development. This article documents what it known to work, where, today.

If you need the software to work on some platform where it currently doesn't, we accept patches! You can also send problem reports to our development forum, file a bug report, or discuss it on the users' mailing list.

Raspbian, Debian, Ubuntu

The current stable release of the PiDP-8/I software distribution was built for and tested with the Raspbian Stretch Lite distribution. Prior releases were built atop the Raspbian Jessie Lite distribution; current software should still work on Jessie, though we no longer test that, having upgraded all of our development systems to Stretch.

Raspbian-based OSes like pipaOS should also work, but this is not tested by the project's current developers.

The project's primary maintainer occasionally builds the software on Debian and Ubuntu systems as well, which works fine, since Raspbian and Ubuntu are both derivatives of Debian. On such systems, the software is designed to detect the absence of the PiDP-8/I front panel hardware and work without it.

Because of that success, we expect it will run on any other Debian derivative, too.

The configuration script and documentation advice on installing third-party dependencies is given in terms of Debian type OSes. That makes using the PiDP-8/I software distribution on this class of OSes the most straightforward.

Non-Debian Linuxes

There are non-Debian type Linux based OSes for the Raspberry Pi such as openSuSE for the Pi 3 and CentOS for the Pi 3. Since the primary developers on this project haven't tried any of these Pi Linux distros, and no one has reported on their attempts to make it work, we can only speculate on the workarounds required, if any.


This project's current primary maintainers use macOS at home, so the PiDP-8/I software is frequently built and tested on macOS while we are working on features that do not require the PiDP-8/I front panel hardware.

Why? Because it builds 3-12 times faster than on a Pi 3, depending on what has to be built!

The third party dependency advice given by the configure script and in the documentation needs to be adjusted. We recommend getting such things from Homebrew.


Because of our regular testing on macOS, the port to FreeBSD was straightforward. On the FreeBSD 11.2 system we did the work on, we had to install the following non-core packages:

$ sudo pkg install coreutils gmake perl5 python py27-pip

Avoid the temptation to install the python3 package instead: this package follows the Python project's recommendation to install the interpreter only as "python3" to avoid conflicts with Python 2. We try to write our Python scripts to work on both versions, but until we cut over to requiring Python 3 only, we can't change our script shebang lines to work with this package.

It is expected that the code that drives the PiDP-8/I front panel hardware will not work on FreeBSD for the Raspberry Pi. We have an open feature ticket for that, if you want to work on it.


The PiDP-8/I software's build system requires a POSIX type environment. That gives you two major choices for building the simulator on Windows.


This works, and appears to work well besides.

You will have to install the libncurses-devel and python2-pip packages as well as standard Unix build tools: GCC, GNU Make, etc. Having done all that, the software will build and run.

I most recently tested this on 64-bit Windows 10 running Cygwin 2.9.0.

Windows Subsystem for Linux

You'd think this would work because the default Linux implementation for Windows 10's WSL feature is Ubuntu, and this software is known to build and run under Ubuntu easily, since it's closely related to Raspbian. Alas, it utterly failed the last time we tried it.

The primary problem is that WSL's terminal handling was extremely weak at the time, and has been so since the start. This breaks a broad swath of software and is thus well known as a major weakness of WSL. Microsoft is aware of this and is slowly improving it, so it's possible that they've fixed all of the problems since our tests were done.

If it isn't working yet, the changes announced for WSL 2 and the Windows console might finally clear all of that up when it's released. (Insider builds are still a couple of months in the future at the time of this writing, and a stable release is still further in the future.)

Meanwhile, Cygwin or a Linux VM under HyperV are better options for the purposes of running the PiDP-8/I software on Windows.