Same for me. I saw this yesterday. It is because HARMONY-1558 has changed Class interfaces but didn't change x86_64 specific files. Now that I look at the error messages, I think it is quite easy to fix the build. I'll take care of weekend.
I wonder how did you get to building drlvm if classlib didn't build for you because of -fpic problem? DRLVM build always requires prebuilt classlib... On Friday 10 November 2006 23:53 Stefano Mazzocchi wrote: > I've managed to get everything in place for a DRLVM build.. it runs for > a while and then it fails with these errors: > > [cc] > /home/stefano/src/harmony/drlvm/vm/vmcore/src/util/em64t/base/jit_lock_rt_s >upport_em64t.cpp: In function ‘void* rth_get_lil_monitor_enter()’: > [cc] > /home/stefano/src/harmony/drlvm/vm/vmcore/src/util/em64t/base/jit_lock_rt_s >upport_em64t.cpp:127: error: ‘managed_null’ is not a member of ‘Class’ > [cc] > /home/stefano/src/harmony/drlvm/vm/vmcore/src/util/em64t/base/jit_lock_rt_s >upport_em64t.cpp: In function ‘void* rth_get_lil_monitor_exit()’: > [cc] > /home/stefano/src/harmony/drlvm/vm/vmcore/src/util/em64t/base/jit_lock_rt_s >upport_em64t.cpp:265: error: ‘managed_null’ is not a member of ‘Class’ > [cc] > /home/stefano/src/harmony/drlvm/vm/vmcore/src/util/em64t/base/ini_em64t.cpp >: In function ‘void JIT_execute_method_default(void*, _jmethodID*, > jvalue*, jvalue*)’: > [cc] > /home/stefano/src/harmony/drlvm/vm/vmcore/src/util/em64t/base/ini_em64t.cpp >:201: error: ‘struct Class’ has no member named ‘name’ > [cc] > /home/stefano/src/harmony/drlvm/vm/vmcore/src/util/em64t/base/ini_em64t.cpp >:229: error: ‘managed_null’ is not a member of ‘Class’ > [cc] > /home/stefano/src/harmony/drlvm/vm/vmcore/src/util/em64t/base/ini_em64t.cpp >:326: error: ‘managed_null’ is not a member of ‘Class’ > [cc] > /home/stefano/src/harmony/drlvm/vm/vmcore/src/util/em64t/base/ini_em64t.cpp >:359: error: ‘struct Class’ has no member named ‘name’ > > Suggestions? -- Gregory Shimansky, Intel Middleware Products Division
