Jamie Nicolson wrote: > Steven T. Hatton wrote: > > > Short questions: > > > > Does anybody have JSS 3.1.1 working on Solaris 8? > > My desktop machine is Solaris 8. It is always the very first platform > that "works" for me. However, I use Sun's compilers, not GCC.
I'll have to forego trying to compile it for now. The problem could be any number of things, from OS patches, to the fact that I compiled gcc myself, to which make I use, etc. > In any case, you only want to use the libraries, not build them, so > let's concentrate on getting that working and forget about building JSS. > > The best documentation there is on all the pieces you need to gather to > get JSS working is at: > http://mozilla.org/projects/security/pki/jss/using_jss.html > > > One of the problems I have is not knowing how to test that things are > > working. The sample code did not compile. I don't know if is expected > > to. When i tried to hand hack it, I was still unable to get it > > working. Perhaps I simply need to figre out how to "initialize" the > > provider, but without some sense that the underlying software is > > working, that seems like an exercise in masochism. > > Which sample program is not compiling? Please be specific about the > problems you are encountering so I have a chance of debugging them. For > example, mozilla/security/jss/samples/SigTest.java should work. To start with, I simply tried to run "make", and that sure didn't work. I could probably go in and play with the Makefile and the source code to get it to work. Here's an example of the errors I got when trying to compile the sample code: bash-2.03$ javac SSLClient.java SSLClient.java:263: Wrong number of arguments in constructor. new CryptoManager.InitializationValues ^ Note: SSLClient.java uses or overrides a deprecated API. Recompile with "-deprecation" for details. 1 error, 1 warning bash-2.03$ I actually went in and fixed that at one point. I everything may be set up correctly. I would just like to have a better way of verifying things before I dive into trying to write java code. You may recall I started trying to set up a certificate database directory and got hung up on the descrepencies between the documentation and the new functionality of the NSS tools. > > I'd love to have all the relevent nspr, nss, jss, etc tarballed in one > > file which I could unpack in say /usr/local or /opt, perhaps set some > > links and environment variable. Of course I'm suggesting > > /usr/local/jss as the place all other files would fall under. i.e., > > tar xvfz jss-tarbal.tar.gz would place only jss in $PWD, and all the > > other file under $PWD/jss. > > The closest thing we have to this is the binary release packages and the > "Using JSS" doc given above. I don't see us going any further than that. > We provide an SDK, not a packaged application. Our clients are not > end-users, but programmers who have to decide where they want to put > things. > I'm assuming you got my e-mail with the results of my build as well as my environment. If you are interested, that may give some indication of where the problem is wrt compiling. I'm currently working on getting things set up with the binary builds, and won't be able to continue working on the compile in the short term. I guess what I would really like to have is a sample code directory in which I can simply run ./configure (or have a readme to help me hack the Makefile by hand); make; make test; or executed some tests by hand. For now, I believe I have things installed correctly, and simply need to figure out how to make things work. IIRC a while back when I worked with NSS there was some sample code and some fairly accurate instructions on how to get it going. Here's another thing that confused me. I've seen mdb and mdbinary.jar files around, but I don't know what they are for. I looked around for an explanation of the mdb and mdbinary.jar, etc., but didn't find anything. Perhaps I should know what these are, but I don't. A find on the "using jss" page for "mdb" didn't hit anything, so I assume I can ignore these files? In particular I'm talking about this: ftp://ftp.mozilla.org/pub/security/jss/releases/JSS_3_1_1_RTM/SunOS5.8_OPT.OBJ/mdbinary.jar A couple of other things which I found confusing were two comments by Wan-Teh: "By the way, you also need to install the libnssckbi.so in your NSS config directory (where your cert7.db, key3.db, and secmod.db are)." This may be covered somewhere in the documentation, but It isn't jumping out at me. He also told me: "You are missing two .so's for 32-bit Solaris SPARC. libfreebl_pure32_3.so libfreebl_hybrid_3.so These need to be installed in the same directory as libnss3.so on 32-bit Solaris SPARC." - Wan-Teh This I take to mean if I put all my 64-bit files in /usr/local/nss-3.3.1 the two libfreebl*.so files go there as well. I don't take him to mean I need a separate install of the 32-bit NSS as well. Is that correct? > > P.S. I just downloaded, built, and installed GCC 2.95.3, and used it to > build NSPR, NSS, and JSS on my Solaris 8 box. I followed the build > instructions, and it all worked. So there is indeed something different > about your setup or build procedure. NSS officially supports GCC 2.95.3 > on Solaris; are you using a different version? No, but I may have chosen a different option somewhere. As I said above, it could be some other gnu tool, or something like that which is of a different version. Thanks, Steven
