On Sun, Nov 22, 2009 at 9:08 PM, Nelson B Bolyard <[email protected]> wrote:
> On 2009-11-22 04:44 PST, Maciej Bliziński wrote:
>> Why is ldd showing that the nspr libraries are found, but they don't
>> get loaded when running shlibsign?  Do you have any hints?
>
> Yes, it's because of the changes you've made to freebl.

In this case the cause was the FREEBL_NO_DEPEND environment variable.

>> [1] http://www.opencsw.org/
>> [2] 
>> https://gar.svn.sourceforge.net/svnroot/gar/csw/mgar/pkg/nss/trunk/Makefile
>> [3] https://gar.svn.sourceforge.net/svnroot/gar/csw/mgar/pkg/nss/trunk/files/
>
> Considering that Solaris and OpenSolaris are among the main platforms for
> which NSS is developed and supported (Sun presently employs most of the
> NSS developers), you should not need to make any changes to NSS at all.
> If you want to change the directory in which the shared libraries are
> installed, and where they are searched, that's fine, a good idea.
> But you should not need to make any other changes to NSS.

Ideally, I'd like to pass the -L and -R flags via environment
variables, especially since I'm building the library for both 32 and
64 bit architectures.  Our build system expects builds to read the
flags via $LDFLAGS and $LD_OPTIONS:

          Arch: sparc
        Kernel: sparcv9

Default ISA 32: sparcv8
Default ISA 64: sparcv9

Requested ISAs: sparcv8 sparcv9 i386 amd64
   Needed ISAs: sparcv8 sparcv9
    Build ISAs: sparcv8 sparcv9

  ISAEXEC dirs: /opt/csw/bin /opt/csw/sbin /opt/csw/libexec
 ISAEXEC files:

 Merge include:
 Merge exclude:     /opt/csw/share/info/dir /opt/csw/lib/.*\.la .*\~
/opt/csw/lib/.*\.a

    Modulators: ISA
   Modulations: isa-sparcv8 isa-sparcv9

Requested compiler flags:

* Modulation isa-sparcv8: ISA=sparcv8
     Build Host =
           PATH =
/home/maciej/src/opencsw/pkg/nss/branches/upstream-work/work/install-isa-sparcv8/opt/csw/bin:/home/maciej/src/opencsw/pkg/nss/branches/upstream-work/work/install-isa-sparcv8/opt/csw/bin:/home/maciej/src/opencsw/pkg/nss/branches/upstream-work/work/install-isa-sparcv8/opt/csw/sbin:/home/maciej/src/opencsw/pkg/nss/branches/upstream-work/work/install-isa-sparcv8/opt/csw/sbin:/opt/csw/bin:/opt/csw/bin:/opt/csw/sbin:/opt/csw/sbin:/opt/studio/SOS11/SUNWspro/bin:/home/maciej/src/opencsw/pkg/nss/branches/upstream-work/gar/bin:/usr/bin:/usr/sbin:/usr/java/bin:/usr/ccs/bin:/usr/openwin/bin
PKG_CONFIG_PATH = /opt/csw/lib/pkgconfig
         CFLAGS = -g -xarch=v8 -I/opt/csw/include
       CXXFLAGS = -g -xarch=v8 -I/opt/csw/include
       CPPFLAGS = -I/opt/csw/include
        LDFLAGS = -xarch=v8 -L/opt/csw/lib
     LD_OPTIONS = -R/opt/csw/lib/$ISALIST -R/opt/csw/lib
        ASFLAGS =
       OPTFLAGS = -g -xarch=v8

* Modulation isa-sparcv9: ISA=sparcv9
     Build Host =
           PATH =
/home/maciej/src/opencsw/pkg/nss/branches/upstream-work/work/install-isa-sparcv9/opt/csw/bin/sparcv9:/home/maciej/src/opencsw/pkg/nss/branches/upstream-work/work/install-isa-sparcv9/opt/csw/bin:/home/maciej/src/opencsw/pkg/nss/branches/upstream-work/work/install-isa-sparcv9/opt/csw/sbin/sparcv9:/home/maciej/src/opencsw/pkg/nss/branches/upstream-work/work/install-isa-sparcv9/opt/csw/sbin:/opt/csw/bin/sparcv9:/opt/csw/bin:/opt/csw/sbin/sparcv9:/opt/csw/sbin:/opt/studio/SOS11/SUNWspro/bin:/home/maciej/src/opencsw/pkg/nss/branches/upstream-work/gar/bin:/usr/bin:/usr/sbin:/usr/java/bin:/usr/ccs/bin:/usr/openwin/bin
PKG_CONFIG_PATH = /opt/csw/lib/64/pkgconfig
         CFLAGS = -g -xarch=v9 -I/opt/csw/include
       CXXFLAGS = -g -xarch=v9 -I/opt/csw/include
       CPPFLAGS = -I/opt/csw/include
        LDFLAGS = -xarch=v9 -L/opt/csw/lib/64
     LD_OPTIONS = -R/opt/csw/lib/$ISALIST -R/opt/csw/lib/64
        ASFLAGS =
       OPTFLAGS = -g -xarch=v9

What's the best way to make the NSS build read LDFLAGS and LD_OPTIONS?

> Be aware that the NSS team does not support downstream copies of NSS that
> have been significantly modified by downstream developers.  If you find bugs
> in NSS, we encourage you to file bugs against the main upstream NSS source
> code repository, and contribute patches.

I guess the main need for changes are the nss-config and nss.pc files,
since other software packages require them to build.  I've seen that
Linux distributions create those files downstream.  Is there any
chance for upstream nss-config and nss.pc?

Maciej
-- 
dev-tech-crypto mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-crypto

Reply via email to