I was thinking of modifying 
https://gitlab.com/FreeDOS/net/fdnpkg/-/blob/master/SOURCE/FDNPKG/PKGDB.C?ref_type=heads
to show which package failed CRC check... not thought it much yet.

I tried to begin to recompile fdnpkg without changes first to see how hard it 
is.
make
inf.c:59:15 Warning considered as an error: This statement may fall through:
   /* run inflate() on input until output buffer not full */
    do {
      strm.avail_out = CHUNK;
      strm.next_out = out;
      ret = inflate(&strm, Z_NO_FLUSH);
      switch (ret) {
        case Z_NEED_DICT:
          ret = Z_DATA_ERROR;     /* and fall through */
        case Z_DATA_ERROR:
        case Z_MEM_ERROR:

I think it would need to become:
switch (ret) {
        case Z_NEED_DICT:
          ret = Z_DATA_ERROR;
          __attribute__((fallthrough));
        case Z_DATA_ERROR:
         __attribute__((fallthrough));
        case Z_MEM_ERROR:
        __attribute__((fallthrough));

or maybe:
https://en.cppreference.com/w/c/language/attributes/fallthrough
but it is C23, and fdnpkg seems to use C90.

Anyway... passing that... I get to the fact that it need Watt32 to compile net.c
https://sourceforge.net/p/fdnpkg/code/HEAD/tree/tags/v0.99.7/fdnpkg.txt

https://www.watt-32.net/watt32s.zip have a file explaining how to build it...
seems a bit tedious to me... and was thinking that if it is worth to build it, 
it may
make sense to make it a FreeDOS package so others may easily install and remove 
it.

I know people here feel that it is making a lot of packages almost not related 
to the
use of FreeDOS... but as a developer it seems to worth it to me.


_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to