I added LDFLAGS=-static and recomplied on a redhat 9.0 box. the target runs on redhat 7.3 box looks fine. but i found something strange.
When I use kill -USR2 <pid> have tinc dump connection information. It says"cipher 0 digest 0 maclength 0 compression 0 options 4 status 0018 nexthop ..." to anyother hosts, but says "at MYSELF cipher 91 digest 6 4 maclength 4 compression 5 options 4 status 0018 nexthop", I don't known what wrong or it's just ok? When I use 1.0.3 static downloaded fron tinc-vpn site. both side says cipher and compression ok. ----- Original Message ----- From: "Guus Sliepen" <[email protected]> To: <[email protected]> Sent: Tuesday, April 28, 2009 7:03 PM Subject: Re: Can tinc be complied with openssl 0.9.6? On Tue, Apr 28, 2009 at 12:28:36PM +0800, Starmoon wrote: > I have some redhat 7.3 boxes running as router/server and can't upgrade > them.(too many setup things to do). Is there anyway to modify tinc 1.0.9 to > complie with openssl 0.9.6b? > > Or someone can tell me how to staticly complie tinc with openssl? I think compiling statically is the best option. To create a static binary, call configure with the extra option LDFLAGS=static, for example: ./configure --sysconfdir=/etc --localstatedir=/var --disable-nls LDFLAGS=-static -- Met vriendelijke groet / with kind regards, Guus Sliepen <[email protected]> > _______________________________________________ > tinc mailing list > [email protected] > http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc > _______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
