[gem5-dev] Re: Problem with libelf

2020-08-25 Thread Gabe Black via gem5-dev
For reasons I won't bother to get into here, I just fought with using python 3 as the interpreter in gem5, and reran into what I think was this issue: https://gem5.atlassian.net/browse/GEM5-731 After some digging I found that it was this same issue, so I'm extra motivated for it to be fixed now.

[gem5-dev] Re: Problem with libelf

2020-08-24 Thread Jason Lowe-Power via gem5-dev
I finally got back around to this :). Here's an updated issue and some WIP changes: https://gem5.atlassian.net/browse/GEM5-752. I updated our code to work with current libelf, which was pretty simple except for one change from 1998 :D. There's two things missing: 1. I'm not sure how to tell scons

[gem5-dev] Re: Problem with libelf

2020-08-11 Thread Gabe Black via gem5-dev
I see that we had a local version of libelf as far back as when we started using scons in 2004, where we referred to it's SConscript in m5/libelf/SConscript (not src/m5 or util/m5, just m5), although that directory and all its history seems to have been dropped during one of the times we switched v

[gem5-dev] Re: Problem with libelf

2020-08-11 Thread Gabe Black via gem5-dev
I'm pretty sure it's been that way "forever", where forever is defined as as far back as I can remember. Looking at the history, I see that Nate replaced a GNU libelf with "autoconf nastiness" (I can imagine), and replaced it with a freeBSD version in 2007, so it's been that way at least as long as