Log inUsernamePassword
Log me on automatically each visit    
Register
Register
Log in to check your private messages
Log in to check your private messages
SMS Forum Index » SMS User Support

Post new topic   Reply to topic
Failed to upgrade tor software
View previous topic :: View next topic  
Author Message
Lars
Senior Member


Joined: 25 Oct 2010
Posts: 134

PostPosted: Tue Nov 20, 2012 1:39 pm    Post subject: Failed to upgrade tor software Reply with quote

This is not really a S*M*S-problem, rather a Slackbuild one, but I thought I might ask anyway.
I've been running S*M*S 1.6.0 on an i486 eeePC since july 2011. At first merely as a httpd-, nfs- and nfs-server. -In march this year, very much with Your help, I configured it to also work as a tor-node using the at the time current Slackbuild for tor, namely tor-0.2.2.35. To do this I had to install the devel-packages, and since then I installed several network tools for examining the the traffic. -I only mention this because this is my main reason for not upgrading to S*M*S-2. At least not now.

Now to my problem: I recently installed Slackware 14.0-x86_64 on a workstation (a lot more energyconsuming) and installed the tor-kit just to be able to attach some clientfunctionalities. I used SBopkg and it used tor-0.2.2.37 together with libevent-2.0.10, tor's only dependency.
torproject.org immediately complained about the outdated tor 0.2.2.37 and I decided to try to upgrade it. Just be clear: In my 64-bit-version of Slackware. -I fetched the stable current version 0.2.2.39 from torproject, changed the version-line in the tor.SlackBuild-script (made for 0.2.2.37) and it worked. The upgrade also worked!

I thought I should try the same in my S*M*S-server based on Slackware 13.37 and 32-bit. Since my tor-installation in S*M*S included the same libevent-version that worked with tor-0.2.2.39, namely libevent-2.0.10-i486-1_SBo.tgz, I thought it might work?

Well it didn't! I fetched the current Slackbuild and sourcecode for tor-0.2.2.37 (for Slackware 13.37) and first tried to build that: It left the tmp build-directory with 2 ERRORS quite late in the script, in a section that starts with "ranlib libtor.a"
and lists a lot of lines complaints about "undefined references" under for instance
./libtor.a(main.o): In function `connection_add', `handle_signals', `configure_nameservers', `tor_libevent_initialize' et c:
I'm not the man to interpret that. Shocked

It seems very strange though that a Slackbuild script for tor-0.2.2.37 in 13.37 i486 that uses exactly the same sourcecode that the similar Slackbuild script for 14.0 x86_64 doesn't build?
I've checked that my tor-server is down while building.
The SlackBuild of libevent for Slackware 14.0 and 13.37 use the same sourcecode: libevent-2.0.10-stable.tar.gz.

I really can't figure out why it doesn't build?

The only time so far I've experienced a Slackbuild that doesn't build was a recent script for grub-legacy in Slackware 14.0.

Has anyone else experienced the same? Or succeeded to build tor-0.2.2.37 in i486?

Best regards
Lars
Back to top
View user's profile Send private message
gerasimos_h
Site Admin


Joined: 09 Aug 2007
Posts: 1752
Location: Greece

PostPosted: Tue Nov 20, 2012 7:30 pm    Post subject: Reply with quote

Just to clear something, that I didn't understand, did you build libevent 2.0.10 again in SMS-1.6.0 or install an already build package?
Any reason you don't build latest libevent 2.0.20?

Can you post the build error?

gerasimos_h

_________________
Superb! Mini Server Project Manager
http://sms.it-ccs.com
Back to top
View user's profile Send private message Visit poster's website
Lars
Senior Member


Joined: 25 Oct 2010
Posts: 134

PostPosted: Tue Nov 20, 2012 7:58 pm    Post subject: Reply with quote

No, I didn't rebuild libevent 2.0.10 in SMS-1.6.0. I built it with Slackbuild in march this year and had it already installed.
In that way in the same setup as in Slackware 14: I installed tor 0.2.2.37 in Slackware last week and upgraded to 0.2.2.39 yesterday, with libevent 2.0.10 already installed.

No, I've got no specific reason for not upgrading libevent to 2.0.20! On the other hand I could find no reason for doing that as 2.0.10 obviously was enough for tor 0.2.2.39.

The build error message is quite long, but I don't know any other way to paste it than here (you can always delete it afterwards!): This output is for an effort with 02.2.39, made after I tried 0.2.2.37, but the output and ending were the same.
Code:
ranlib libtor.a
gcc -DHAVE_CONFIG_H -I. -I../..  -DSHARE_DATADIR="\"/usr/share\"" -DLOCALSTATEDIR="\"/var\"" -DBINDIR="\"/usr/bin\"" -I../../src/common     -O2 -march=i486 -mtune=i686 -Wall -fno-strict-aliasing -MT tor_main.o -MD -MP -MF .deps/tor_main.Tpo -c -o tor_main.o tor_main.c
mv -f .deps/tor_main.Tpo .deps/tor_main.Po
gcc  -O2 -march=i486 -mtune=i686 -Wall -fno-strict-aliasing   -o tor tor_main.o ./libtor.a ../common/libor.a ../common/libor-crypto.a ../common/libor-event.a -lz -lm -levent -lssl -lcrypto   -lpthread -ldl
./libtor.a(main.o): In function `connection_add':
main.c:(.text+0x9de): undefined reference to `event_new'
main.c:(.text+0xa09): undefined reference to `event_new'
./libtor.a(main.o): In function `handle_signals':
main.c:(.text+0x354f): undefined reference to `event_new'
./libtor.a(dns.o): In function `launch_test_addresses':
dns.c:(.text+0x359): undefined reference to `evdns_base_resolve_ipv4'
./libtor.a(dns.o): In function `configure_nameservers':
dns.c:(.text+0xd0f): undefined reference to `evdns_base_resolv_conf_parse'
dns.c:(.text+0xd24): undefined reference to `evdns_base_count_nameservers'
dns.c:(.text+0xd76): undefined reference to `evdns_base_count_nameservers'
dns.c:(.text+0xd9c): undefined reference to `evdns_base_set_option'
dns.c:(.text+0xdb9): undefined reference to `evdns_base_set_option'
dns.c:(.text+0xde0): undefined reference to `evdns_base_set_option'
dns.c:(.text+0xe29): undefined reference to `evdns_base_set_option'
dns.c:(.text+0xed1): undefined reference to `evdns_base_set_option'
./libtor.a(dns.o):dns.c:(.text+0xeee): more undefined references to `evdns_base_set_option' follow
./libtor.a(dns.o): In function `configure_nameservers':
dns.c:(.text+0xf01): undefined reference to `evdns_base_search_clear'
dns.c:(.text+0xf0e): undefined reference to `evdns_base_clear_nameservers_and_suspend'
dns.c:(.text+0xf21): undefined reference to `evdns_base_resume'
dns.c:(.text+0xf59): undefined reference to `evdns_base_new'
./libtor.a(dns.o): In function `launch_wildcard_check.clone.10':
dns.c:(.text+0x13b2): undefined reference to `evdns_base_resolve_ipv4'
./libtor.a(dns.o): In function `dns_resolve_impl':
dns.c:(.text+0x21b7): undefined reference to `evdns_base_resolve_ipv4'
dns.c:(.text+0x2290): undefined reference to `evdns_base_resolve_reverse_ipv6'
dns.c:(.text+0x26d7): undefined reference to `evdns_base_resolve_reverse'
./libtor.a(dns.o): In function `dns_init':
dns.c:(.text+0x3780): undefined reference to `evdns_set_random_bytes_fn'
./libtor.a(dns.o): In function `dns_reset':
dns.c:(.text+0x37d8): undefined reference to `evdns_base_clear_nameservers_and_suspend'
dns.c:(.text+0x37e5): undefined reference to `evdns_base_search_clear'
dns.c:(.text+0x3831): undefined reference to `evdns_base_new'
./libtor.a(dns.o): In function `dns_launch_correctness_checks':
dns.c:(.text+0x4881): undefined reference to `event_new'
./libtor.a(dnsserv.o): In function `dnsserv_configure_listener':
dnsserv.c:(.text+0x97e): undefined reference to `evdns_add_server_port_with_base'
../common/libor.a(procmon.o): In function `tor_process_monitor_free':
procmon.c:(.text+0x269): undefined reference to `event_free'
../common/libor.a(procmon.o): In function `tor_process_monitor_new':
procmon.c:(.text+0x30f): undefined reference to `event_new'
../common/libor-event.a(compat_libevent.o): In function `tor_libevent_initialize':
compat_libevent.c:(.text+0x352): undefined reference to `event_config_new'
compat_libevent.c:(.text+0x36c): undefined reference to `event_config_set_flag'
compat_libevent.c:(.text+0x374): undefined reference to `event_base_new_with_config'
compat_libevent.c:(.text+0x381): undefined reference to `event_config_free'
../common/libor-event.a(compat_libevent.o): In function `periodic_timer_new':
compat_libevent.c:(.text+0x8aa): undefined reference to `event_new'
../common/libor-event.a(compat_libevent.o): In function `periodic_timer_free':
compat_libevent.c:(.text+0xa44): undefined reference to `event_free'
collect2: ld returned 1 exit status
make[3]: *** [tor] Error 1
make[3]: Leaving directory `/tmp/SBo/tor-0.2.2.39/src/or'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/SBo/tor-0.2.2.39/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/SBo/tor-0.2.2.39'
make: *** [all] Error 2
#
Back to top
View user's profile Send private message
Lars
Senior Member


Joined: 25 Oct 2010
Posts: 134

PostPosted: Tue Nov 20, 2012 8:25 pm    Post subject: Reply with quote

PS. tried to find a way to make the output more specific so I let Slackbuild print the whole buildscript in text. When I studied it closer there were no indications to where in make [1], make [2] or make [3] the errors occured. Just which directories that were involved with each and that were the ones listed in the end of the code i pasted.
Back to top
View user's profile Send private message
gerasimos_h
Site Admin


Joined: 09 Aug 2007
Posts: 1752
Location: Greece

PostPosted: Tue Nov 20, 2012 8:41 pm    Post subject: Reply with quote

Is this an SMS-1.6.0 installation?
I tried to build libevent-2.0.10 and TOR-0.2.2.39 on SMS-1.6.0 and had no problems...
I attach my libevent-2.0.10 to test, and try to build TOR.

gerasimos_h



libevent-2.0.10-i486-1sms.txz
 Description:
libevent for SMS-1.6.0 GCC-4.5.2

Download
 Filename:  libevent-2.0.10-i486-1sms.txz
 Filesize:  276.78 KB
 Downloaded:  466 Time(s)


_________________
Superb! Mini Server Project Manager
http://sms.it-ccs.com
Back to top
View user's profile Send private message Visit poster's website
Lars
Senior Member


Joined: 25 Oct 2010
Posts: 134

PostPosted: Tue Nov 20, 2012 9:08 pm    Post subject: Reply with quote

Thank You Gerasimos! You are very kind!

Yes it is a SMS-1.6.0 i486 installation I made in july 2011.
When I read the end of the errormessage it seemed to mostly concern libevent?
The tor-node has been up since april, perhaps my installed libevent-2.0.10 has got corrupted in any way.

I'll try your binary tomorrow, perhaps also try to build one myself, and come back with the result.

Thanks again Smile !

Lars
Back to top
View user's profile Send private message
gerasimos_h
Site Admin


Joined: 09 Aug 2007
Posts: 1752
Location: Greece

PostPosted: Tue Nov 20, 2012 9:16 pm    Post subject: Reply with quote

I don't think it get corrupted, trymy libevent and tyr building yours and see how it goes..

gerasimos_h

_________________
Superb! Mini Server Project Manager
http://sms.it-ccs.com
Back to top
View user's profile Send private message Visit poster's website
Lars
Senior Member


Joined: 25 Oct 2010
Posts: 134

PostPosted: Wed Nov 21, 2012 10:06 am    Post subject: Reply with quote

Your success in building tor and your attached libevent encouraged me to at least try my assumption about libevent.
In all cases I had Your libevent as a last way out.

I simply reinstalled the libevent I built in march:
# upgradepkg --reinstall libevent-2.0.10-i486-1_SBo.tgz

And the build of tor-0.2.2.39-i486-3_SBo.tgz immediately worked Very Happy !

Really, I am not sure about the corruption of libevent, but it's a guess anyway. I my Slackware 14 libevent was not a fresh install, it had been in use for about a week. There the build of tor-0.3.2.39 worked at once.
In my SMS-1.6.0 libevent has been in use for 7-8 months and something had obviously happened to it that destructed the build of tor.

I save your libevent-2.0.10-i486-1sms.txz for a rainer day.

Anyway: Again You have been very helpful Smile and Your S*M*S-server, even if 1½ years old, has worked as a charm since I installed it! Thanks again!

My best regards
Lars
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    SMS Forum Index » SMS User Support All times are GMT + 2 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum

SMS - Superb! Mini Server Project © 2016
Powered by phpBB © 2001, 2002 phpBB Group
iCGstation v1.0 Template By Ray © 2003, 2004 iOptional