Re: [rvm-research] Resolving External References
Khaled Z Mahmoud <[email protected]> Mon, 4 Dec 2017 20:27:06 -0500
| Newsgroups | gmane.comp.java.jikes.rvm.devel |
|---|---|
| Message-ID | <CAER=_eU_sFKOQXgyh+XKzoUraOzuYcgyX1-r2Mx-NREkmKyGBg@mail.gmail.com> |
And I also checked the the methods have proper definitions in sys.h. What I did actually, is that I checked existing system calls, and made sure the new system calls I have similar declarations in files as the existing ones but without avail. On Mon, Dec 4, 2017 at 6:54 PM, Khaled Z Mahmoud <[email protected]> wrote: > Hi, > > This error is printed when building the bootloader. I am actually using > the system call mechanism (Not JNI ... Sorry about that). I seem to have > all what is mentioned in the documentation of the " > http://www.jikesrvm.org/JavaDoc/org/jikesrvm/runtime/SysCall.html" > documentation especially the following point : "There must be a matching > field NAMEIP in BootRecord.java for each method declared here." > > However, I looked at the *.exp files, and that does not reveal a lot about > the format. It seems that functions I want inside the "/tools/bootImageRunner/sys.C" > are not seen and that causes the build error. > > > > > On Mon, Dec 4, 2017 at 4:19 PM, Erik Brangs <[email protected]> wrote: > >> Hi, >> >> On 04.12.2017 19:32, Khaled Z Mahmoud wrote: >> > I think this is not a difficult question. We have some modifications to >> JikesRVM and we do place calls to C code via JNI. >> >> Normal JNI should work out of the box. If you want to call C code without >> the overhead of JNI, you can use the syscall mechanism. >> >> > When I compile, I receive the following error: >> > >> > >> > /home/*maikon*/jikes/jikesrvm/target/FullAdaptiveMarkSweep_x86_64-linux/libjvm.so: >> undefined reference to `SetPackageTimeWindowLimit' >> > >> > >> > I am now using the latest version of JikesRVM. I know the so files that >> contain these functions. How shall I resolve this error ? >> >> Problems with undefined references might be caused by missing definitions >> in header files or missing symbol exports. You can look at sys.c for header >> problems. The build expects exported symbols for the shared libraries to be >> defined explicitly. You can find the definitions in the *.exp files in the >> bootloader directory and its subdirectories (e.g. libjvm.exp). >> >> >> Kind regards, >> >> Erik Brangs >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Jikesrvm-researchers mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers >> > > > > -- > Regards, > Khaled Mahmoud > -- Regards, Khaled Mahmoud ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Jikesrvm-researchers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers