GitLab

It should be emphasized that there are now two branches that are required to be present:

origin/master is supposed to be stable and buildable at all times

origin/relcan, for "release candidate", is used by the camelian-packages repositories package-
building routines for creating packages.  My procedure lately has been to fuss and fiddle
with relcan until the completed final packages work properly, and then merge relcan into
master.  That merge gets tagged as a release version, and at that point ../include/version.h
is incremented.

When GCC went from version 8 to version 9, it started inserted endbr64 instructions into
the generated .s code.  endbr64 is a signal that the address is a valid target for an indirect
jump.  Code thus annotated is more resistant to hacking and errors.  But it messes up our ability
to trick GDB into showing us good line numbers when stepping into subroutines, so I modified
SFIX to just strip them out.

This is version 2.6.  It was being installed in the wrong place.  Found it because of a Centos package
build test; I was forcing it into usr/local/bin and not looking at DESTDIR.   I am going to hold my
my nose and not change the version code; this is all happening in one day.

Changes made since the last commit were in the README.md file and in copyright information.

In particular, sfix is now cobcd-sfix, cobst is now cobcd-st, and cprint.py
has become cobcd.py.  The result is that the files deployed to implement the
Camelian/Symas debugging extensions are now all named cobcd*

The idea is that on a Windows MSYS build, the 'make clean' will not delete the
./msys/ files, because they will be needed.  On other systems, we want the
./msys/ product files to be deleted.

The root directory now contains a version.h file.  The #define VERSION x.y line provides a
version code that is used directly in cobst and sfix.  The same version is extracted by
scripts for updating cprint.py, and for creating the tarballs for distributing the source code