nss build error

[Ryan Schmidt]

On Mar 20, 2009, at 17:42, William Davis wrote:

> trying to upgrade nss gave this build error:
>
> cc -dynamiclib -compatibility_version 1 -current_version 1 - 
> install_name /opt/local/lib/libssl3.dylib - 
> headerpad_max_install_names -L/opt/local/lib  -o  
> Darwin9.6.0_DBG.OBJ/libssl3.dylib Darwin9.6.0_DBG.OBJ/derive.o  
> Darwin9.6.0_DBG.OBJ/prelib.o Darwin9.6.0_DBG.OBJ/ssl3con.o  
> Darwin9.6.0_DBG.OBJ/ssl3gthr.o Darwin9.6.0_DBG.OBJ/sslauth.o  
> Darwin9.6.0_DBG.OBJ/sslcon.o Darwin9.6.0_DBG.OBJ/ssldef.o  
> Darwin9.6.0_DBG.OBJ/sslenum.o Darwin9.6.0_DBG.OBJ/sslerr.o  
> Darwin9.6.0_DBG.OBJ/ssl3ext.o Darwin9.6.0_DBG.OBJ/sslgathr.o  
> Darwin9.6.0_DBG.OBJ/sslmutex.o Darwin9.6.0_DBG.OBJ/sslnonce.o  
> Darwin9.6.0_DBG.OBJ/sslreveal.o Darwin9.6.0_DBG.OBJ/sslsecur.o  
> Darwin9.6.0_DBG.OBJ/sslsnce.o Darwin9.6.0_DBG.OBJ/sslsock.o  
> Darwin9.6.0_DBG.OBJ/ssltrace.o Darwin9.6.0_DBG.OBJ/sslver.o  
> Darwin9.6.0_DBG.OBJ/authcert.o Darwin9.6.0_DBG.OBJ/cmpcert.o  
> Darwin9.6.0_DBG.OBJ/nsskea.o Darwin9.6.0_DBG.OBJ/sslinfo.o  
> Darwin9.6.0_DBG.OBJ/ssl3ecc.o Darwin9.6.0_DBG.OBJ/ 
> unix_err.o   ../../../../dist/Darwin9.6.0_DBG.OBJ/lib/libfreebl.a  - 
> L../../../../dist/Darwin9.6.0_DBG.OBJ/lib -lnss3 -lnssutil3 - 
> L../../../../dist/Darwin9.6.0_DBG.OBJ/lib -lplc4 -lplds4 -lnspr4  - 
> dylib_file /opt/local/lib/libsoftokn3.dylib:../../../../dist/ 
> Darwin9.6.0_DBG.OBJ/lib/libsoftokn3.dylib
> Undefined symbols:
>   "_CERT_NewTempCertificate", referenced from:
>       _ssl3_HandleCertificate in ssl3con.o
>       _ssl3_HandleCertificate in ssl3con.o
>       _ssl2_ClientHandleServerCert in sslcon.o
>       _ssl2_HandleClientCertificate in sslcon.o
>       _ssl3_ServerHandleSessionTicketXtn in ssl3ext.o
>       _ConvertToSID in sslsnce.o
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[2]: *** [Darwin9.6.0_DBG.OBJ/libssl3.dylib] Error 1
> make[1]: *** [libs] Error 2
> make: *** [libs] Error 2

I see the same thing, on Mac OS X 10.5.6 Intel with Xcode 3.1.2  
(iPhone SDK 2.2.1), if the previous version of the port is active. I  
was able to work around it by deactivating the old version first. You  
could file this as a bug in the issue tracker.