Re: [Gems-users] Opal compilation and traces

["Mishali Naik" <mishalinaik@xxxxxxxxx>]

Yes my destination is the same as the place I am loading opal module from. Yes, I am sure that the code is actually called because I have even tried to modify the existing printfs in opal.c but I don't even see those changes being made. for example in module/opal.c:
 if (install_error == Sim_Set_Ok) {
      printf( "Mish: successful installation of the opal queue.\n");
    } else {
      printf( "error installing opal queue.\n");
      exit(1);
    }
This change to the printf should have taken place, but indeed its not ...
thanks a lot!

On 10/30/06, Dan Gibson < degibson@xxxxxxxx> wrote:

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
>