Hi Gabe, I have more details about this. In this use case, SST initialized the Python environment before adding the "gem5 object". This gem5 object will add more Python stuff from gem5 to the environment.
The function that does that is initPython() https://gem5.googlesource.com/public/gem5/+/refs/heads/develop/ext/sst/gem5.cc#415 The following commands will pull the docker image for SST testing purposes (note that host_gem5_root and guest_gem5_root must be specified), ``` docker run -u $UID:$GID --volume "${host_gem5_root}":"${guest_gem5_root}" -w \ "${guest_gem5_root}" --rm gcr.io/gem5-test/sst-env \ bash -c "\ scons build/RISCV/libgem5_opt.so -j${nproc} --without-tcmalloc; \ cd ext/sst; \ make clean; make; \ sst --add-lib-path=./ sst/example.py; ``` We appreciate your help! Regards, Hoa Nguyen On 12/8/21, Jason Lowe-Power <[email protected]> wrote: > Hey Gabe, > > This change breaks the SST integration. In the SST integration python is > initialized from the SST module, not from init.cc (this is because SST has > their own python interpreter). > > We would appreciate some help in fixing this. Hoa and Giacomo can give you > an example that's breaking to help you fix it, I believe. > > https://gem5-review.googlesource.com/c/public/gem5/+/49413 > > There's strong interest in having the SST integration working in this > current release. We've spent a lot of time figuring out all of the > intricacies and would appreciate any help you can provide in these last few > days before the release! > > Thanks! > > Jason > _______________________________________________ gem5-dev mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
