Subj : hardcoded config entry?
To   : Michael Dukelsky
From : Kai Richter
Date : Tue Sep 19 2023 07:11 pm

Hello Michael!

20 Jul 23, Kai Richter wrote to Michael Dukelsky:

 KR>>> mistake and needed to change the CFGDIR path but the next make
 KR>>> run did not rebuild any files?

 MD>> Fixed.

 KR> Fetched. But not tested yet. I'll report if done.

Sorry, long time no see.

The build script fails on every second run.
For static and dynamic building i prepared huskymak with the dynlib and path adjustment settings.

cd ~/husky
cat mk.static.sh

#!/bin/sh
cp huskymak.stat huskymak.cfg
../build.sh


 % ./mk.static.sh
Trying to update huskybse
Trying to update huskylib
Trying to update smapi
Trying to update fidoconf
Trying to update areafix
Trying to update hpt
Trying to update htick
Trying to update hptkill
Trying to update hptsqfix
Trying to update sqpack
Trying to update fidoroute
Trying to update msged
Trying to update util
Trying to update areastat
Trying to update nltools
Already up to date.
 [up to date for all above]
diff: invalid option -- Z
usage: diff [-aBbdilpTtw] [-c | -e | -f | -n | -q | -u] [--ignore-case]
            [--no-ignore-case] [--normal] [--strip-trailing-cr] [--tabsize]
            [-I pattern] [-L label] file1 file2
 [more diff useage]

### Config name and/or path has changed. Please run the same command again ###

If i do run the same command again then i can see clang linking many .o files.
The last linked are msged then nltools then the msged help compiler reported two times "done".

During this run i didn't noticed any errors.

If i start the mk.static.sh again then i get the same "run again" result as seen above. I tried the build.sh alone and got the same results.

I have no idea where the trigger "config changed" does come from.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
 * Origin:  Monobox  (2:240/77)

.