John E. Malmberg wrote:
> As far as doing things non-standard on OpenVMS:
>
> There are currently an estimated less than 5 OpenVMS developers that are
> using the supplied configure scripts and related makefiles for building.
>
> The rest are rolling their own makefiles and manually creating con
John E. Malmberg wrote:
> >> * lib/passfd.c
> >>
> >> This needs "_X_OPEN_SOURCE_EXTENDED" for the XPG4 V2 features
> >> in the code to compile on OpenVMS. Specifically the "msg_control"
> >> and "msg_controllen" members of struct msghdr.
> >>
> >> This would need to be defined bef
On 7/3/2017 7:07 PM, Bruno Haible wrote:
Hello John,
* Config.h
OpenVMS needs __UNIX_PUTC macro defined for putc_unlocked
and friends to be visible.
The right place to do this (for a macro that affects multiple
gnulib modules) is the 'extensions' module.
* lib/passfd.c
This nee
Hello John,
> * Config.h
>OpenVMS needs __UNIX_PUTC macro defined for putc_unlocked
>and friends to be visible.
The right place to do this (for a macro that affects multiple
gnulib modules) is the 'extensions' module.
> * lib/passfd.c
>
>This needs "_X_OPEN_SOURCE_EXTENDED" for the
Hello,
This is some of the things that I still need to do to get gnulib to the
point of compiling on OpenVMS.
* Config.h
OpenVMS needs __UNIX_PUTC macro defined for putc_unlocked
and friends to be visible.
* lib/passfd.c
This needs "_X_OPEN_SOURCE_EXTENDED" for the XPG4 V2 features
i
