Difficulties installing ser2sock on RP OS bookworm

[dkrause]

I am attempting to install ser2sock on the latest Raspberry Pi OS distribution (bookworm). I installed libssl-dev and cloned the latest ser2sock repo from GitHub. I executed the configuration script with the following result:

Code: Select all

pi@raspberrypi:/usr/local/src/ser2sock $ sudo ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for SSL_CTX_new in -lssl... yes
checking for BIO_pop in -lcrypto... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking for stdint.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking for unistd.h... (cached) yes
checking for pid_t... yes
checking for error_at_line... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for bzero... yes
checking for gettimeofday... yes
checking for memset... yes
checking for select... yes
checking for socket... yes
checking for strchr... yes
checking for strdup... yes
checking for strerror... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands


So far, so good... configure seems to have worked! Then I tried to execute make:

Code: Select all

pi@raspberrypi:/usr/local/src/ser2sock $ sudo make
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /usr/local/src/ser2sock/missing --run aclocal-1.11
/usr/local/src/ser2sock/missing: line 52: aclocal-1.11: command not found
WARNING: `aclocal-1.11' is missing on your system.  You should only need it if
         you modified `acinclude.m4' or `configure.ac'.  You might want
         to install the `Automake' and `Perl' packages.  Grab them from
         any GNU archive site.
 cd . && /bin/bash /usr/local/src/ser2sock/missing --run automake-1.11 --gnu
/usr/local/src/ser2sock/missing: line 52: automake-1.11: command not found
WARNING: `automake-1.11' is missing on your system.  You should only need it if
         you modified `Makefile.am', `acinclude.m4' or `configure.ac'.
         You might want to install the `Automake' and `Perl' packages.
         Grab them from any GNU archive site.
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /usr/local/src/ser2sock/missing --run autoconf
aclocal.m4:17: warning: this file was generated for autoconf 2.69.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.
/bin/bash ./config.status --recheck
running CONFIG_SHELL=/bin/bash /bin/bash ./configure --no-create --no-recursion
configure: error: cannot find required auxiliary files: config.guess config.sub
make: *** [Makefile:225: config.status] Error 1


Not so good. I don't know how to find or fix the missing aclocal-1.11 or automake-1.11. I checked to verify that automake is installed. It is, but it is automake-1.16.5, not 1.13. I'm sure that this is just a configuration problem, but I don't know where to start. Please help.

David

David A. Krause
krause@acm.org
303-517-9930

[jon.thomp]

Alarm Decoder isn't supported on any Raspian past Buster. There are those of us that have tried to get it updated, but the developer seems to have lost interest in updating the product to modern Raspian versions.

[dkrause]

Thanks for your reply.

I never heard that Buster was the latest OS to be supported. In fact, I am currently running the AlarmDecoder (AD2) HAT board on an rpi4b that is running Bullseye... no problems. I use ser2sock to read the rpi serial port and broadcast it to other computers including rpis and Macs. My goal is to upgrade this system to Bookworm.

It seems to me that the AD2 hardware/firmware should be compatible... the firmware simply writes to and reads from the rpi serial port. This is no big deal. It is just the software, namely ser2sock, that must be migrated. Conceptually, there is nothing in the ser2sock code that incompatible with Bookworm. It's just the complex configure and make files that are based on older utilities. Much of this complexity comes from the addition of ssl. I don't even need ssl as I am operating on a small isolated network.

I will look into a replacement for ser2sock... hopefully something that is easier to build.

Also, I agree that we should persuade Sean Matthews to support his product on new rpi operating systems. Is there anything that I can do to help?

David

[jon.thomp]

The problem is that there are a lot of things that break in Python3. I've been trying to get things updated in my own fork of the code, but am rather stuck on getting the web interface to run. It appears that there was a convenience script that reverted bullseye to python 2 that makes it useable in that version.

Sean Matthews has said in another post that he just doesn't have time to update the code.

[edrikk]

@jon.thomp have you tried this fork against work you're doing? I'm not sure if this person got the web interface working or not, but seems to have made a lot of progress just based on the commits: https://github.com/jareep/alarmdecoder-webapp/tree/python3-port

It would be so amazing to get some updates to this project, and a way to get the Debian backend updated.

The problem is that there are a lot of things that break in Python3. I've been trying to get things updated in my own fork of the code, but am rather stuck on getting the web interface to run. It appears that there was a convenience script that reverted bullseye to python 2 that makes it useable in that version.

Sean Matthews has said in another post that he just doesn't have time to update the code.

[jon.thomp]

I'm further than they are. I have the web interface working in the test wsgi server, but not in gunicorn.

The problem I'm running into has to do with messaging from the client to the server. I think early on in my port I realized that gevent-web sockets was no longer maintained, so I tried to move to socket.io. The result is that the client isn't able to get updates from the server.