On 07/22/11 13:53, nathan binkert wrote: >> Is this our bug, or do we need to inform the swig guys ? > I seem to remember seeing it in a old version of swig. > > Nate > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
That might turn out to be the case, but there's a good chance it's new. This SWIG checkin seems to be the culprit since it adds the macro gcc is complaining about. http://swig.svn.sourceforge.net/viewvc/swig/trunk/Lib/python/pycontainer.swg?r1=12619&r2=12620&; <http://swig.svn.sourceforge.net/viewvc/swig/trunk/Lib/python/pycontainer.swg?r1=12619&r2=12620&;> It was checked in on April 9th of this year. I didn't find much about it on Google other than this: http://bugs.orfeo-toolbox.org/view.php?id=385 which is an open bug on a thing I'm not familiar with. Maybe 2.0.4 is just too new for people to have hit it? Maybe we're doing something fairly unusual? Maybe we broke some rule those other folks broke too? Like I said, I don't know much about SWIG, so I don't know for sure how this pycontainer.swg is supposed to work or why the definition of that macro isn't making it into the things that are using it. Gabe _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
