swig: Fix issue with circular import in 2.0.9/2.0.10
Review Request #2003 - Created Sept. 6, 2013 and submitted
| Information | |
|---|---|
| Andreas Hansson | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 9856:5222bd5462f2 --------------------------- swig: Fix issue with circular import in 2.0.9/2.0.10 This patch fixes an issue which prevented gem5 from running when built using swig 2.0.9 and 2.0.10. The generated event.py tried to import m5.internal which in turn relied on importing event. This patch seems to fix the problem, and so far has not caused any other issues.
Built on Ubuntu 10.04, RHE5, Fedora 19, Fedora RawHide, OpenSuse 12.3, OSX 10.8, with clang 3.2, 3.3, gcc 4.7, 4.8 and swig 2.0.4 and 2.0.9 and 2.0.10
Posted (Sept. 6, 2013, 8:20 a.m.)
I'm surprised this is an issue... normally a circular import dependency in Python is not a problem, as long as the import isn't used until both modules have had a chance to fully load. What error message do you get?
Review request changed
Updated (Sept. 11, 2013, 8:19 a.m.)
Description: |
|
|||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Diff: |
Revision 2 (+1 -8) |
Thanks for the tweaks!
