Jump to content

cubbins

Members
  • Posts

    1
  • Joined

  • Last visited

cubbins's Achievements

Member

Member (1/2)

0

Reputation

  1. Above is a good discussion, whose final solution was to make sure your current "shell" or "window" to execute a command is the same as the one which contains the environment variables. Good show to arrive at a solution. However, in my case, it is not a solution. I have all the proper environment variables defined, and I still have the error "libsystemc-2.3.3.so not found". A quick and dirty solution for me is here: assume the system is looking in all the customary places for library files.With me after having no success trying to define environment variables for this library, I simply copied the "libsystem-2.3.3.so" to the system directory /usr/lib, a common place for library files. I used the command "sudo cp libsystem-2.3.3.so /usr/lib/" And that got it. Why my environment variables for systemc library files did not work. I do not know why. Does it matter libsystem-2.3.3.so is located in /usr/lib, a common place for library files, probably not, yet the difference to me is, I've gotten over this hump and the software I am interested in is working.
×
×
  • Create New...