in reply to Re^2: Creating my own perl module from c++ code
in thread Creating my own perl module from c++ code

Well, in your build directory, ./lib is the directory where you may (but don't have to) work on your Perl sources. It's not the directory where the finished products are placed - neither the Perl modules, nor the C libraries. They are in subdirectories in blib. Try, after running 'make':
perl -Iblib/lib -Iblib/arch -MTamarLog -e '...'
But, assuming you have test files, should have succeeded, as this is what 'make test' does as well.

Replies are listed 'Best First'.
Re^4: Creating my own perl module from c++ code
by Anonymous Monk on Jul 22, 2009 at 11:00 UTC
Re^4: Creating my own perl module from c++ code
by tomerb (Novice) on Jul 22, 2009 at 13:10 UTC
    I get the exact same error as before when I try this.
      Did you actually run a succesful make? Because the error seems to suggest it finds a TamarLog.so file in /usr/perl5/site_perl/5.8.4/sun4-solaris-64int/auto/TamarLog/ instead of picking up the one in ./blib/arch.
Re^4: Creating my own perl module from c++ code
by tomerb (Novice) on Jul 22, 2009 at 14:49 UTC
    here is the output of "nm ScriptLog.so":

    [57] | 0| 0|FUNC |GLOB |0 |UNDEF |__1c2k6Fpv_v_
    [53] | 0| 0|FUNC |GLOB |0 |UNDEF |__1c2n6FI_pv_
    [63] | 2552| 8|FUNC |GLOB |0 |8 |__1cFGoLog2t5B6M_v_

    any idea why did the compilation create them UNDEF???