2.0b4 is almost 3 years old and is from before X86_FS was really
working. If there isn't some strong reason you're using that, I'd
suggest moving to the current development repository version.

Gabe

On 10/31/10 03:51, wagner meneguzzi pinto wrote:
> Hello Gabe,
> I'm using version 2.0b4-M5, the only modifications I did was to
> declare some variables not found, because I downloaded the M5 from a
> User that had Alpha-and then only spent a few things that were giving
> errors for X86. If they want to take a look, I took the M5 the end of
> this link: (http://www.eecs.umich.edu/~blakeg/).
> So, yes in the directory has a file called thread_context.do (which
> can not be displayed) and thread_context.hh and thread_context.cc ...
> Do not know what could be wrong, I tried to install everything again
> but still the error continues
>
> --- Em *sex, 29/10/10, Gabe Black /<[email protected]>/* escreveu:
>
>
>     De: Gabe Black <[email protected]>
>     Assunto: Re: [m5-users] Problems with m5.debug.bin
>     Para: "M5 users mailing list" <[email protected]>
>     Data: Sexta-feira, 29 de Outubro de 2010, 19:19
>
>     What version of the source are you using? Have you changed
>     anything? Is
>     there a file called build/X86_FS/cpu/thread_context.do (or similar) in
>     the build directory? Was it included in the files that were linked
>     together at the end? I'm assuming that's the command that produced
>     this
>     error. Were there any earlier error messages? I'm pretty confident
>     this
>     isn't because of M5 itself and is specific to your machine or your
>     version of the source, so you might want to try deleting the build
>     directory and starting from scratch there in case something got
>     stuck in
>     a funny state. If you haven't done any work on the source, you
>     could try
>     downloading it again in case a file was accidentally deleted or
>     modified
>     somehow.
>
>     Gabe
>
>     wagner meneguzzi pinto wrote:
>     > Hello everyone,
>     > I'm having some problems building the M5 simulator. More
>     specifically
>     > in the construction of m5.debug.bin as follows:
>     >
>     > scons: done reading SConscript files.
>     > scons: Building targets ...
>     > g + +-o build/X86_FS/m5.debug.bin
>     build/X86_FS/python/swig/pyevent.do
>     > build/X86_FS/python/swig/pyobject.do build/X86_FS/dev/baddev.do
>     > build/X86_FS/dev/disk_image .'s (...)
>     >
>     > When referencing the file simple_thread.do, occurs the following
>     errors:
>     >
>     > build/X86_FS/cpu/simple_thread.do: In function `ThreadContext:
>     > ThreadContext () ':
>     > simple_thread.cc: (. text._ZN13ThreadContextC2Ev [ThreadContext:
>     > ThreadContext ()] +0 x8): undefined reference to `vtable for
>     > ThreadContext '
>     > build/X86_FS/cpu/simple_thread.do: (.
>     > rodata._ZTI18ProxyThreadContextI12SimpleThreadE [typeinfo for
>     > ProxyThreadContext <SimpleThread>] +0 x8): undefined reference to
>     > `typeinfo for ThreadContext '
>     > collect2: ld returned 1 exit status
>     > scons: *** [build/X86_FS/m5.debug.bin] Error 1
>     > scons: building terminated because of errors.
>     >
>     > I am using Ubuntu 10.04.
>     > I appreciate a lot if someone can help.
>     >
>     >
>     > 
>     >
>     ------------------------------------------------------------------------
>     >
>     > _______________________________________________
>     > m5-users mailing list
>     > [email protected] </mc/[email protected]>
>     > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
>
>     _______________________________________________
>     m5-users mailing list
>     [email protected] </mc/[email protected]>
>     http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
>
>
>  
>
>
> _______________________________________________
> m5-users mailing list
> [email protected]
> http://m5sim.org/cgi-bin/mailman/listinfo/m5-users

_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users

Reply via email to