Hello All!

I have been trying to build elements of Husky, namely :

fidoconf-master/
hptkill-master/
hpt-master/
hptsqfix-master/
hptzip-master/
huskybse-master/
huskylib-master/
huskymak.cfg
makefile
smapi-master/
sqpack-master/

huskymak.cfg was changed to PREFIX=/usr/local

When compiling via a make, I get an error with the last dozen or so lines of :

--
gcc -Wall -c -s -O3 -fomit-frame-pointer -fstrength-reduce -fPIC -DUNIX  
-Ihuskylib src/xstr.c
ar r libhusky adcase calendar cmpfname crc cvtdate dirlayer fexist ffind 
genmsgid genverst
getfree ioutil log locking mapfile memory qksort patmat recode ftnaddr 
setfsize strext strftime
temp tdelay tree version xstr
ar: creating libhusky
ar: adcase: No such file or directory
make: *** [Makefile:46: libhusky] Error 1
--

The content of the Makefile in the main directory has :

--
 Makefile for the Husky build environment

# include Husky-Makefile-Config
ifeq ($(DEBIAN), 1)
# Every Debian-Source-Paket has one included.
include /usr/share/husky/huskymak.cfg
else ifdef RPM_BUILD_ROOT
# RPM build requires all files to be in the source directory
include huskymak.cfg
else
include ../huskymak.cfg
endif
++ rest ignored +++
--

If I cd to make and run make -f makefile all I get errors likewise if I do a 
make -f
makefile.lnx programs


Clearly I am doing something wrong but what ?

The INSTALL.md is not very explicit on the 'HOWTO' as to what directory you 
should be in when
running make :)


The objective is to create a front end I can use in conjuction with some 
software I am writing
to access netmails coming in via mbse which uses JAM messagebase only to 
collect messages with
specific subject lines. I can use mbse to post netmails and likewise echo 
messages but as sall
is JAM only i.e., no support for .msg type areas this is the only way I can 
think of doing it.

Another solution is to still use Husky for a specific node address that is NOT 
in mbse with a
basic mailer to do the same but in this instance to use it for reading and 
writing messages
to/from Netmail and a echo area.

The program is written in Cobol that creates C code that in turn runs through 
GCC.
Cobol can handles LS (line sequentual) and SEQ (sequentual) files without 
issue. Here note that
LS is like text records with the linux stand of line termination as against 
SEQ that uses a nul
for record termination.  I am using ISAM for the main database file.

So, for reading writing any message I use the LS format so I just have to 
somehow link between
the two formats ( *.MSG files and LS ) in order to read/write.

Can any one help me ?

Thanks in advance.

Vince

--- Mageia Linux v7.1 X64/Mbse v1.0.7.13/GoldED+/LNX 1.1.5-b20180707