[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #9058 [Tor]: tor current compile breakage "libor-crypto.a"

#9058: tor current compile breakage "libor-crypto.a"
-------------------------------+--------------------------------------------
 Reporter:  yancm              |          Owner:                    
     Type:  defect             |         Status:  new               
 Priority:  normal             |      Milestone:  Tor: 0.2.5.x-final
Component:  Tor                |        Version:  Tor: unspecified  
 Keywords:  tor-client netbsd  |         Parent:                    
   Points:                     |   Actualpoints:                    
-------------------------------+--------------------------------------------

Comment(by nickm):

 > Do we need to do something similar for ssl?

 Maybe, if /usr/pkg isn't in the search path by default.  (We'd like to
 migrate to just using pkg-config, but that patch isn't ready yet.)

 If you run that command line, but add "-L/usr/pkg/lib" right after the
 "gcc", does it start working?  If so, you could probably work around this
 issue by specifying LDFLAGS="-L/usr/pkg/lib" manually when you run
 configure.

 > Where is the best place to check to see if the autogen/configure scripts
 find the right ssl? (There may be a base system ssl?)

 The output of configure, when it talks about openssl

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9058#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs