1. Forum
  2. Fidonet
  3. FIDOSOFT.HUSKY

  • Packing problems

    From Rick Smith@1:105/81 to Tommi Koivula on Sat Aug 6 05:31:14 2022
    Hello Tommi!

    Saturday August 06 2022 08:36, you wrote to me:

    * Forwarded from area 'FIDOSOFT.HUSKY'

    03 Aug 22 06:36, Rick Smith wrote to All:

    Hello All!

    zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)
    A 06:42:58 Error executing packer (errorlevel==12, permanent
    error) 1 06:42:58 Start packing... 4 06:42:58 EchoTossLogFile
    not found -> Scanning all areas 4 06:42:58 Scanning NetmailArea
    NETMAIL 7 06:42:58 Packing for 1:105/81 FidoNet Uplink,
    e9162100.pkt > ea7bc400.we0 6 06:42:58 cmd: zip -9 -j -q
    \ftn\outb\00690051.sep\ea7bc400.we0 \ftn\tmp\outb \e9162100.pkt

    zip error: Nothing to do! (ftnoutb00690051.sepea7bc400.we0)

    This is a klibc problem which can be "fixed" by setting UNIXROOT to a non-existing path.

    The better solution is to use watcom build of hpt or not to use
    arcmail at all.

    I have set unixroot in my toss.cmd , I have your watcom exe problem still exists, I will post my config.

    Regards,

    Rick

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)
  • From Kai Richter@2:240/77 to Rick Smith on Sat Aug 6 17:24:38 2022
    Hello Rick!

    06 Aug 22, Rick Smith wrote to Tommi Koivula:

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

    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.

    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
    * Origin: Monobox (2:240/77)