Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 12/12/2012 in all areas

  1. Ok, I think you have messed up the file permissions in your "objdir" directory by calling "configure" through sudo. (Why?!) You should start afresh by removing the "objdir" directory first, or try the following from within a "new" build directory. Call "configure" without the "CPPFLAGS=-fpermissive" (Where did you get that from anyway?), and compile as regular user. Afterwards you can install via sudo: ../configure --prefix=/usr/local/systemc-2.3 make sudo make install Greetings from Oldenburg, Philipp
    1 point
  2. In general, a failing libtool indicates a local problem with your environment. Please check for free space, directory permission, etc. You use a filesystem with sipport for symbolic links, right? (i.e. not NTFS, FAT32)? Do you try to cross-compile? That said, can you please post the output of the call (incl. the parameters given to) the 'configure' script? You somehow added -fpermissive to the compiler flags, which is a bad, if not very bad idea. /Philipp
    1 point
  3. You should be able to increase the Visual Studio stack with /Zm (from memory). You can increase the SC_THREAD stack size with the set_stack_size() method of SystemC - but if that works, I would still suspect you are declaring large stack allocated arrays in the SC_THREADs. Alan
    1 point
×
×
  • Create New...