Hi there

It's been some time since I built Husky software and when I did it was using a process that has now changed.

I've been following the new steps and am up to looking at huskymak.cfg and the changes I need to make to it.

I'm comparing my old huskymak.cfg from the old building process with the new one.

My question is that in my old .cfg I had a switch DYNLIBS=1 whereas the default setting for the new huskymak.cfg is DYNLIBS=0

I'm wondering if I should set this to 1 or leave as default?

My system is a Debian Linux one and I am not a very experienced Linux user..

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

My question is that in my old .cfg I had a switch DYNLIBS=1 whereas the default setting for the new huskymak.cfg is DYNLIBS=0

I'm wondering if I should set this to 1 or leave as default?

I have been leaving mine to the new default, 0.

My system is a Debian Linux one and I am not a very experienced Linux user..

The difference is that husky no longer depends on the files in..

/usr/local/lib{64}

With DYNLIBS=0 the binaries are statically linked. You can run these binaries on another system without rebuilding. For example you can copy pktinfo to another machine and it will run there.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 24 Sep 2022 at 02:59a, Alan Ianson pondered and said...

My question is that in my old .cfg I had a switch DYNLIBS=1 whereas the default setting for the new huskymak.cfg is DYNLIBS=0

I'm wondering if I should set this to 1 or leave as default?

I have been leaving mine to the new default, 0.

interesting thanks, so no static linking

With DYNLIBS=0 the binaries are statically linked. You can run these binaries on another system without rebuilding. For example you can copy pktinfo to another machine and it will run there.

that does not seem correct to me, as I understand it from the config, setting a 0 means that the feature won't be enabled, which was why with my earlier attempts at building stuff (using the old system) and with those older settings being enabled (=1) I wanted to query if I should change it to =1 for the new system :)

It seems to me surely it would be better to be statically linked so that the stuff I build is more 'portable' ?

Thanks for your reply Al :)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 25 Sep 2022 at 02:17p, Paul Hayton pondered and said...

I have been leaving mine to the new default, 0.

interesting thanks, so no static linking

With DYNLIBS=0 the binaries are statically linked. You can run these binaries on another system without rebuilding. For example you can co

This setting confused me, but I went with 0 and I think that was the way to go - I hope :)

After installing a few more dependencies I ran the script and it all built, then ran sudo make -j install and it all seemed to work, so thats' great. I hope from now on I can just run those two steps from time to time and all will build and install... much nicer system :)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

With DYNLIBS=0 the binaries are statically linked. You can run these
binaries on another system without rebuilding. For example you can co

This setting confused me, but I went with 0 and I think that was the way to go
- I hope :)

Yes, this confused me at first but static linking works too.

After installing a few more dependencies I ran the script and it all built, then ran sudo make -j install and it all seemed to work, so thats' great. I hope from now on I can just run those two steps from time to time and all will build and install...

Yes, I think that is the case but this new way of doing things is still new to me.

much nicer system :)

I actually prefer dynamic linking, everything here is dynamically linked except the husky stuff.

Static linking does have the advantage that I can simply copy hpt/htick/pktinfo to another machine and they work without needing to buld the libs in
/usr/local/lib64.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)