Hello Rick!

06 Aug 22, Rick Smith wrote to Tommi Koivula:

 RS>>> A 06:42:58   Error executing packer (errorlevel==12, permanent
 RS>>> error) 1 06:42:58   Start packing... 4 06:42:58
 RS>>> EchoTossLogFile not found -> Scanning all areas 4 06:42:58
 RS>>> FidoNet Uplink, e9162100.pkt > ea7bc400.we0 6 06:42:58   cmd:
 RS>>> zip -9 -j -q \ftn\outb\00690051.sep\ea7bc400.we0 \ftn\tmp\outb
 RS>>> \e9162100.pkt

 RS>>> zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)
                                    ^^^^
Looks like a seperator problem.


II.1.1 Overview

This is the standard way of compiling Husky source code on Unix-style
operating systems. It will also work on OS/2 if you have the EMX compiler and
a more or less complete chain of GNU tools installed. [...]

If you compile Husky in this way, the default path of the configuration file
and other specialties will be compiled into your executables based onto your
individual needs, and shared libraries will be used if possible to decrease
hard disk space requirements and improve flexibility.


In my old OS/2 configs i have c:\dir\cfg  pathnames. I don't know if letterless is supported but with external tools you have interfaces into other software that may not be able to handle mixed or incomplete path names.

 RS> I have set unixroot in my toss.cmd

I'm not on latest source but once there was a DIRSEP definition in huskymak.cfg.

For initial installations i recommend static builds. More diskspace usage, more memory usage, but easy transferable to other VMs.

Regards

Kai

--- GoldED+/LNX 1.1.4.7