On Mon, 17 Nov 2003, Nicholas Clark wrote:
> Heiko Schlichting said that I could/should forward this to the list.
> Seems interesting. I've not yet looked at Configure, or what it's up to
> in the CPP tests, but it seems that we have enough information to work
> round the problem. (without needing to assign blame either way]
>
> Nicholas Clark
>
> ----- Forwarded message from Heiko Schlichting <[EMAIL PROTECTED]> -----
Thanks for this nice diagnosis:
> The IRIX compiler behaves in a different way for input
> from stdin and for input from a file:
>
> -----------------------------------------------
> | [EMAIL PROTECTED] 107 (/tmp): cat cpp_stuff.c
> | #define RCAT(a,b)a/**/b
> | #define ACAT(a,b)a ## b
> | RCAT(Rei,ser)
> | ACAT(Cir,cus)
> -----------------------------------------------
> | [EMAIL PROTECTED] 108 (/tmp): cc -E - < cpp_stuff.c
> | # 1 ""
> |
> |
> | Reiser
> | Cir ## cus
> -----------------------------------------------
> | [EMAIL PROTECTED] 109 (/tmp): cc -E cpp_stuff.c
> | #line 1 "cpp_stuff.c"
> |
> |
> | Rei ser
> | Circus
> -----------------------------------------------
Yup, Configure's cpp tests did not anticipate this possibility. Is there a
flag one could give to the compiler to make it always use ANSI
preprocessing mode?
If not, then cppstind for IRIX should probably be changed to use the
wrapper script. One way to do that might be to have Configure compare
two tests (as above). If they differ, use the wrapper script.
In any case, could you let us know the exact compiler and OS in question
so that we can at least have accurate comments in the relevant Configure
sections?
Thanks,
Andy Dougherty [EMAIL PROTECTED]
