client11 failure after upgrade

[Mike Markowski]

I decided to bring my R-Pi up to date and updated/upgraded the little box.  Now my pidp11 no longer lights.  First, pdp.sh wasn't happy:

$ ./pdp.sh 

0

Checking further into it, I cd to /opt/pidp11/bin and try:

$ ./pidp11.sh 

*** Start portmapper for RPC service, OK to fail if already running

rpcbind: another rpcbind is already running. Aborting

*** booting idled ***

*** Start client/server ***

./client11: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28' not found (required by ./client11)

Is source available to recompile?  (I also re-downloaded all from https://obsolescence.wixsite.com/obsolescence/pidp-11-building-instructions )

Thanks!
Mike Markowski

[Mike Markowski]

Oh no, am I the only to experience this?  I thought others would quickly be saying the same.  Maybe I should simply recreate my OS image?  Any advice is welcome to get my PiDP-11/70 going again is very welcome!

Thanks,

Mike

[Mike Markowski]

The problem occurred after I did the following:

apt-get update

apt-get -y upgrade

apt-get -y dist-upgrade

apt-get -y autoremove

apt-get -y autoclean

A small program shows my glibc version:

root@raspberrypi:/home/pi# cat glibc-version.c
#include <stdio.h>
#include <stdlib.h>
#include <gnu/libc-version.h>


int main(int argc, char *argv[]) {
  printf("GNU libc version: %s\n", gnu_get_libc_version());
  exit(EXIT_SUCCESS);
}
root@raspberrypi:/home/pi# ./glibc-version
GNU libc version: 2.24
root@raspberrypi:/home/pi#

[Jonathan Morton]

> On 29 Mar, 2020, at 1:54 am, Mike Markowski <mike....@gmail.com> wrote:
>
> Is source available to recompile?

I think some people have had success in compiling everything, and that should solve the glibc version mismatch.

- Jonathan Morton

[David Johnson]

I'm concerned that you actually don't have the latest version at all.
I followed the install instructions quite a few months ago, and this is what I see:

root@raspberrypi:/home/pi# ldd --version
ldd (Debian GLIBC 2.28-10+rpi1) 2.28
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.


root@raspberrypi:/home/pi# cat /etc/*release*
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
root@raspberrypi:/home/pi#

> --
> You received this message because you are subscribed to the Google Groups "[PiDP-11]" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pidp-11+u...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/pidp-11/70E511C9-0B24-4A95-9B66-612E8E56C1BF%40gmail.com.

[andy]

Hi Mike- FWIW I did a fresh "by the book" Oscar reinstall with the latest Raspbian + updates and I had none of the problems you experienced

cheers

andy

On Sunday, March 29, 2020 at 5:40:57 PM UTC-4, Mike Markowski wrote:

[Jon Brase]

If you installed according to the instructions you linked, the sources are already on your Pi. Go to /opt/pidp11/src , and then run "sudo makeclient.sh" and "sudo makeserver.sh". The "sudo" is needed because the directory is owned by root.

/opt/pidp11/bin/server11 and /opt/pidp11/bin/client11 are links to the binaries these scripts generate in the /opt/pid11/src directory tree, so after that you should be all set.

This is something that can happen when you upgrade from one release of a Linux distribution to another: Library versions get upgraded when you go to the new release, and all the programs that came in through the distribution's package manager get upgraded to use the new libraries, but anything that was installed from a third party source or compiled locally has to be recompiled to use the new libraries. This is a side effect of source code being available for most programs on Linux: library developers feel that they can safely make backwards-incompatible changes because pretty much all of the programs that use their library make source code available to the user, and so the user can always recompile (and, furthermore, if the user is installing from their distribution's repository, the distro maintainers take care of making sure that all the programs are compiled for the right libary versions, so 99.9% of the time the user doesnt have to recompile).

There's a fairly good bet that you're the first one to try upgrading to a new Raspbian release, so it may very well be that nobody has encountered this issue for the pidp11 software before specifically, but it's a fairly common issue in general when using third-party software on Linux.

[Mike Markowski]

Thanks to all for the helpful replies.  For anyone else who might eventually search on this, I had to do the following:

Enter code here...cd /opt/pidp11/src
pushd 02.3_simh/4.x+realcons/bin-rpi
sudo mv pdp11_realcons pdp11_realconsOLD  # Or simply delete it.
popd
sudo ./makeclient.sh

I have my blinkenlights back after that.  :-)  It seems strange that doing a system upgrade apparently downgraded libc.  And a little embarrassing to learn that the source code was sitting on my machine the whole time!  :-P  Thanks again, everyone.

Mike

On Sunday, March 29, 2020 at 8:35:49 PM UTC-4, Jon Brase wrote:

If you installed according to the instructions you linked, the sources are already on your Pi. Go to /opt/pidp11/src , and then run "sudo makeclient.sh" and "sudo makeserver.sh". The "sudo" is needed because the directory is owned by root.

[...]

[Jon Brase]

On Monday, March 30, 2020 at 8:15:31 AM UTC-5, Mike Markowski wrote:

Thanks to all for the helpful replies.  For anyone else who might eventually search on this, I had to do the following

Enter code here...cd /opt/pidp11/src
pushd 02.3_simh/4.x+realcons/bin-rpi
sudo mv pdp11_realcons pdp11_realconsOLD  # Or simply delete it.
popd
sudo ./makeclient.sh

I have my blinkenlights back after that.  :-)  It seems strange that doing a system upgrade apparently downgraded libc.  And a little embarrassing to learn that the source code was sitting on my machine the whole time!  :-P  Thanks again, everyone.

 The upgrade shouldn't have actually downgraded libc (are you actually seeing a lower version number than was previously present), however, new versions of libraries on Linux are often not back-compatible with software compiled for older versions, which is why programs that weren't brought in through your distro's package manager (and thus automatically kept consistent with the installed versions of libraries) generally need to be recompiled to run after an upgrade.

[Mike Markowski]

I'm not 100% certain because I didn't check glibc before the upgrade, but David Johnson in this thread shows he has 2.28 installed.  In my case after the upgrade:

$ ldd --version
ldd (Debian GLIBC 2.24-11+deb9u4) 2.24
Copyright (C) 2016 Free Software Foundation, Inc.

This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

A quick Google shows other Raspian users have experienced the same.  It looks as if a fresh install brings in a more current glibc than subsequent upgrades - or maybe my upgrade dropped to an older, stable version?  I don't know at this point and will dig into it some.  Thanks again.

Mike