I posted this to FIDOSOFT.HUSKY but figured there might be some people on FSX who don't read there that might know.

build.sh keeps abending.

make: *** No rule to make target 'huskylib//home/bbs/husky/gnmsgid.c'

So I set GNMSGID=0 in huskymak.cfg & ran it again.

make: *** No rule to make target 'fidoconf//home/bbs/Husky/obj/afixcmd.o'

I am starting to wonder if maybe the makefiles I pulled from github are busted?

I am following the instructions in the huskybse INSTALL.asciidoc on a debian linux stable system.

Is there a trick to this?

$$
--- SBBSecho 3.28-Linux
* Origin: Capitol City Online (21:1/175)

--- Dumas Walker Said ---
I posted this to FIDOSOFT.HUSKY but figured there might be some people on FSX
who don't read there that might know.
--- Dumas Walker Done ---
I just compiled Husky. I followed the INSTALLasciidoc instructions at https://github.com/huskyproject/huskybse/blob/master/INSTALL.asciidoc

(Ubuntu 24.04 I think)

1. Install pre-reqs:

Package What requires the package -------------------------------------------------
git getting the sources and updating them
make, gcc, g++ build from sources
libperl-dev hpt at PERL=1
zlib1g, zlib1g-dev hpt, htick at USE_HPTZIP=1
texinfo hpt, htick, msged at ((HTML=1 or TXT=1 or
PDF=1 or DVI=1) and defined DOCDIR) or
defined INFODIR
ncurses-base, msged
ncurses-bin
libmodule-build-perl, util
libtest-simple-perl

2. Install

wget https://raw.githubusercontent.com/huskyproject/huskybse/master/script/init_buil d
chmod 0755 init_build
./init_build
cd ~/husky
./build.sh
sudo make -j install

---
I did this on a fresh OS install. I also have pre-compiled binaries if you need them? I actually setup a Docker script so I can build reguarly.

-jA
--- ViSiON/3 0.1.0/linux
* Origin: Zombie Toolshed (21:4/158.1)

Hello Dumas!

25 Feb 26 13:14, Dumas Walker wrote to All:

build.sh keeps abending.
make: *** No rule to make target 'huskylib//home/bbs/husky/gnmsgid.c'
So I set GNMSGID=0 in huskymak.cfg & ran it again.
make: *** No rule to make target
'fidoconf//home/bbs/Husky/obj/afixcmd.o'
I am starting to wonder if maybe the makefiles I pulled from github
are busted?
I am following the instructions in the huskybse INSTALL.asciidoc on a debian linux stable system.
Is there a trick to this?

Did you make any changes to huskymak.cfg besides GNMSGID=0 ?

I've just compiled Husky on a fresh debian-stable installation without any issues.

sudo apt install git make gcc g++ libperl-dev libmodule-build-perl \
libtest-simple-perl zlib1g-dev libncurses-dev texinfo

Then:
wget https://raw.githubusercontent.com/huskyproject/huskybse/master/script/init_build
chmod 755 ./init_build
./init_build
cd ~/husky
./build.sh

And finally: sudo make install

The errors make me think there's something wrong with your building environment, so you might also wanna try building on a clean one using:

env -i HOME="$HOME" PATH="$PATH" TERM="$TERM" USER="$USER" \
bash -c 'cd ~/husky && ./build.sh'

Regards,
Jegor

--- msged/lnx 6.3 2026-02-22
* Origin: MsgEd TE is available for OS/2, Linux, NT and DOS! (21:3/228)

1. Install pre-reqs:

Package What requires the package -------------------------------------------------
git getting the sources and updating them
make, gcc, g++ build from sources
libperl-dev hpt at PERL=1
zlib1g, zlib1g-dev hpt, htick at USE_HPTZIP=1
texinfo hpt, htick, msged at ((HTML=1 or TXT=1 or
PDF=1 or DVI=1) and defined DOCDIR) or
defined INFODIR
ncurses-base, msged
ncurses-bin
libmodule-build-perl, util
libtest-simple-perl

I confirmed that I have all of these.

2. Install

wget https://raw.githubusercontent.com/huskyproject/huskybse/master/script/init_bui
d
chmod 0755 init_build
./init_build
cd ~/husky
./build.sh
sudo make -j install

I did this, as well as editing huskymak.cfg, as called for in the
instructions.

---
I did this on a fresh OS install. I also have pre-compiled binaries if you nee
them? I actually setup a Docker script so I can build reguarly.

I might need them. I will try some other stuff first and then ask! Thanks!

Mike

* SLMR 2.1a * Overdrawn? No way! I still have checks left!
--- SBBSecho 3.28-Linux
* Origin: Capitol City Online (21:1/175)

build.sh keeps abending.
make: *** No rule to make target 'huskylib//home/bbs/husky/gnmsgid.c'
So I set GNMSGID=0 in huskymak.cfg & ran it again.
make: *** No rule to make target 'fidoconf//home/bbs/Husky/obj/afixcmd.o'
I am starting to wonder if maybe the makefiles I pulled from github
are busted?
I am following the instructions in the huskybse INSTALL.asciidoc on a debian linux stable system.
Is there a trick to this?

Did you make any changes to huskymak.cfg besides GNMSGID=0 ?

Yes, I made the requested path changes. I will include them below.

I've just compiled Husky on a fresh debian-stable installation without any issues.

sudo apt install git make gcc g++ libperl-dev libmodule-build-perl \
libtest-simple-perl zlib1g-dev libncurses-dev texinfo

I have all of these.

Then:
wget https://raw.githubusercontent.com/huskyproject/huskybse/master/script/ini
_build
chmod 755 ./init_build
./init_build
cd ~/husky
./build.sh

And finally: sudo make install

Did all of those except the last one since build.sh kept failing.

The errors make me think there's something wrong with your building environment, so you might also wanna try building on a clean one using:

env -i HOME="$HOME" PATH="$PATH" TERM="$TERM" USER="$USER" \
bash -c 'cd ~/husky && ./build.sh'

I will try this next.

Here are the other changes that I made to the huskymak.cfg. I am only
changing the one in ~/husky and not the many huskymak.cfg datasets in any of the directories below it:

# A subdirectory for the source files
_SRC_DIR=/home/bbs/husky

# A subdirectory for the files created during the build BUILDDIR=/home/bbs/Husky

# A subdirectory for object files
OBJDIR=${BUILDDIR}/obj

# A subdirectory for generated dependency makefiles
DEPDIR=${BUILDDIR}/dep

# Prefix for all installation directories
# Set to your homedir if you have no root privilegies
PREFIX=/home/bbs/Husky

# Where to put dynamic libraries (*.so files) when DYNLIBS=1.
# You should take care that this directory is listed in the LD_LIBRARY_PATH
# environment variable (if necessary, modify your /etc/profile file). Some
# 64-bit operating systems use ${PREFIX}/lib here.
LIBDIR=/home/bbs/lib64

# Where to put programs.
BINDIR=${PREFIX}/bin

# Where to put manual pages. If you comment this out, no manual
# pages will be produced.
MAN1DIR=/home/bbs/share/man/man1
MAN3DIR=/home/bbs/share/man/man3
MAN5DIR=/home/bbs/share/man/man5

# The fidoconfig config file will be in this directory:
CFGDIR=/home/bbs/Husky

# Filename (without path) for the config file (default: config)
#CFGNAME=config

# Name of the config file of MSGED TE:
MSGEDCFG=\"$(CFGDIR)/msged.cfg\"

# If you have a working texinfo installation (consisting of the "makeinfo"
# and "install-info" programs) and do not comment out the following setting,
# it will cause GNU info documentation to be built and installed into the given # directory.
INFODIR=/home/bbs/share/info

# A directory for documentation in HTML, TXT, DVI, PDF formats.
# If you comment it out, no documention in these formats will be produced and
# you won't know how to use the software ;-).
DOCDIR=/home/bbs/share/doc/husky

Mike


* SLMR 2.1a * Photons have mass? I didn't know they were Catholic...
--- SBBSecho 3.28-Linux
* Origin: Capitol City Online (21:1/175)

The errors make me think there's something wrong with your building environment, so you might also wanna try building on a clean one using:

env -i HOME="$HOME" PATH="$PATH" TERM="$TERM" USER="$USER" \
bash -c 'cd ~/husky && ./build.sh'

OK I tried that. Still got the same error:

make: *** No rule to make target 'huskylib//home/bbs/husky/gnmsgid.c', needed by 'huskylib//home/bbs/Husky/obj/gnmsgid.o'. Stop.

However, adding '-j 1' after build.sh forced it not to run jobs in parallel, so it stopped looking for something that wasn't built yet and this error went away.

I got some other errors on my path statements, which I was able to fix in huskymak.cfg.

It seems now to have built everything. I will test it later. Thanks!

Mike
$$
--- SBBSecho 3.28-Linux
* Origin: Capitol City Online (21:1/175)

Hello Dumas!

26 Feb 26 09:59, Dumas Walker wrote to JEGOR:

Here are the other changes that I made to the huskymak.cfg. I am
only changing the one in ~/husky and not the many huskymak.cfg datasets in any of the directories below it:

# A subdirectory for the source files
_SRC_DIR=/home/bbs/husky

# A subdirectory for the files created during the build BUILDDIR=/home/bbs/Husky

I believe relative paths are expected for these two parameters, not the absolute ones. That could be the reason you're getting weird paths like 'huskylib//home/bbs/husky/gnmsgid.c'. Did you try leaving the default values for _SRC_DIR and BUILDDIR?

Regards,
Jegor

--- msged/lnx 6.3 2026-02-22
* Origin: We love MsgEd ... (21:3/228)