Marvin Humphrey wrote on 1/14/10 11:42 AM:
On Thu, Jan 14, 2010 at 10:39:20AM -0600, Peter Karman wrote:
A web search reveals that this is a GCC error, but it's unexpected because
GCC should be tolerant by default. Do the flags that you're passing to GCC
include "-std=c90", "-std=C89", or "-ansi"?
no.
Hmm. Does adding "-std=c99" make the problem go away? Maybe GCC 3.x handled
this differently.
yes, that makes the problem go away. The issue was present under gcc 3.4 (RHEL
4) and gcc 4.2 (OSX 10.6).
Seems like making that flag explicit when gcc is detected would be a good thing.
Does that kind of test properly go into Build.PL or into Charmonizer somewhere?
--
Peter Karman . http://peknet.com/ . [email protected]
