On 17/01/09 08:10 AM, Bruno Haible wrote:
>>> $ cd gllib
>>> $ cc -DHAVE_CONFIG_H -I. -I.. -I../intl -g -E getdate.c | \
>>> grep mbstate_t | head -2
>>> extern size_t rpl_wcrtomb (char *s, wchar_t wc, mbstate_t *ps);
>>> typedef charmbstate_t;
>> Thanks for reporting this. Ca
> > $ cd gllib
> > $ cc -DHAVE_CONFIG_H -I. -I.. -I../intl -g -E getdate.c | \
> > grep mbstate_t | head -2
> > extern size_t rpl_wcrtomb (char *s, wchar_t wc, mbstate_t *ps);
> > typedef charmbstate_t;
>
> Thanks for reporting this. Can you send me the complete output of
> "
Albert Chin wrote:
> I missed another
> platform where this is a problem, IRIX. Using the same gnulib-tool
> invocation as on HP-UX:
> $ ./gnulib-tool --create-testdir --dir=t arpa_inet crypto/md5 \
> environ filemode fnmatch fnmatch-gnu getdate gettext glob human \
> iconv_open inet_pton lst
On Thu, Jan 15, 2009 at 12:27:36AM +0100, Bruno Haible wrote:
> > This causes a problem on HP-UX 11.00 because is included more
> > than once.
> > $ ./gnulib-tool --create-testdir --dir=t arpa_inet crypto/md5 \
> > environ filemode fnmatch fnmatch-gnu getdate gettext glob human \
> > iconv_o
Hi Albert,
> Why does lib/wchar.in.h have:
> #ifndef _GL_WCHAR_H
> ...
> #ifndef _GL_WCHAR_H
> #define _GL_WCHAR_H
> rather than just:
> #ifndef _GL_WCHAR_H
> #define _GL_WCHAR_H
This is the necessary idiom when using #include_next.
> This causes a problem on HP-UX 11.00 because is
Why does lib/wchar.in.h have:
#ifndef _GL_WCHAR_H
...
#ifndef _GL_WCHAR_H
#define _GL_WCHAR_H
rather than just:
#ifndef _GL_WCHAR_H
#define _GL_WCHAR_H
This causes a problem on HP-UX 11.00 because is included more
than once.
$ ./gnulib-tool --create-testdir --dir=t arpa_inet crypto/
