Re: [Gems-users] Opal compilation and traces

[Dan Gibson <degibson@xxxxxxxx>]

Is your DESTINATION the same as the place you're loading the opal module?
Are you sure that the code is actually called?


Mishali Naik wrote:
> I have tried to change hard-coded reference but after I make clean and 
> rebuild opal (make module DESTINATION=..), I don't see the changes 
> taking place. No matter which file I make changes to/add printfs the 
> changes don't take place. Do I need to do anything additional to 
> ensure the changes to take place in opal? thanks a lot.
> On 10/30/06, *Dan Gibson* <degibson@xxxxxxxx 
> <mailto:degibson@xxxxxxxx>> wrote:
>     Taking a quick peek at the code, it looks like it might be looking for
>     the absolute path /scatch.local rather than the relative path
>     ./scratch.local. Either:
>
>     1) make a link from /scratch.local to your space OR
>     2) change the hard-coded references to relative paths
>
>     Regards,
>     Dan
>
>     Mishali Naik wrote:
>     > Thanks a lot for your prompt reply. I really appreciate it. I
>     > understand that it is hardcoded so if I have a symlink to
>     > scratch.local in the  directory where I am running simics, why is
>     > still giving error? Sorry if I am missing something.  Also if I add
>     > printf's in the opal code and then make clean and rebuild opal, I
>     > don't see the changes taking place. What could the problem be?
>     >
>     >
>     >
>     > 
--
http://www.cs.wisc.edu/~gibson [esc]:wq!