Grüß Dich, Martin!

Am 07 Aug 04, Martin Foster schrieb an Vince Coen:

 MF> As well as that, some of the INSTALL docs are contradictory. The one
 MF> included in the huskybase module states something to the effect that once
 MF> smapi and fidoconf have been compiled, it's simply a matter of un-tarring
 MF> each of the other required modules into the base husky directory, then
 MF> changing to the module directory and compiling the module from there.

Are you sure that you have the correct huskybse module?

At "II.1.2 Configuring" of /huskybse/INSTALL it requires to
create the huskymak.cfg in the top level directory.

But you are right, at II.1.3 it requires to compile the smapi at first,
which is not valid for the current version. The smapi-current documentation
is not yet up to date, but in the VERSION file of smapi you will find that
smapi-current requires huskylib-current.

It would be an idea to use the VERSION file on every husky module for the
indication of dependencies and change the install docs so they refer to the
VERSION file. That way the newbe's may find the required versions without
help of others.

 MF> In the case of hpt, that's not true, one has to change to the
"make"
 MF> directory otherwise it won't compile. *That* information is contained in
 MF> the INSTALL doc for hpt.

Yes but,... That are two total different ways of comilation, which have
nothing to do with each other. You must choose your way, way 1 for
huskymak.cfg *OR* way 2 without huskymak.cfg but different makefiles.

For you it is true to change to the make directory because you use a
platform dependent legacy makefile.

For others is true that they must not change to the make directory because
they use the huskymak.cfg.

You are not allowed to mix both way's.

For your system, something with your huskymak.cfg or dependencies was wrong.

Tschuess

Kai

---