M-209 Simulation Software Now On GitLab

Jan 012013

My M-209 Simulation Software is now hosted on ~~GitHub~~ GitLab (note: I moved all of my public repositories from GitHub to GitLab in June, 2018). This means that all past, present and future versions of it will be available in one spot, and users can easily track changes from version to version.

The main Gitlab page for this software project is here:

https://gitlab.com/NF6X_Crypto/hagelin

You can download tar or zip files for each release from this page:

https://gitlab.com/NF6X_Crypto/hagelin/tags

You can also clone the entire repository onto your computer by installing the free git software and then using this command:

git clone git@gitlab.com:NF6X_Crypto/hagelin.git

I do my development of this software on my Mac, using the toolchain and libraries provided by MacPorts. If you use MacPorts on a Mac, then you do not need to install the git software from the link above; it is provided by the git-core package in MacPorts.

It should be easy to build this project on other Unix-like platforms such as Linux, too.

I haven’t verified it recently, but it should also be possible to build this project on Windows computers in the Cygwin environment.

I plan to host my future open-source projects on GitLab, too. See all of my public repositories sorted into groups on my GitLab groups page.

6 Responses to “M-209 Simulation Software Now On GitLab”

JoelJ says:

2013/05/12 at 15:55

I went through the install on Mountain Lion,
installed xcode via app store, then installed xcode command line
installed, upgraded old, and got running macports (http://www.macports.org/install.php#requirements – note this was a very long and involved process for me due to an old macport installation that wasn’t maintained

git cloned the source, per command above

ran ./configure
It failed looking for Boost headers

(ran around the web finding the boost headers, compiling it (long wait time here), not working, and finally thought to try….)
sudo port install boost

You might want to include this info in your “INSTALL” document on git to help someone else along the install process
- Mark J. Blair, NF6X says:
  
  2013/05/12 at 15:58
  
  Thank you for your suggestion! I’ll try to remember to improve the installation document in a future release. I’ve been told that the manual page needs some work, too.
Thomas Heptner says:

2019/03/27 at 09:19

Hi,

I tried to install the M209 Simulator in Debian Linux by downloading: hagelin-master.tar.gz, unzip and untar it to ~/Projects/hagelin-master and typed

./configure
…
checking for Boost headers version >= 0.0.0… no
configure: error: cannot find Boost headers version >= 0.0.0

had to install libboost

sudo apt-get install libboost*

tried again

./configure
…
checking for Boost headers version >= 0.0.0… yes
checking for Boost’s header version…
configure: error: invalid value: boost_major_version=

Please help how to go on…

Thanks in advance,

Thomas.
- Mark J. Blair, NF6X says:
  
  2019/03/27 at 11:54
  
  Hi! Needing to install the Boost libraries is normal and expected. If I am not mistaken, your new bug is something that happens when I ignore this software for a long time, and Boost changes enough that the boost detection script breaks. I’ve had to update that before.
  
  If you tell me which Debian distribution you’re using, then I’ll try to install it in a virtual machine and then update my software to work with it.
- Mark J. Blair, NF6X says:
  
  2019/04/04 at 13:12
  
  I’ve set up Debian Stretch in a virtual machine and built my simulator. I found that I needed to install the “libboost-dev” and “libboost-regex-dev” packages, and then execute “autoreconf” in the simulator directory. Then I was able to “./configure”, “make”, and “make check” successfully. You might find that there are other packages that you’ll also need to install. If you get more errors, let me know and then we’ll work through it. Good luck!
  - Thomas Heptner says:
    
    2019/04/08 at 02:46
    
    Thanks for your help but “autoreconf” executed in “~/Projects/hagelin-master” did not change anything… what do i do wrong??? Do I have the right version of your software downloaded??? I took this one https://gitlab.com/NF6X_Crypto/hagelin/-/archive/master/hagelin-master.tar.gz
    
    lenny@rocky:~/Projects/turing/hagelin-master$ autoreconf lenny@rocky:~/Projects/turing/hagelin-master$ ./configurechecking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether make supports nested variables... (cached) yes checking for clang++... no checking for g++... g++ 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 g++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of g++... gcc3 checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking how to print strings... printf checking for gcc... gcc 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 whether gcc understands -c and -o together... yes checking dependency style of gcc... gcc3 checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for mt... mt checking if mt is a manifest tool... no checking how to run the C preprocessor... gcc -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 for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking how to run the C++ preprocessor... g++ -E checking for ld used by g++... /usr/bin/ld -m elf_x86_64 checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for Boost headers version >= 0.0.0... yes checking for Boost's header version... configure: error: invalid value: boost_major_version= lenny@rocky:~/Projects/turing/hagelin-master$