Here are the remaining changes to fix the #include_next problem for
Sun Studio 12 on GNU/Linux, for modules I don't maintain. OK to
install these, Bruno and Simon?
Index: ChangeLog
===
RCS file: /cvsroot/gnulib/gnulib/ChangeLog,v
ret
Bruno Haible <[EMAIL PROTECTED]> writes:
> Although I cannot reproduce the original problem (tried gcc 3.3.1 and 4.2.0),
I ran into a similar problem a couple of days ago with Sun Studio 12
on GNU/Linux. That compiler supports #include_next but is not GCC.
It gets into recursive inclusion loops,
Hi Simon,
> I suppose the reason for this bug is that the gnulib stdint.h
> replacement is installed by libidn.
It is installed, but under a different name, namely idn-int.h!
> However, I believe we have discussed this mode of operation before, and
> there hasn't been any problems until now.
Th
Simon Josefsson <[EMAIL PROTECTED]> writes:
> Perhaps #include_next is simply not reliable to use in generated *.h
> files?
We need to handle it better, yes. I'll look into it.
Remko van der Vossen <[EMAIL PROTECTED]> writes:
> Hello everyone,
>
> I have a problem with using libidn;
>
> I tried to compile mutt (1.5.9 and CVS) with libidn support, but got the
> following error in both cases:
>
> gcc -DPKGDATADIR=\"/usr/share/mutt\" -DSYSCONFDIR=\"/etc\"
> -DBINDIR=\"/usr/
