31 Dec
2015
31 Dec
'15
8:49 p.m.
Thanks for the clarification. I understand now.
On Thu, Dec 31, 2015 at 16:52 Karel Gardas
On 12/31/15 07:41 PM, Alain O'Dea wrote:
Yes. I can do that.
On SmartOS it may not be GCC 3.4.3 causing this. I see this on GCC 4.7.x through 4.9.x. The paths to gcc on SmartOS also differ. I'll have to verify that as part of checking this.
This is misunderstanding. GCC 3.4.3 provides *correct* CPP behavior, while all 4.x provides broken CPP. That means as a workaround when GCC 3.4.3 is installed I set it as GHC's CPP automatically on Solaris. When it is not available, then GHC behaves like you've seen when using CPP...
Hopefully this is more clear now,
Karel