On Wed, Mar 31, 2021 at 8:41 PM Terry Fuller <t...@pgmguild.com> wrote:
> Hello all, > > I'm having more problems building mod_rexx. I was earlier able to build > mod_rexx for both windows and linux (linux mint 20 specifically). I'm now > trying to eliminate differences between the source files for each operating > system. > > I have source that builds properly on Windows (Windows 10), but the same > source in Linux gets compile (gcc) errors: > > - In file included from mod_rexx.c:27: > mod_rexx.h:153:40: error: unknown type name ‘LONG’ > > I was getting similar errors for 'PSZ' as well, but finally chased that > down to a typedef in rexx.h that was conditioned on 'OOREXX_COMPATIBILITY' > What version of rexx.h are you using? oorexx has no such compatibility flag. The use of the OS/2 derived types in the APIs was scrapped years ago with the 4.0 release. These were replaced with either ANSI portable types (int32_t, etc.) or Rexx-defined versions. The oorexx APIs use RexxReturnCode for return codes and a type CONSTANT_STRING where PSZ used to be used. Rick > Most of the LONG references are associated with return codes... is there > some standard (portable) type that I should be using instead of LONG? > > Rather than requiring a compatibility flag to be set, is there some > standard type I should use in place of PSZ? > > Thanks in advance :-) > > -- > taf > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
