2 Replies Latest reply: May 10, 2013 2:17 AM by 988024 RSS

    built so file from spracv9 lib files

      I am very new on Solaris, and I have one confusion, please forgive me if it is very silly.

      I am building 64 bit so(shared object) file using make command. During compilation I need to use 64 bit library path (/usr/ucblib/sparcv9).

      I am using following path in MakeFile LIBB = -L/usr/ucblib/sparcv9 -L/usr/lib/sparcv9 -R/usr/ucblib/sparcv9 -R/usr/lib/sparcv9

      My question is when i will move this built so file from Solaris version 9 to 10/11 where sparcv9 may not be available, will there any impact on built lib file, or all depended lib from (/usr/ucblib/sparcv9) to migrate in built so lib file.

      Thanks in Advance
        • 1. Re: built so file from spracv9 lib files
          Let me preface my comments with the following:
          I have absolutely no skills on compiling files. I'm a hardware person.

          However your inquiry leads me to think you may have a misunderstanding on a couple of points.

          SPARCV9 libraries would be specific for use with particular hardware.
          SPARCV9 is not a generic reference to "64bit".

          Glance through: http://en.wikipedia.org/wiki/SPARC

          Are you expecting your shared objects to be limited to specific hardware?
          (No x86 compatibility? No Cool-Threads hardware compatibility? 32bit exclusion?)

          Now I'll let others choose to respond to your actual inquiry.


          Edited by: rukbat on May 9, 2013 12:48 PM
          You may have also chosen the wrong forum.
          Your post may be more appropriate to the Solaris Development sub-forum.
          • 2. Re: built so file from spracv9 lib files
            Thanks for your reply...

            We are not depends on H/W, we require 64 bit so file. so we need to set those LD_LIBRARY_PATH for completion and Run.

            Here are my question if you aware about them:
            1) Is user build so file get all depended so, like Java Runnable jar (Jar file includes all dependent jars)?
            If it is yes then correct me if I am wrong- We no need to worry about this dependent path for SPARCV9 or whatever, we already have our dependent in our built so.......

            Any help will be Appreciates.