Hello Rick!

10 Apr 21, Rick Smith wrote to Kai Richter:

 RS> What I did to fix it was in my huskymak.cfg I changed

 RS> PERL=1
 RS> USE_HPTZIP=0
 RS> DYNLIBS=0

 RS> and I was building with the sudo make all install
 RS> And voila it now works as expected.

Thanks for the update!

 RS> I am curious tho because I have installed this many times and put my
 RS> backup in place and have never had this problem.  Do you suppose it
 RS> could be manjaro that causes the issues somehow?

Not directly. Dynlibs puts several functions into external lib files. Those are installed to a lib/ directory which is user-readonly.

I'm not sure what kind of output you'll get on userlevel for

make all
sudo make install

but with dynlibs=1 this will fail because the lib must be installed before the program can be compiled. See the husky base module huskybse files README and INSTALL for detail.


Depending on the *nix distribution there could be specific optimised compiler settings. If those settings change it's always helpful to re-compile those libs too if you want to re-compile software that depends on those libs.

Those dependencies can be very tricky and sometimes it's important to use the correct sequence. E.g. when you use old software that need an old lib version and new tools that need a new version.

The advantage is that the functions inside the lib need to be in memory (RAM and HD) only once - but all linked software can use it.

With dynlibs=0 all required functions of the lib are included directly into the program. If another program uses the same function it would be loaded into memory again and is a RAM wasting dupe.

But even for the raspi this is not relevant for fidonet or husky software. The software is small and there are 3 to ~10 programs running at the same time usually. I think most systems could handle that easily.

If you use dynlibs you should make sure to backup the matching libs too. Without dynlibs your program would work with the single program file.

Regards

Kai

--- GoldED+/LNX 1.1.4.7