On 7/7/2017 2:43 AM, Bruno Haible wrote:
John E. Malmberg wrote:
I found out what the issue is. The OpenVMS stdio.h file makes the
unlocked IO routines only available as macros. There is no declaration.
Configure detects the macros, and that there is no declaration of them.
The unlocked-io.h
John E. Malmberg wrote:
> I found out what the issue is. The OpenVMS stdio.h file makes the
> unlocked IO routines only available as macros. There is no declaration.
>
> Configure detects the macros, and that there is no declaration of them.
>
> The unlocked-io.h since the HAVE_DECL_FPUTS_UNLO
On 7/6/2017 5:04 PM, Paul Eggert wrote:
Bruno Haible wrote:
I guess that this would not work:
#include
#include "unlocked-io.h"
would not make the unlocked IO routines visible, because
gets skipped
when it gets included a second time. Right?
If we treat __UNIX_PUTC like we treat _GNU
Bruno Haible wrote:
I guess that this would not work:
#include
#include "unlocked-io.h"
would not make the unlocked IO routines visible, because gets skipped
when it gets included a second time. Right?
If we treat __UNIX_PUTC like we treat _GNU_SOURCE then we should be OK, since
__UNIX
John E. Malmberg wrote:
> >> * 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.
>
> This makes it visible to th
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.
This makes it v
