On 8/23/06, Steve Reinhardt <[EMAIL PROTECTED]> wrote:
Michael Van Biesbrouck wrote:
> On 8/23/06, Steve Reinhardt <[EMAIL PROTECTED]> wrote:
>> Yea, I just noticed that in spite of the name, --enable-shared seems to
>> create a non-shared version of the library as well. (Or maybe the
>> non-shared version always gets built?)
>
> The non-shared library is always built, but it is never usable for
> embedded purposes (thus the errors that were being reported).
Did you see that documented somewhere, or are you just saying that based
on your experience? I saw this note here:
http://www.python.org/doc/ext/link-reqs.html
that sounded like it might explain the problems you were having with the
static library, but didn't actually try it to see if it helped.
That might fix the problems that I have experienced. The purpose
there is to support loading shared objects for dynamic extensions, so
I'm not sure that any benefit would occur (dynamic linking will still
occur even though the static library was used). It might remove the
LD_LIBRARY_PATH requirement that I have.
Is the counter initialization bug easy to fix? I would like to start
using M5 as soon as possible.
Michael
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
