Andi Vajda <va...@apache.org> wrote: > Bill, > > Did that solve your problem ?
Hmmm, I'm still seeing it. And some other stuff: build/_GoodStuff/__wrap03__.cpp: In function ‘PyObject* com::parc::goodstuff::relations::t_Something1SeqIterator_nextElement(com::parc::goodstuff::relations::t_Something1SeqIterator*, PyObject*)’: build/_GoodStuff/__wrap03__.cpp:9122: error: ‘class com::parc::goodstuff::relations::t_Something1SeqIterator’ has no member named ‘parameters’ build/_GoodStuff/__wrap03__.cpp:9122: error: ‘class com::parc::goodstuff::relations::t_Something1SeqIterator’ has no member named ‘parameters’ build/_GoodStuff/__wrap03__.cpp: In function ‘PyObject* com::parc::goodstuff::family::t_Something2Iterator_nextElement(com::parc::goodstuff::family::t_Something2Iterator*, PyObject*)’: build/_GoodStuff/__wrap03__.cpp:15376: error: ‘class com::parc::goodstuff::family::t_Something2Iterator’ has no member named ‘parameters’ build/_GoodStuff/__wrap03__.cpp:15376: error: ‘class com::parc::goodstuff::family::t_Something2Iterator’ has no member named ‘parameters’ build/_GoodStuff/__wrap03__.cpp: At global scope: build/_GoodStuff/__wrap03__.cpp:27749: error: ‘t_JArray’ was not declared in this scope build/_GoodStuff/__wrap03__.cpp:27749: error: parse error in template argument list build/_GoodStuff/__wrap03__.cpp:27749: error: insufficient contextual information to determine type build/_GoodStuff/__wrap03__.cpp:27749: warning: ‘>>’ operator will be treated as two right angle brackets in C++0x build/_GoodStuff/__wrap03__.cpp:27749: warning: suggest parentheses around ‘>>’ expression build/_GoodStuff/__wrap03__.cpp:27749: error: spurious ‘>>’, use ‘>’ to terminate a template argument list build/_GoodStuff/__wrap03__.cpp:27749: error: expected primary-expression before ‘)’ token build/_GoodStuff/__wrap03__.cpp:27749: error: too many initializers for ‘PyTypeObject’ build/_GoodStuff/__wrap03__.cpp:41430: error: ‘t_JArray’ was not declared in this scope build/_GoodStuff/__wrap03__.cpp:41430: error: parse error in template argument list build/_GoodStuff/__wrap03__.cpp:41430: error: insufficient contextual information to determine type build/_GoodStuff/__wrap03__.cpp:41430: error: expected primary-expression before ‘)’ token build/_GoodStuff/__wrap03__.cpp:41430: error: too many initializers for ‘PyTypeObject’ error: command 'gcc' failed with exit status 1 I think when I tried it this afternoon (I was running out the door and kind of rushed) I just did a wrap, and not a --build. Sorry about that. Bill > > Andi.. > > On Feb 28, 2011, at 20:05, Andi Vajda <va...@apache.org> wrote: > > > > > On Sun, 27 Feb 2011, Bill Janssen wrote: > > > >> Andi Vajda <va...@apache.org> wrote: > >> > >>> It may be simplest if you can send me the source file for this class > >>> as well as a small jar file I can use to reproduce this ? > >> > >> Turns out to be simple to reproduce. Put the attached in a file called > >> test.java, and run this sequence: > >> > >> % javac -classpath . test.java > >> % jar cf test.jar *.class > >> % python -m jcc.__main__ --python test --shared --jar /tmp/test.jar > >> --build --vmarg -Djava.awt.headless=true > > > > This was a tougher one. It was triggered by a combination of things: > > - no wrapper requested for java.io.File or --package java.io > > - a subclass of a parameterized class or interface implementor of a > > parameterized interface wasn't pulling in classes used as type > > parameters (java.io.File here). > > > > A fix is checked into jcc trunk/branch_3x rev 1075642. > > This also includes the earlier fix about using absolute class names. > > > > Andi..
