Hello Vince!

19 Nov 19, Vince Coen wrote to All:

 VC> huskybse-master/

Maybe i'm outdated, but my source doesn't have the -master "extension".

 VC> huskylib-master/
 VC> huskymak.cfg
 VC> makefile

Looks like somebody made a general makefile for all husky modules.

 VC> adcase: No such file or directory make: *** [Makefile:46: libhusky]

 VC> The content of the Makefile in the main directory has :

There is none in my old husky suite.

Please try a manual "oldscool" compilation as follows.

The entry point for compilation is the huskybse module.
huskybse itself is not a module. It doesn't need to be compiled.

But you can find the INSTALL doc there and examples for the huskymak.cfg.

The basic concept is:

II.1.3 Compiling and Installing

Now, you can build smapi and fidoconfig (please do it in this order) using

  cd ~/husky/smapi
  make clean
  # or use "gmake" if "make" does not invoke GNU make on your system!
  make all install

  cd ~/husky/fidoconf
  make clean
  make all install

It is important that you a) INSTALL (gmake install) smapi before you try to
COMIPLE fidoconf, because otherwise the smapi library - which is required for
building fidoconfig - will not be found, and likewise, that you INSTALL
fidoconf before you try to COMPILE anything else.

You can build and install any module using the command sequence

  cd ~/husky/MODULENAME
  make clean
  make all install

 VC> Clearly I am doing something wrong but what ?

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

In general it should be the directory where the makefile is.

Within the makefile there are "targets".
Target: clean
Target: all
Target: install

Note that "make all" builds all but it does not install it. You need the "make
install" for that or both in one "make all install".

The install target copies the file to their destination in the PREFIX tree,
/usr/local/ in your case. There are lib files like libhusky (your error above)
that are placed into the lib path.

If you compile another husky module it may rely on that lib file and is looking
for that libhusky in the lib path. If not found -> error.

The sequence of compilation and installation is important.

For the actual husky suite you may need huskylib at first. -> check docs.

Regards

Kai

--- GoldED+/LNX 1.1.4.7