issue 12
(No deb file for download) reported by miserlou
- Can somebody package this for me as a .deb?
:) :) :)
Can somebody package this for me as a .deb?
:) :) :)
Dec 10, 2009
issue 11
(epsilon make fail FreeBSD RELENG_8) reported by grarpamp
- 1.0 epsilon fails to compile on the subject OS version
because -ldl and -lresolv are invalid on that platform because the
functions reside in -lc, not separately.
remove them from the configure/makefile setup bits and things work fine.
no patch available at this time.
can we just have the standard major.minor release numbering from
now on please? maybe beta/rc[x] if need be.
it went gamma > delta > epsilon, which is in random order and thus bad.
thx.
1.0 epsilon fails to compile on the subject OS version
because -ldl and -lresolv are invalid on that platform because the
functions reside in -lc, not separately.
remove them from the configure/makefile setup bits and things work fine.
no patch available at this time.
can we just have the standard major.minor release numbering from
now on please? maybe beta/rc[x] if need be.
it went gamma > delta > epsilon, which is in random order and thus bad.
thx.
Dec 01, 2009
issue 6
(Unable to build torsocks) commented on by movax0x13
- I had the same problem in jaunty 9,04 but:
sudo aptitude install libtool
fixed it
I had the same problem in jaunty 9,04 but:
sudo aptitude install libtool
fixed it
issue 7
(Package for debian) commented on by pmatth...@debian.org
- I have already packaged it and suc. uploaded it do Debian, so this could be closed,
cheers.
I have already packaged it and suc. uploaded it do Debian, so this could be closed,
cheers.
Nov 20, 2009
issue 10
(Torsocks and Wikipedia) reported by likolenko
- (Sorry if this is off-topic. I couldn't find any better place to post it.)
THE PROBLEM: Proxychains provides the ability to chain multiple proxies,
which is becoming *increasingly* useful for Tor, if not critically
important, in terms of real-world usability. Here's why. More and more
sites (perhaps Wikipedia is the most horrible example) ban Tor explicitly
and *systematically* but don't deal as carefully with open proxies. So
chaining Tor and an open proxy (as an "extra exit") is a *very useful*
solution. This "magic trick" is really great: since I started to use it
(with proxychains), I've never had problems with any Tor bans. But, since
torsocks is better, I wouldn't want to continue to use proxychains.
CONCLUSION: torsocks is *useless* for editing Wikipedia. And more and more
of our favorite projects or sites ban us systematically just because they
can (not only is the list of exits so openly available, but it's almost
enticing to the greedy admin).
MY SUGGESTED SOLUTION: Could you make this feature available in torsocks?
You don't need to add advanced chain support, just hack it to support two
extra proxies (see NOTE below; using just one proxy should be allowed too,
of course), specified in the config file or as command line arguments, and
add an argument like "--pseudonymous" to mark its use explicitly. I'm sure
this would make many people happy.
I considered the word "pseudonymous" expressive enough of the risks
involved (although adding a warning/comment wouldn't hurt): unlike when
using random Tor exits, if the user forgets the open proxy enabled in the
config file, he will be "less anonymous", i.e. "pseudonymous", which is too
risky for what torsocks promises to be. Thus, forcing the user to always
need to use an explicit argument, suggestively named "pseudonymous", is
probably the best compromise between simplicity (=security) and power/choice.
Of course, providing a way to change the open proxy "exit" dynamically
(without restarting the socksified application) would be the greatest
solution. And I don't think Tor itself needs to support this feature
("external exits" or "non-Tor identities").
Or, if it does, could you talk to the Tor developers? I believe you're in a
better position to convince them.
... And then writing a (GUI) Tor + open-proxies manager (or even harvester)
(or adding one to Vidalia or Tork) would be almost trivial, I guess.
Moreover, this would render Tor use even more low-profile for many
adversaries, complementing the bridges.torproject.org solution. It just
looks like a logical addition.
NOTE: (potentially important!) allowing the chaining of two extra proxies
instead of just one may help, just in case Tor's detractors will start to
ban us by "FORWARDED_FOR".
(Sorry if this is off-topic. I couldn't find any better place to post it.)
THE PROBLEM: Proxychains provides the ability to chain multiple proxies,
which is becoming *increasingly* useful for Tor, if not critically
important, in terms of real-world usability. Here's why. More and more
sites (perhaps Wikipedia is the most horrible example) ban Tor explicitly
and *systematically* but don't deal as carefully with open proxies. So
chaining Tor and an open proxy (as an "extra exit") is a *very useful*
solution. This "magic trick" is really great: since I started to use it
(with proxychains), I've never had problems with any Tor bans. But, since
torsocks is better, I wouldn't want to continue to use proxychains.
CONCLUSION: torsocks is *useless* for editing Wikipedia. And more and more
of our favorite projects or sites ban us systematically just because they
can (not only is the list of exits so openly available, but it's almost
enticing to the greedy admin).
MY SUGGESTED SOLUTION: Could you make this feature available in torsocks?
You don't need to add advanced chain support, just hack it to support two
extra proxies (see NOTE below; using just one proxy should be allowed too,
of course), specified in the config file or as command line arguments, and
add an argument like "--pseudonymous" to mark its use explicitly. I'm sure
this would make many people happy.
I considered the word "pseudonymous" expressive enough of the risks
involved (although adding a warning/comment wouldn't hurt): unlike when
using random Tor exits, if the user forgets the open proxy enabled in the
config file, he will be "less anonymous", i.e. "pseudonymous", which is too
risky for what torsocks promises to be. Thus, forcing the user to always
need to use an explicit argument, suggestively named "pseudonymous", is
probably the best compromise between simplicity (=security) and power/choice.
Of course, providing a way to change the open proxy "exit" dynamically
(without restarting the socksified application) would be the greatest
solution. And I don't think Tor itself needs to support this feature
("external exits" or "non-Tor identities").
Or, if it does, could you talk to the Tor developers? I believe you're in a
better position to convince them.
... And then writing a (GUI) Tor + open-proxies manager (or even harvester)
(or adding one to Vidalia or Tork) would be almost trivial, I guess.
Moreover, this would render Tor use even more low-profile for many
adversaries, complementing the bridges.torproject.org solution. It just
looks like a logical addition.
NOTE: (potentially important!) allowing the chaining of two extra proxies
instead of just one may help, just in case Tor's detractors will start to
ban us by "FORWARDED_FOR".
Nov 20, 2009
WhatIsTorsocks (What is torsocks?) Wiki page commented on by likolenko
- For mike4004: You misunderstood gas's answer to paynito. You are talking about different things.
Do you need to install Tor separately, or is it included in the torsocks package? The former (you need to install Tor).
Now, do you need to install Tor in order to use torsocks at all? Obviously not (you don't need to install Tor). But this was a different question.
For mike4004: You misunderstood gas's answer to paynito. You are talking about different things.
Do you need to install Tor separately, or is it included in the torsocks package? The former (you need to install Tor).
Now, do you need to install Tor in order to use torsocks at all? Obviously not (you don't need to install Tor). But this was a different question.
issue 2
(compile problems on mac os x 10.5) commented on by rob...@roberthogan.net
- to be honest, i think i'm not going to be able to debug this one remotely. the
errors you're seeing are specific to a patch from an earlier poster in this thread
in the osx git branch. pity that osx can't be vm'd legitimately. hopefully Alex (in
comment 16) will take notice..
to be honest, i think i'm not going to be able to debug this one remotely. the
errors you're seeing are specific to a patch from an earlier poster in this thread
in the osx git branch. pity that osx can't be vm'd legitimately. hopefully Alex (in
comment 16) will take notice..
Sep 21, 2009
issue 2
(compile problems on mac os x 10.5) commented on by dlwim...@newcommunities.net
- yeah i found that file already. tsocks is the same way for obvious reasons. also, for future documentation it
seems the conf file is in /usr/local/etc/torsocks.conf by default on OS X. However even with
server = 127.0.0.1
server_port = 1080
tordns_enable = false (i found this line to be necessary when using tsocks before)
it cant seem to get anything to go through the proxy. I am using "ssh -D 1080 user@domain.org" as my
proxy btw. I may have misspoken before when i said it seemed to work after spitting out debug info. That was
just an initial impression. I think that at that point i had not added the disable tordns line in the config file
and so i got a "could not resolve hostname" line giving the impression that it might be working. Upon further
testing however, it seems that it freezes after the debug lines and does not send any information through the
proxy.
Here is a sample of the "debug" lines mentioned above:
torsocks ssh user@domain.org
21:43:20 libtorsocks(1391): The symbol connect$UNIX2003() was not found in any shared library. The error
reported was: dlsym(RTLD_NEXT, connect$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol connect$NOCANCEL$UNIX2003() was not found in any shared library.
The error reported was: dlsym(RTLD_NEXT, connect$NOCANCEL$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol select$UNIX2003() was not found in any shared library. The error
reported was: dlsym(RTLD_NEXT, select$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol select$NOCANCEL$UNIX2003() was not found in any shared library.
The error reported was: dlsym(RTLD_NEXT, select$NOCANCEL$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol poll$UNIX2003() was not found in any shared library. The error
reported was: dlsym(RTLD_NEXT, poll$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol poll$NOCANCEL$UNIX2003() was not found in any shared library.
The error reported was: dlsym(RTLD_NEXT, poll$NOCANCEL$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol close$UNIX2003() was not found in any shared library. The error
reported was: dlsym(RTLD_NEXT, close$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol close$NOCANCEL$UNIX2003() was not found in any shared library.
The error reported was: dlsym(RTLD_NEXT, close$NOCANCEL$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol getpeername$UNIX2003() was not found in any shared library. The
error reported was: dlsym(RTLD_NEXT, getpeername$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol sendto$UNIX2003() was not found in any shared library. The error
reported was: dlsym(RTLD_NEXT, sendto$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol sendto$NOCANCEL$UNIX2003() was not found in any shared library.
The error reported was: dlsym(RTLD_NEXT, sendto$NOCANCEL$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol sendmsg$UNIX2003() was not found in any shared library. The error
reported was: dlsym(RTLD_NEXT, sendmsg$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol sendmsg$NOCANCEL$UNIX2003() was not found in any shared
library. The error reported was: dlsym(RTLD_NEXT, sendmsg$NOCANCEL$UNIX2003): symbol not found!
I hope we can work together to get this worked out. Also, i would be happy to help write any documentation
you may need for Mac OS X.
David
yeah i found that file already. tsocks is the same way for obvious reasons. also, for future documentation it
seems the conf file is in /usr/local/etc/torsocks.conf by default on OS X. However even with
server = 127.0.0.1
server_port = 1080
tordns_enable = false (i found this line to be necessary when using tsocks before)
it cant seem to get anything to go through the proxy. I am using "ssh -D 1080 user@domain.org" as my
proxy btw. I may have misspoken before when i said it seemed to work after spitting out debug info. That was
just an initial impression. I think that at that point i had not added the disable tordns line in the config file
and so i got a "could not resolve hostname" line giving the impression that it might be working. Upon further
testing however, it seems that it freezes after the debug lines and does not send any information through the
proxy.
Here is a sample of the "debug" lines mentioned above:
torsocks ssh user@domain.org
21:43:20 libtorsocks(1391): The symbol connect$UNIX2003() was not found in any shared library. The error
reported was: dlsym(RTLD_NEXT, connect$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol connect$NOCANCEL$UNIX2003() was not found in any shared library.
The error reported was: dlsym(RTLD_NEXT, connect$NOCANCEL$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol select$UNIX2003() was not found in any shared library. The error
reported was: dlsym(RTLD_NEXT, select$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol select$NOCANCEL$UNIX2003() was not found in any shared library.
The error reported was: dlsym(RTLD_NEXT, select$NOCANCEL$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol poll$UNIX2003() was not found in any shared library. The error
reported was: dlsym(RTLD_NEXT, poll$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol poll$NOCANCEL$UNIX2003() was not found in any shared library.
The error reported was: dlsym(RTLD_NEXT, poll$NOCANCEL$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol close$UNIX2003() was not found in any shared library. The error
reported was: dlsym(RTLD_NEXT, close$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol close$NOCANCEL$UNIX2003() was not found in any shared library.
The error reported was: dlsym(RTLD_NEXT, close$NOCANCEL$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol getpeername$UNIX2003() was not found in any shared library. The
error reported was: dlsym(RTLD_NEXT, getpeername$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol sendto$UNIX2003() was not found in any shared library. The error
reported was: dlsym(RTLD_NEXT, sendto$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol sendto$NOCANCEL$UNIX2003() was not found in any shared library.
The error reported was: dlsym(RTLD_NEXT, sendto$NOCANCEL$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol sendmsg$UNIX2003() was not found in any shared library. The error
reported was: dlsym(RTLD_NEXT, sendmsg$UNIX2003): symbol not found!
21:43:20 libtorsocks(1391): The symbol sendmsg$NOCANCEL$UNIX2003() was not found in any shared
library. The error reported was: dlsym(RTLD_NEXT, sendmsg$NOCANCEL$UNIX2003): symbol not found!
I hope we can work together to get this worked out. Also, i would be happy to help write any documentation
you may need for Mac OS X.
David
Sep 21, 2009
issue 2
(compile problems on mac os x 10.5) commented on by rob...@roberthogan.net
- torsocks will use the proxy defined in /usr/etc/torsocks.conf, or more properly
$CONFDIR/torsocks.conf, depending on what CONFDIR is at compile time. You can also
do 'export TSOCKS_CONF_FILE= /location/of/torsocks.conf' and then run torsocks,
which will pick up the configuration in that file.
By default torsocks will try to proxy through 127.0.0.1:9050 if nothing else is
defined, so if you change the server and server_port entries in torsocks.conf to
what you want, that should get it working for you.
This needs to be better documented of course.
torsocks will use the proxy defined in /usr/etc/torsocks.conf, or more properly
$CONFDIR/torsocks.conf, depending on what CONFDIR is at compile time. You can also
do 'export TSOCKS_CONF_FILE= /location/of/torsocks.conf' and then run torsocks,
which will pick up the configuration in that file.
By default torsocks will try to proxy through 127.0.0.1:9050 if nothing else is
defined, so if you change the server and server_port entries in torsocks.conf to
what you want, that should get it working for you.
This needs to be better documented of course.
Sep 21, 2009
issue 2
(compile problems on mac os x 10.5) commented on by dlwim...@newcommunities.net
- I am running a 64-bit capable processor, however snow leopard by default boots into a 32-bit kernel
regardless... Applications that support 64-bit however can still run in 64-bit mode (Finder, Terminal, any 3rd
party apps that have 64-bit support, etc). Also on further testing it seems that torsocks (and tsocks) only give
me that error when i try to use it on a gui app (World of Warcraft for example). If i do "torsocks ssh..." it spits out
a bunch of stuff and then seems to work.. i haven't however been able to actually make it proxy ssh.
I am running a 64-bit capable processor, however snow leopard by default boots into a 32-bit kernel
regardless... Applications that support 64-bit however can still run in 64-bit mode (Finder, Terminal, any 3rd
party apps that have 64-bit support, etc). Also on further testing it seems that torsocks (and tsocks) only give
me that error when i try to use it on a gui app (World of Warcraft for example). If i do "torsocks ssh..." it spits out
a bunch of stuff and then seems to work.. i haven't however been able to actually make it proxy ssh.
Sep 20, 2009
issue 2
(compile problems on mac os x 10.5) commented on by rob...@roberthogan.net
- it looks like this problem has also been encountered with sshfs in macfusion in snow
leopard. unfortunately, the only fix showing up in google at the moment is to remove
the library. i have no doubt that 10.6 has introduced something new that torsocks is
missing, but will have to wait for the internets to enlighten me.
btw, are you 32-bit or 64-bit?
it looks like this problem has also been encountered with sshfs in macfusion in snow
leopard. unfortunately, the only fix showing up in google at the moment is to remove
the library. i have no doubt that 10.6 has introduced something new that torsocks is
missing, but will have to wait for the internets to enlighten me.
btw, are you 32-bit or 64-bit?
Sep 19, 2009
issue 2
(compile problems on mac os x 10.5) commented on by dlwim...@newcommunities.net
- thanks for the quick response..
that seems to have fixed it (still using the autoreconf -fiv line)
however now i need some help in actual use...
using tsocks before i would just call "tsocks 'application/path' &'
doing that with torsocks gives me the same error that tsocks was giving me after i upgraded to 10.6
(different path of course though):
dyld: could not load inserted library: /usr/local/lib/torsocks/libtorsocks.dylib
thanks again for your help,
David
thanks for the quick response..
that seems to have fixed it (still using the autoreconf -fiv line)
however now i need some help in actual use...
using tsocks before i would just call "tsocks 'application/path' &'
doing that with torsocks gives me the same error that tsocks was giving me after i upgraded to 10.6
(different path of course though):
dyld: could not load inserted library: /usr/local/lib/torsocks/libtorsocks.dylib
thanks again for your help,
David
issue 2
(compile problems on mac os x 10.5) commented on by dlwim...@newcommunities.net
- Hi,
I've been using tsocks from macports for the last few years but the recent update to Snow Leopard (10.6)
seems to have broken it. (I upgraded macports and reinstalled tsocks and now I get a: dyld: could not load
inserted library: /opt/local/lib/libtsocks.dylib message) Because of this i am looking for a new utility to send
connections through an ssh/socks proxy. I tried to build torsocks on my computer running 10.6 using the
following commands in terminal:
git clone git://git.torproject.org/git/torsocks
cd torsocks
git pull origin osx
make -f Makefile.cvs
./configure
make
This make fails. (Incorrect libtool version)
autoreconf -fiv
make
This make fails with:
make all-recursive
Making all in src
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -Wall -MT tsocks.lo
-MD -MP -MF .deps/tsocks.Tpo -c -o tsocks.lo tsocks.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -Wall -MT tsocks.lo -MD -MP -MF .deps/tsocks.Tpo
-c tsocks.c -fno-common -DPIC -o .libs/tsocks.o
In file included from /usr/include/sys/types.h:75,
from /usr/include/sys/socket.h:75,
from tsocks.c:57:
/usr/include/sys/cdefs.h:289:8: error: #error "Can't define _NONSTD_SOURCE when only UNIX conformance is
available."
make[2]: *** [tsocks.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
any ideas?
thanks,
David
Hi,
I've been using tsocks from macports for the last few years but the recent update to Snow Leopard (10.6)
seems to have broken it. (I upgraded macports and reinstalled tsocks and now I get a: dyld: could not load
inserted library: /opt/local/lib/libtsocks.dylib message) Because of this i am looking for a new utility to send
connections through an ssh/socks proxy. I tried to build torsocks on my computer running 10.6 using the
following commands in terminal:
git clone git://git.torproject.org/git/torsocks
cd torsocks
git pull origin osx
make -f Makefile.cvs
./configure
make
This make fails. (Incorrect libtool version)
autoreconf -fiv
make
This make fails with:
make all-recursive
Making all in src
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -Wall -MT tsocks.lo
-MD -MP -MF .deps/tsocks.Tpo -c -o tsocks.lo tsocks.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -Wall -MT tsocks.lo -MD -MP -MF .deps/tsocks.Tpo
-c tsocks.c -fno-common -DPIC -o .libs/tsocks.o
In file included from /usr/include/sys/types.h:75,
from /usr/include/sys/socket.h:75,
from tsocks.c:57:
/usr/include/sys/cdefs.h:289:8: error: #error "Can't define _NONSTD_SOURCE when only UNIX conformance is
available."
make[2]: *** [tsocks.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
any ideas?
thanks,
David
Aug 27, 2009
Source (Building Torsocks from source) Wiki page commented on by jd.mubix
- If your 'make' fails, first make sure you have Automake and libtool. If you are still having issues, run 'autoreconf -fiv'. After that 'make' should work flawlessly.
If your 'make' fails, first make sure you have Automake and libtool. If you are still having issues, run 'autoreconf -fiv'. After that 'make' should work flawlessly.
Aug 20, 2009
issue 2
(compile problems on mac os x 10.5) commented on by rob...@roberthogan.net
- Hey Gregory,
Could you give it a whirl to see if it works?
git clone git://git.torproject.org/git/torsocks
git pull origin osx
Thanks,
Robert
Hey Gregory,
Could you give it a whirl to see if it works?
git clone git://git.torproject.org/git/torsocks
git pull origin osx
Thanks,
Robert
Aug 20, 2009
issue 2
(compile problems on mac os x 10.5) commented on by gregory.dudek
- Regarding the (perhaps obsolete) comment that torocks may not be compatible with OSX, I want to state
unequivocally that I got it running happily on OSX Leopard back when I made comment #3 (May 2009). It can
work, it does work, maybe in needs some handholding to compile (but perhaps it has been resolved by now).
Naturally the kernel extension (comment #11) is a great idea that might be a nicer long-term fix, but either way,
it's usable if you sweat it enough.
Regarding the (perhaps obsolete) comment that torocks may not be compatible with OSX, I want to state
unequivocally that I got it running happily on OSX Leopard back when I made comment #3 (May 2009). It can
work, it does work, maybe in needs some handholding to compile (but perhaps it has been resolved by now).
Naturally the kernel extension (comment #11) is a great idea that might be a nicer long-term fix, but either way,
it's usable if you sweat it enough.
Aug 18, 2009
issue 8
(error segmentation) commented on by starslig...@breakthru.com
- here are a few infos made by my system to report to Launchpad
Private bug reported:
Binary package hint: pidgin
It do that only if i start pidgin with "torsocks" and will send a
message
Intel x86 64 karmic 9.10 beta4 and jaunty 9.04 ( ubuntu )
pidgin 1:2.5.8
ProblemType: Crash
Architecture: amd64
Date: Tue Aug 18 02:11:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.5.8-1ubuntu2
ProcCmdline: pidgin
ProcEnviron:
LANGUAGE=
LANG=fr_CH.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
SegvAnalysis:
Segfault happened at: 0x7ff589e81a92 <sendmsg+130>: movzwl (%rbx),%edx
PC (0x7ff589e81a92) ok
source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
sendmsg (s=24, msg=0x7ff566f88d60, flags=16384) at tsocks.c:1739
pa_iochannel_write_with_creds ()
?? () from /usr/lib/libpulsecommon-0.9.16.so
pa_mainloop_dispatch () from /usr/lib/libpulse.so.0
pa_mainloop_iterate () from /usr/lib/libpulse.so.0
Title: pidgin crashed with SIGSEGV in sendmsg()
Uname: Linux 2.6.31-6-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
** Affects: pidgin (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-crash need-amd64-retrace
--
pidgin crashed with SIGSEGV in sendmsg()
https://bugs.launchpad.net/bugs/415143
You received this bug notification because you are a direct subscriber
of the bug.
Status in “pidgin” package in Ubuntu: New
Bug description:
Binary package hint: pidgin
It do that only if i start pidgin with "torsocks" and will send a message
Intel x86 64 karmic 9.10 beta4 and jaunty 9.04 ( ubuntu )
pidgin 1:2.5.8
ProblemType: Crash
Architecture: amd64
Date: Tue Aug 18 02:11:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.5.8-1ubuntu2
ProcCmdline: pidgin
ProcEnviron:
LANGUAGE=
LANG=fr_CH.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
SegvAnalysis:
Segfault happened at: 0x7ff589e81a92 <sendmsg+130>: movzwl (%rbx),%edx
PC (0x7ff589e81a92) ok
source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
sendmsg (s=24, msg=0x7ff566f88d60, flags=16384) at tsocks.c:1739
pa_iochannel_write_with_creds ()
?? () from /usr/lib/libpulsecommon-0.9.16.so
pa_mainloop_dispatch () from /usr/lib/libpulse.so.0
pa_mainloop_iterate () from /usr/lib/libpulse.so.0
Title: pidgin crashed with SIGSEGV in sendmsg()
Uname: Linux 2.6.31-6-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/30437097/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/30437098/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/30437099/Disassembly.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/30437100/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/30437101/ProcStatus.txt
** Attachment added: "Registers.txt"
http://launchpadlibrarian.net/30437102/Registers.txt
** Attachment added: "Stacktrace.txt"
http://launchpadlibrarian.net/30437103/Stacktrace.txt
** Attachment added: "ThreadStacktrace.txt"
http://launchpadlibrarian.net/30437104/ThreadStacktrace.txt
here are a few infos made by my system to report to Launchpad
Private bug reported:
Binary package hint: pidgin
It do that only if i start pidgin with "torsocks" and will send a
message
Intel x86 64 karmic 9.10 beta4 and jaunty 9.04 ( ubuntu )
pidgin 1:2.5.8
ProblemType: Crash
Architecture: amd64
Date: Tue Aug 18 02:11:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.5.8-1ubuntu2
ProcCmdline: pidgin
ProcEnviron:
LANGUAGE=
LANG=fr_CH.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
SegvAnalysis:
Segfault happened at: 0x7ff589e81a92 <sendmsg+130>: movzwl (%rbx),%edx
PC (0x7ff589e81a92) ok
source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
sendmsg (s=24, msg=0x7ff566f88d60, flags=16384) at tsocks.c:1739
pa_iochannel_write_with_creds ()
?? () from /usr/lib/libpulsecommon-0.9.16.so
pa_mainloop_dispatch () from /usr/lib/libpulse.so.0
pa_mainloop_iterate () from /usr/lib/libpulse.so.0
Title: pidgin crashed with SIGSEGV in sendmsg()
Uname: Linux 2.6.31-6-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
** Affects: pidgin (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-crash need-amd64-retrace
--
pidgin crashed with SIGSEGV in sendmsg()
https://bugs.launchpad.net/bugs/415143
You received this bug notification because you are a direct subscriber
of the bug.
Status in “pidgin” package in Ubuntu: New
Bug description:
Binary package hint: pidgin
It do that only if i start pidgin with "torsocks" and will send a message
Intel x86 64 karmic 9.10 beta4 and jaunty 9.04 ( ubuntu )
pidgin 1:2.5.8
ProblemType: Crash
Architecture: amd64
Date: Tue Aug 18 02:11:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.5.8-1ubuntu2
ProcCmdline: pidgin
ProcEnviron:
LANGUAGE=
LANG=fr_CH.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic
SegvAnalysis:
Segfault happened at: 0x7ff589e81a92 <sendmsg+130>: movzwl (%rbx),%edx
PC (0x7ff589e81a92) ok
source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
sendmsg (s=24, msg=0x7ff566f88d60, flags=16384) at tsocks.c:1739
pa_iochannel_write_with_creds ()
?? () from /usr/lib/libpulsecommon-0.9.16.so
pa_mainloop_dispatch () from /usr/lib/libpulse.so.0
pa_mainloop_iterate () from /usr/lib/libpulse.so.0
Title: pidgin crashed with SIGSEGV in sendmsg()
Uname: Linux 2.6.31-6-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/30437097/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/30437098/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/30437099/Disassembly.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/30437100/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/30437101/ProcStatus.txt
** Attachment added: "Registers.txt"
http://launchpadlibrarian.net/30437102/Registers.txt
** Attachment added: "Stacktrace.txt"
http://launchpadlibrarian.net/30437103/Stacktrace.txt
** Attachment added: "ThreadStacktrace.txt"
http://launchpadlibrarian.net/30437104/ThreadStacktrace.txt
Aug 15, 2009
issue 2
(compile problems on mac os x 10.5) commented on by rob...@roberthogan.net
- Hi Alex,
I've committed your patch to a branch in git called osx. Can you verify it works as expected?
git clone git://git.torproject.org/git/torsocks
git pull origin osx
Any comments/feedback appreciated. You might also look over the commit logs to ensure
I've understood all the elements in your patch correctly.
Thanks!
Robert
Hi Alex,
I've committed your patch to a branch in git called osx. Can you verify it works as expected?
git clone git://git.torproject.org/git/torsocks
git pull origin osx
Any comments/feedback appreciated. You might also look over the commit logs to ensure
I've understood all the elements in your patch correctly.
Thanks!
Robert
Aug 13, 2009
issue 2
(compile problems on mac os x 10.5) commented on by al...@ohmantics.com
- torsocks is as compatible with OS X as it is with any other OS. It's design is fundamentally flawed and leakage will
continue to be a problem until it's pushed down into the kernel.
The patch I supplied fixes the problem shaolinint has.
You can test for OS X in configure scripts by checking that "uname -s" returns "Darwin" or check for __APPLE__ in
the preprocessor.
torsocks is as compatible with OS X as it is with any other OS. It's design is fundamentally flawed and leakage will
continue to be a problem until it's pushed down into the kernel.
The patch I supplied fixes the problem shaolinint has.
You can test for OS X in configure scripts by checking that "uname -s" returns "Darwin" or check for __APPLE__ in
the preprocessor.
Aug 07, 2009
issue 9
(crash when i open a program who open some connections) reported by starslig...@breakthru.com
- What steps will reproduce the problem?
1. xchat for linux
2. config a few servers
3. torsocks xchat and open more than one servers
What is the expected output? What do you see instead?
Nothing appare , when open one server,i.e;: OFTC, all are ok, if i open
another one, torsocks crash and close xchat too.
If it use only one server, it never close or make problem
What version of the product are you using? On what operating system?
the last version: delta 1 from git on kubuntu jaunty 9.04 x86 64
Please provide any additional information below.
What steps will reproduce the problem?
1. xchat for linux
2. config a few servers
3. torsocks xchat and open more than one servers
What is the expected output? What do you see instead?
Nothing appare , when open one server,i.e;: OFTC, all are ok, if i open
another one, torsocks crash and close xchat too.
If it use only one server, it never close or make problem
What version of the product are you using? On what operating system?
the last version: delta 1 from git on kubuntu jaunty 9.04 x86 64
Please provide any additional information below.
Aug 06, 2009
issue 8
(error segmentation) reported by starslig...@breakthru.com
- What steps will reproduce the problem?
1. start pidgin on linux jaunty 64 with torsocks
2. send pm
3.
What is the expected output? What do you see instead?
desktop2:~$ torsocks pidgin
00:05:23 libtorsocks(32276): sendto: Connection is a UDP or ICMP stream,
may be a DNS request or other form of leak:rejecting.
00:05:23 libtorsocks(32276): sendto: Connection is a UDP or ICMP stream,
may be a DNS request or other form of leak:rejecting.
Erreur de segmentation
What version of the product are you using? On what operating system?
last git 1.0 delta , kubuntu jaunty 9.0.4 x86 64
Please provide any additional information below.
The error don't come everytime ...
Kopete leaks DNS so i think need to be change in "Tor" wiki
What steps will reproduce the problem?
1. start pidgin on linux jaunty 64 with torsocks
2. send pm
3.
What is the expected output? What do you see instead?
desktop2:~$ torsocks pidgin
00:05:23 libtorsocks(32276): sendto: Connection is a UDP or ICMP stream,
may be a DNS request or other form of leak:rejecting.
00:05:23 libtorsocks(32276): sendto: Connection is a UDP or ICMP stream,
may be a DNS request or other form of leak:rejecting.
Erreur de segmentation
What version of the product are you using? On what operating system?
last git 1.0 delta , kubuntu jaunty 9.0.4 x86 64
Please provide any additional information below.
The error don't come everytime ...
Kopete leaks DNS so i think need to be change in "Tor" wiki
Aug 02, 2009
issue 2
(compile problems on mac os x 10.5) commented on by rob...@roberthogan.net
- i genuinely believe that torsocks is not compatible with OSX. In the absence of anyone willing
to supply patches and an OSX system of my own to build and test on it will probably stay
that way.
Could you supply an strace of your activity? This might help me document the changes that I
think are required. Though I will be relying on someone with an OSX platform to assist with
coding/testing in the future.
i genuinely believe that torsocks is not compatible with OSX. In the absence of anyone willing
to supply patches and an OSX system of my own to build and test on it will probably stay
that way.
Could you supply an strace of your activity? This might help me document the changes that I
think are required. Though I will be relying on someone with an OSX platform to assist with
coding/testing in the future.
Aug 01, 2009
issue 2
(compile problems on mac os x 10.5) commented on by shaolinint
- hey man,
I compile torsocks successfully on my Mac OS X 10.5.
However, when I executed 'torsocks lynx http://whatismyipaddress.com' to check my ip
address, it shows my original ip.
here's my torsocks configuration:
local = 127.0.0.0/255.128.0.0
local = 127.128.0.0/255.192.0.0
local = 169.254.0.0/255.255.0.0
local = 172.16.0.0/255.240.0.0
local = 192.168.0.0/255.255.0.0
server = 127.0.0.1
thanks.
shaolinint
hey man,
I compile torsocks successfully on my Mac OS X 10.5.
However, when I executed 'torsocks lynx http://whatismyipaddress.com' to check my ip
address, it shows my original ip.
here's my torsocks configuration:
local = 127.0.0.0/255.128.0.0
local = 127.128.0.0/255.192.0.0
local = 169.254.0.0/255.255.0.0
local = 172.16.0.0/255.240.0.0
local = 192.168.0.0/255.255.0.0
server = 127.0.0.1
thanks.
shaolinint
Jul 20, 2009
issue 6
(Unable to build torsocks) commented on by starslig...@breakthru.com
- i have the same problem with ubuntu jaunty 9.04 64 bits but with 'autoreconf -fiv',
the build have passed and done .
i have the same problem with ubuntu jaunty 9.04 64 bits but with 'autoreconf -fiv',
the build have passed and done .
Jul 17, 2009
issue 2
(compile problems on mac os x 10.5) commented on by rob...@roberthogan.net
- Alternatively, you could provide some guidance on how to identify MAC OSX during
compilation and I can do the necessary. In the absence of an OSX platform to build on I am
not in a good position to clean this up and commit for testing.
Alternatively, you could provide some guidance on how to identify MAC OSX during
compilation and I can do the necessary. In the absence of an OSX platform to build on I am
not in a good position to clean this up and commit for testing.
Jul 17, 2009
issue 2
(compile problems on mac os x 10.5) commented on by rob...@roberthogan.net
- This patch s hugely appreciated and I would like to apply it. Could you #ifdef your changes for
the mac osx platform? As it stands the patch will break compilation on linux platforms.
This patch s hugely appreciated and I would like to apply it. Could you #ifdef your changes for
the mac osx platform? As it stands the patch will break compilation on linux platforms.
Jul 15, 2009
issue 2
(compile problems on mac os x 10.5) commented on by al...@ohmantics.com
- While you might be on the path toward compilation, Mac OS X 10.5 Leopard introduces new symbols that need
to be patched to prevent leakage (e.g. "connect$UNIX2003" instead of "connect"). Long term. this entire path of
using DYLD_INSERT_LIBRARIES is untenable; a much better solution would be a kernel extension.
Perhaps somebody who enjoys a hot autoconf poker in the eye can clean the attached patch up some.
While you might be on the path toward compilation, Mac OS X 10.5 Leopard introduces new symbols that need
to be patched to prevent leakage (e.g. "connect$UNIX2003" instead of "connect"). Long term. this entire path of
using DYLD_INSERT_LIBRARIES is untenable; a much better solution would be a kernel extension.
Perhaps somebody who enjoys a hot autoconf poker in the eye can clean the attached patch up some.
Jul 15, 2009
issue 2
(compile problems on mac os x 10.5) commented on by rob...@roberthogan.net
- Ah, think I've put that MAP_ANON fix in the wrong place.
Can you try adding the lines below at the end of common.h:
/* Required by some BSDs */
#ifndef MAP_ANONYMOUS
#ifdef MAP_ANON
#define MAP_ANONYMOUS MAP_ANON
#endif
#endif
Ah, think I've put that MAP_ANON fix in the wrong place.
Can you try adding the lines below at the end of common.h:
/* Required by some BSDs */
#ifndef MAP_ANONYMOUS
#ifdef MAP_ANON
#define MAP_ANONYMOUS MAP_ANON
#endif
#endif
Jul 14, 2009
issue 2
(compile problems on mac os x 10.5) commented on by mr.kamu
- (just to clarify, I have git pull'ed the lastest revision.)
(just to clarify, I have git pull'ed the lastest revision.)
Jul 14, 2009
issue 2
(compile problems on mac os x 10.5) commented on by mr.kamu
- Hi rob,
autoreconf worked, thanks, but the MAP_ANON problem still exists:
dead_pool.c: In function ‘init_pool’:
dead_pool.c:103: error: ‘MAP_ANONYMOUS’ undeclared (first use in this function)
dead_pool.c:103: error: (Each undeclared identifier is reported only once
dead_pool.c:103: error: for each function it appears in.)
make[2]: *** [dead_pool.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Hi rob,
autoreconf worked, thanks, but the MAP_ANON problem still exists:
dead_pool.c: In function ‘init_pool’:
dead_pool.c:103: error: ‘MAP_ANONYMOUS’ undeclared (first use in this function)
dead_pool.c:103: error: (Each undeclared identifier is reported only once
dead_pool.c:103: error: for each function it appears in.)
make[2]: *** [dead_pool.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Jul 09, 2009
issue 7
(Package for debian) commented on by rob...@roberthogan.net
- no, i have no plans to create a package - so please do so, that would be great.
no, i have no plans to create a package - so please do so, that would be great.
Jul 09, 2009
issue 6
(Unable to build torsocks) commented on by vympel1
- Thanks for your time to find solution to my problem, but i had no luck this time. Did
as it said there: found folders 'aclocal' and 'aclocal-1.10' under /usr/share, merged
all into 'aclocal-1.10', deleted 'aclocal', created symlink 'aclocal' for
'aclocal-1.10'; found folder 'automake-1.10' under /usr/share, created symlink
'automake' for it.
Terminal output is same :(
Thanks for your time to find solution to my problem, but i had no luck this time. Did
as it said there: found folders 'aclocal' and 'aclocal-1.10' under /usr/share, merged
all into 'aclocal-1.10', deleted 'aclocal', created symlink 'aclocal' for
'aclocal-1.10'; found folder 'automake-1.10' under /usr/share, created symlink
'automake' for it.
Terminal output is same :(
issue 6
(Unable to build torsocks) commented on by vympel1
- I receive an error during compiling. Here is a process (on Ubuntu 8.10 i386):
cd '/usr/local/src' ## <-- user has all permissions for this folder
git clone git://git.torproject.org/git/torsocks
cd torsocks
make -f Makefile.cvs
Here is an output:
aclocal
autoheader
automake
src/Makefile.am:39: Libtool library used but `LIBTOOL' is undefined
src/Makefile.am:39: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/Makefile.am:39: to `configure.in' and run `aclocal' and `autoconf' again.
src/Makefile.am:39: If `AC_PROG_LIBTOOL' is in `configure.in', make sure
src/Makefile.am:39: its definition is in aclocal's search path.
make: *** [all] Error 1
How to fix this?
I receive an error during compiling. Here is a process (on Ubuntu 8.10 i386):
cd '/usr/local/src' ## <-- user has all permissions for this folder
git clone git://git.torproject.org/git/torsocks
cd torsocks
make -f Makefile.cvs
Here is an output:
aclocal
autoheader
automake
src/Makefile.am:39: Libtool library used but `LIBTOOL' is undefined
src/Makefile.am:39: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/Makefile.am:39: to `configure.in' and run `aclocal' and `autoconf' again.
src/Makefile.am:39: If `AC_PROG_LIBTOOL' is in `configure.in', make sure
src/Makefile.am:39: its definition is in aclocal's search path.
make: *** [all] Error 1
How to fix this?
Jul 08, 2009
issue 7
(Package for debian) reported by ioerror
- I'd like to package torsocks for debian. Do you mind if I ITP it and make a
debian package? Or do you have plans to create a Debian package?
I'd like to package torsocks for debian. Do you mind if I ITP it and make a
debian package? Or do you have plans to create a Debian package?
Jun 29, 2009
issue 2
(compile problems on mac os x 10.5) commented on by rob...@roberthogan.net
- i think you need to do: autoreconf -fiv
i think you need to do: autoreconf -fiv
Jun 28, 2009
issue 2
(compile problems on mac os x 10.5) commented on by vike2000
- trying to build this in macports it seems to me ive come a little further
Error: Target org.macports.build returned: shell command " cd
"/opt/local/var/macports/build/_Users_vike_data_macports_ports_net_torsocks/work/torsocks-1.0-gamma"
&& make all " returned error 2
Command output: checking if the linker accepts -multiply_defined suppress... yes
checking if the linker accepts -single_module... yes
configure: creating ./config.status
/bin/sh ./config.status
config.status: creating src/usewithtor
config.status: creating src/torsocks
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
cd . && /bin/sh
/opt/local/var/macports/build/_Users_vike_data_macports_ports_net_torsocks/work/torsocks-1.0-
gamma/missing --run autoheader
rm -f stamp-h1
touch config.h.in
cd . && /bin/sh ./config.status config.h
config.status: creating config.h
make all-recursive
Making all in src
/bin/sh ../libtool --tag=CC --mode=compile /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I.. -
I/opt/local/include -O2 -Wall -MT tsocks.lo -MD -MP -MF .deps/tsocks.Tpo -c -o tsocks.lo tsocks.c
../libtool: line 818: X--tag=CC: command not found
../libtool: line 851: libtool: ignoring unknown tag : command not found
../libtool: line 818: X--mode=compile: command not found
../libtool: line 985: *** Warning: inferring the mode of operation is deprecated.: command not found
../libtool: line 986: *** Future versions of Libtool will require --mode=MODE be specified.: command not
found
../libtool: line 1016: libtool: warning: cannot infer operation mode from `/usr/bin/gcc-4.0': No such file or
directory
../libtool: line 7079: libtool: you must specify a MODE: command not found
../libtool: line 7080: Try `libtool --help' for more information.: command not found
make[2]: *** [tsocks.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
attaching my local portfile-repository's port's files - with patches based on the
[http://trac.macports.org/browser/trunk/dports/net/tsocks tsocks port]
building manually according to the [http://code.google.com/p/torsocks/wiki/Source?tm=4 instructions]
produces the exact same errors as mr.kamu's last post
but, while writing posts and cross-checking i've gotten tsocks working for my needs. but good luck, ill check
back.
(i made a "[http://trac.macports.org/ticket/15629#comment:4 crosspost]" at macports)
trying to build this in macports it seems to me ive come a little further
Error: Target org.macports.build returned: shell command " cd
"/opt/local/var/macports/build/_Users_vike_data_macports_ports_net_torsocks/work/torsocks-1.0-gamma"
&& make all " returned error 2
Command output: checking if the linker accepts -multiply_defined suppress... yes
checking if the linker accepts -single_module... yes
configure: creating ./config.status
/bin/sh ./config.status
config.status: creating src/usewithtor
config.status: creating src/torsocks
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
cd . && /bin/sh
/opt/local/var/macports/build/_Users_vike_data_macports_ports_net_torsocks/work/torsocks-1.0-
gamma/missing --run autoheader
rm -f stamp-h1
touch config.h.in
cd . && /bin/sh ./config.status config.h
config.status: creating config.h
make all-recursive
Making all in src
/bin/sh ../libtool --tag=CC --mode=compile /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I.. -
I/opt/local/include -O2 -Wall -MT tsocks.lo -MD -MP -MF .deps/tsocks.Tpo -c -o tsocks.lo tsocks.c
../libtool: line 818: X--tag=CC: command not found
../libtool: line 851: libtool: ignoring unknown tag : command not found
../libtool: line 818: X--mode=compile: command not found
../libtool: line 985: *** Warning: inferring the mode of operation is deprecated.: command not found
../libtool: line 986: *** Future versions of Libtool will require --mode=MODE be specified.: command not
found
../libtool: line 1016: libtool: warning: cannot infer operation mode from `/usr/bin/gcc-4.0': No such file or
directory
../libtool: line 7079: libtool: you must specify a MODE: command not found
../libtool: line 7080: Try `libtool --help' for more information.: command not found
make[2]: *** [tsocks.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
attaching my local portfile-repository's port's files - with patches based on the
[http://trac.macports.org/browser/trunk/dports/net/tsocks tsocks port]
building manually according to the [http://code.google.com/p/torsocks/wiki/Source?tm=4 instructions]
produces the exact same errors as mr.kamu's last post
but, while writing posts and cross-checking i've gotten tsocks working for my needs. but good luck, ill check
back.
(i made a "[http://trac.macports.org/ticket/15629#comment:4 crosspost]" at macports)
issue 6
(Unable to build torsocks) reported by neoeinstein
- *What steps will reproduce the problem?*
1. get the git master
2. attempt to build
*What is the expected output? What do you see instead?*
A completed build. Instead getting libtool errors.
*What version of the product are you using? On what operating system?*
The git master (505fbcbb) on Ubuntu Jaunty.
Please provide any additional information below.
Full output of my build attempt:
{{{
:~/src/tor/torsocks$ git fetch -v
From git://git.torproject.org/git/torsocks
= [up to date] master -> origin/master
:~/src/tor/torsocks$ git rev-parse master
505fbcbb44ab053be749af2347e9f0fb4c312ab8
:~/src/tor/torsocks$ git clean -dfx
Removing Makefile
Removing Makefile.in
Removing autom4te.cache/
Removing config.h
Removing config.h.in
Removing config.log
Removing config.status
Removing configure
Removing libtool
Removing src/.deps/
Removing src/Makefile
Removing src/Makefile.in
Removing src/torsocks
Removing src/usewithtor
Removing stamp-h1
:~/src/tor/torsocks$ make -f Makefile.cvs
aclocal
autoheader
automake
autoconf
:~/src/tor/torsocks$ ./configure --prefix=/usr/local
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking if the C compiler accepts -Wall... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking sys/poll.h usability... yes
checking sys/poll.h presence... yes
checking for sys/poll.h... yes
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking for unistd.h... (cached) yes
checking for strcspn... yes
checking for strdup... yes
checking for strerror... yes
checking for strspn... yes
checking for strtol... yes
checking for mmap... yes
checking for strcasecmp... yes
checking for strncasecmp... yes
checking for strtol... (cached) yes
checking for connect in -l"c"... yes
checking for socket... yes
checking for inet_aton... yes
checking for gethostbyname... yes
checking for dlsym in -ldl... yes
checking for res_query in -lresolv... no
checking for RTLD_NEXT from dlfcn.h... no
checking for RTLD_NEXT from dlfcn.h with _GNU_SOURCE... yes
checking whether to enable tordns... yes
checking for correct select prototype... select(int n, fd_set *readfds,
fd_set *writefds, fd_set *exceptfds, struct timeval *timeout)
checking for correct connect prototype... connect(int __fd, const struct
sockaddr * __addr, socklen_t __len)
checking for correct close prototype... close(int fd)
checking for correct res_querydomain prototype... res_querydomain(const
char *name, const char *domain, int class, int type, unsigned char *answer,
int anslen)
checking for correct res_send prototype... res_send(const unsigned char
*msg, int msglen, unsigned char *answer, int anslen)
checking for correct res_search prototype... res_search(const char *dname,
int class, int type,unsigned char *answer, int anslen)
checking for correct res_query prototype... res_query(const char *dname,
int class, int type,unsigned char *answer, int anslen)
checking for correct getpeername prototype... getpeername(int __fd, struct
sockaddr * __name, socklen_t *__namelen)
checking for correct poll prototype... poll(struct pollfd *ufds, unsigned
long nfds, int timeout)
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for dlfcn.h... (cached) yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating ./config.status
config.status: creating src/usewithtor
config.status: creating src/torsocks
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
:~/src/tor/torsocks$ make
make all-recursive
make[1]: Entering directory `/home/mgriep/src/tor/torsocks'
Making all in src
make[2]: Entering directory `/home/mgriep/src/tor/torsocks/src'
/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I..
-g -O2 -Wall -MT tsocks.lo -MD -MP -MF .deps/tsocks.Tpo -c -o tsocks.lo
tsocks.c
../libtool: line 821: X--tag=CC: command not found
../libtool: line 854: libtool: ignoring unknown tag : command not found
../libtool: line 821: X--mode=compile: command not found
../libtool: line 988: *** Warning: inferring the mode of operation is
deprecated.: command not found
../libtool: line 989: *** Future versions of Libtool will require
--mode=MODE be specified.: command not found
../libtool: line 1132: Xgcc: command not found
../libtool: line 1132: X-DHAVE_CONFIG_H: command not found
../libtool: line 1132: X-I.: command not found
../libtool: line 1132: X-I..: command not found
../libtool: line 1132: X-g: command not found
../libtool: line 1132: X-O2: command not found
../libtool: line 1132: X-Wall: command not found
../libtool: line 1132: X-MT: command not found
../libtool: line 1132: Xtsocks.lo: command not found
../libtool: line 1132: X-MD: command not found
../libtool: line 1132: X-MP: command not found
../libtool: line 1132: X-MF: command not found
../libtool: line 1132: X.deps/tsocks.Tpo: No such file or directory
../libtool: line 1132: X-c: command not found
../libtool: line 1184: Xtsocks.lo: command not found
../libtool: line 1189: libtool: compile: cannot determine name of library
object from `': command not found
make[2]: *** [tsocks.lo] Error 1
make[2]: Leaving directory `/home/mgriep/src/tor/torsocks/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/mgriep/src/tor/torsocks'
make: *** [all] Error 2
:~/src/tor/torsocks$ ./libtool --version
ltmain.sh (GNU libtool) 1.5.24 (1.1220.2.455 2007/06/24 02:13:29)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
:~/src/tor/torsocks$
}}}
*What steps will reproduce the problem?*
1. get the git master
2. attempt to build
*What is the expected output? What do you see instead?*
A completed build. Instead getting libtool errors.
*What version of the product are you using? On what operating system?*
The git master (505fbcbb) on Ubuntu Jaunty.
Please provide any additional information below.
Full output of my build attempt:
{{{
:~/src/tor/torsocks$ git fetch -v
From git://git.torproject.org/git/torsocks
= [up to date] master -> origin/master
:~/src/tor/torsocks$ git rev-parse master
505fbcbb44ab053be749af2347e9f0fb4c312ab8
:~/src/tor/torsocks$ git clean -dfx
Removing Makefile
Removing Makefile.in
Removing autom4te.cache/
Removing config.h
Removing config.h.in
Removing config.log
Removing config.status
Removing configure
Removing libtool
Removing src/.deps/
Removing src/Makefile
Removing src/Makefile.in
Removing src/torsocks
Removing src/usewithtor
Removing stamp-h1
:~/src/tor/torsocks$ make -f Makefile.cvs
aclocal
autoheader
automake
autoconf
:~/src/tor/torsocks$ ./configure --prefix=/usr/local
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking if the C compiler accepts -Wall... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking sys/poll.h usability... yes
checking sys/poll.h presence... yes
checking for sys/poll.h... yes
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking for unistd.h... (cached) yes
checking for strcspn... yes
checking for strdup... yes
checking for strerror... yes
checking for strspn... yes
checking for strtol... yes
checking for mmap... yes
checking for strcasecmp... yes
checking for strncasecmp... yes
checking for strtol... (cached) yes
checking for connect in -l"c"... yes
checking for socket... yes
checking for inet_aton... yes
checking for gethostbyname... yes
checking for dlsym in -ldl... yes
checking for res_query in -lresolv... no
checking for RTLD_NEXT from dlfcn.h... no
checking for RTLD_NEXT from dlfcn.h with _GNU_SOURCE... yes
checking whether to enable tordns... yes
checking for correct select prototype... select(int n, fd_set *readfds,
fd_set *writefds, fd_set *exceptfds, struct timeval *timeout)
checking for correct connect prototype... connect(int __fd, const struct
sockaddr * __addr, socklen_t __len)
checking for correct close prototype... close(int fd)
checking for correct res_querydomain prototype... res_querydomain(const
char *name, const char *domain, int class, int type, unsigned char *answer,
int anslen)
checking for correct res_send prototype... res_send(const unsigned char
*msg, int msglen, unsigned char *answer, int anslen)
checking for correct res_search prototype... res_search(const char *dname,
int class, int type,unsigned char *answer, int anslen)
checking for correct res_query prototype... res_query(const char *dname,
int class, int type,unsigned char *answer, int anslen)
checking for correct getpeername prototype... getpeername(int __fd, struct
sockaddr * __name, socklen_t *__namelen)
checking for correct poll prototype... poll(struct pollfd *ufds, unsigned
long nfds, int timeout)
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for dlfcn.h... (cached) yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating ./config.status
config.status: creating src/usewithtor
config.status: creating src/torsocks
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
:~/src/tor/torsocks$ make
make all-recursive
make[1]: Entering directory `/home/mgriep/src/tor/torsocks'
Making all in src
make[2]: Entering directory `/home/mgriep/src/tor/torsocks/src'
/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I..
-g -O2 -Wall -MT tsocks.lo -MD -MP -MF .deps/tsocks.Tpo -c -o tsocks.lo
tsocks.c
../libtool: line 821: X--tag=CC: command not found
../libtool: line 854: libtool: ignoring unknown tag : command not found
../libtool: line 821: X--mode=compile: command not found
../libtool: line 988: *** Warning: inferring the mode of operation is
deprecated.: command not found
../libtool: line 989: *** Future versions of Libtool will require
--mode=MODE be specified.: command not found
../libtool: line 1132: Xgcc: command not found
../libtool: line 1132: X-DHAVE_CONFIG_H: command not found
../libtool: line 1132: X-I.: command not found
../libtool: line 1132: X-I..: command not found
../libtool: line 1132: X-g: command not found
../libtool: line 1132: X-O2: command not found
../libtool: line 1132: X-Wall: command not found
../libtool: line 1132: X-MT: command not found
../libtool: line 1132: Xtsocks.lo: command not found
../libtool: line 1132: X-MD: command not found
../libtool: line 1132: X-MP: command not found
../libtool: line 1132: X-MF: command not found
../libtool: line 1132: X.deps/tsocks.Tpo: No such file or directory
../libtool: line 1132: X-c: command not found
../libtool: line 1184: Xtsocks.lo: command not found
../libtool: line 1189: libtool: compile: cannot determine name of library
object from `': command not found
make[2]: *** [tsocks.lo] Error 1
make[2]: Leaving directory `/home/mgriep/src/tor/torsocks/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/mgriep/src/tor/torsocks'
make: *** [all] Error 2
:~/src/tor/torsocks$ ./libtool --version
ltmain.sh (GNU libtool) 1.5.24 (1.1220.2.455 2007/06/24 02:13:29)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
:~/src/tor/torsocks$
}}}
Jun 08, 2009
issue 2
(compile problems on mac os x 10.5) commented on by mr.kamu
- Thanks for your help rob, however this problem has arrose:
$ make
make all-recursive
Making all in src
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -g -O2
-Wall -MT tsocks.lo -MD -MP -MF .deps/tsocks.Tpo -c -o tsocks.lo tsocks.c
../libtool: line 818: X--tag=CC: command not found
../libtool: line 851: libtool: ignoring unknown tag : command not found
../libtool: line 818: X--mode=compile: command not found
../libtool: line 985: *** Warning: inferring the mode of operation is deprecated.:
command not found
../libtool: line 986: *** Future versions of Libtool will require --mode=MODE be
specified.: command not found
../libtool: line 1129: Xgcc: command not found
../libtool: line 1129: X-DHAVE_CONFIG_H: command not found
../libtool: line 1129: X-I.: command not found
../libtool: line 1129: X-I..: command not found
../libtool: line 1129: X-g: command not found
../libtool: line 1129: X-O2: command not found
../libtool: line 1129: X-Wall: command not found
../libtool: line 1129: X-MT: command not found
../libtool: line 1129: Xtsocks.lo: command not found
../libtool: line 1129: X-MD: command not found
../libtool: line 1129: X-MP: command not found
../libtool: line 1129: X-MF: command not found
../libtool: line 1129: X.deps/tsocks.Tpo: No such file or directory
../libtool: line 1129: X-c: command not found
../libtool: line 1181: Xtsocks.lo: command not found
../libtool: line 1186: libtool: compile: cannot determine name of library object from
`': command not found
make[2]: *** [tsocks.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Thanks for your help rob, however this problem has arrose:
$ make
make all-recursive
Making all in src
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -g -O2
-Wall -MT tsocks.lo -MD -MP -MF .deps/tsocks.Tpo -c -o tsocks.lo tsocks.c
../libtool: line 818: X--tag=CC: command not found
../libtool: line 851: libtool: ignoring unknown tag : command not found
../libtool: line 818: X--mode=compile: command not found
../libtool: line 985: *** Warning: inferring the mode of operation is deprecated.:
command not found
../libtool: line 986: *** Future versions of Libtool will require --mode=MODE be
specified.: command not found
../libtool: line 1129: Xgcc: command not found
../libtool: line 1129: X-DHAVE_CONFIG_H: command not found
../libtool: line 1129: X-I.: command not found
../libtool: line 1129: X-I..: command not found
../libtool: line 1129: X-g: command not found
../libtool: line 1129: X-O2: command not found
../libtool: line 1129: X-Wall: command not found
../libtool: line 1129: X-MT: command not found
../libtool: line 1129: Xtsocks.lo: command not found
../libtool: line 1129: X-MD: command not found
../libtool: line 1129: X-MP: command not found
../libtool: line 1129: X-MF: command not found
../libtool: line 1129: X.deps/tsocks.Tpo: No such file or directory
../libtool: line 1129: X-c: command not found
../libtool: line 1181: Xtsocks.lo: command not found
../libtool: line 1186: libtool: compile: cannot determine name of library object from
`': command not found
make[2]: *** [tsocks.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
