Hi Joel, The document says: Add the assembly file to the list of OBJS in the Makefile: INCLUDEDIR=include TARGET=libhooks.la OBJS=hooks.lo alpha_m5.lo and then they create an Alpha assembly file named alpha_m5.lo
Similarly, I copied the m5op_x86.S file from gem5/util/m5 folder to parsec-2.1/pkgs/libs/hooks/src folder where the Makefile is. I also modified the Makefile such that I have: TARGET=libhooks.la OBJS=hooks.lo m5op_x86.lo INCLUDEDIR=include Does this make sure I build using the x86 assembly file? Is the place of the m5op_x86.S file and the OBJS list look correct? On Thu, Sep 19, 2013 at 12:48 AM, Joel Hestness <[email protected]>wrote: > Hi Fulya, > This error occurs when the hooks library is linked as a shared library. > Though I don't recall the details to build the hooks library statically, I > suggest that you try doing that before building the benchmarks (building > this statically is suggested by the ".la" on the end of "libhooks.la" in > our tech report on how to build PARSEC for m5/gem5: > http://www.cs.utexas.edu/~parsec_m5/TR-09-32.pdf). You'll need to ensure > that you're building hooks using the x86 assembly files from gem5/util/m5/. > The tech report also contains some tips for bodytrack, which tends to be > tricky to link. To ensure that your final binary is statically linked, run > 'ldd bodytrack' from the command line. You should see 'not a dynamic > executable'. > > Also, per your prior email, you can compile benchmarks for gem5 x86 > simulation using a standard gcc/g++ installation on an x86_64 machine. You > don't need a crosscompiler or any special flags. > > Hope this helps, > Joel > > > > On Wed, Sep 18, 2013 at 5:43 PM, Fulya Kaplan <[email protected]> wrote: > >> Hi, >> >> I am running Parsec on X86 and I modified something in hooks, so I compiled >> benchmarks myself and mounted the new versions on the x86root-parsec.img >> that I got from Parsec website. I did not change anything else in the >> x86root-parsec image except replacing the newly compiled binaries. >> >> However, when I run the benchmarks I get the error saying: >> >> mounting filesystems... >> loading script... >> ./bodytrack: error while loading shared libraries: libhooks.so.0: cannot >> open shared object file: No such file or directory >> >> The command line I use to compile bodytrack is: >> >> parsecmgmt -a build -c gcc-hooks -p bodytrack >> >> I also made a change in the gcc.bldconf file adding -static option: >> >> export LDFLAGS="-static -L${CC_HOME}/lib64 -L${CC_HOME}/lib" >> >> Do you know anything about this libhooks.so.0 error? Do I need to set other >> flags or what am i missing? >> >> Best, >> >> Fulya >> >> >> _______________________________________________ >> gem5-users mailing list >> [email protected] >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> > > > > -- > Joel Hestness > PhD Student, Computer Architecture > Dept. of Computer Science, University of Wisconsin - Madison > http://pages.cs.wisc.edu/~hestness/ > > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
